|
On Aug 11, 2015, at 10:13 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:--
Anything in the IBM i job logs?
Seems like either the table isn't there or user ID being doesn't have
authority to add records.
Charles
On Tue, Aug 11, 2015 at 10:12 AM, Charles Wilt
<charles.wilt@xxxxxxxxx>
wrote:
C205105V is your IBM i DB Name? Use WRKRDBDIRE to make sure.--
Does a select work?
Select * from [INDY2].[C205105V].[VD_GPL].[AX__METRICS]
This has worked for me:
insert into LINKSVR.IBMDBNAM.MYLIB.MYFILE values('00014',5,99);
I've never tried it with the brackets in the names.
Charles
On Tue, Aug 11, 2015 at 9:56 AM, Darryl Freinkel
<dhfreinkel@xxxxxxxxx>
wrote:
Insert into [INDY2].[C205105V].[VD_GPL].[AX__METRICS]
Values(Current_timestamp, 'Extract', 'STD COST', 'Number of STD
COST records extracted',
(select count(*) from dbo.DMFINVENTJOURNALENTITY ) ) ; Insert
into [INDY2].[C205105V].[VD_GPL].[AX__METRICS]
Values(Current_timestamp,
'Extract',
'OSV',
'Duplicates found',
(SELECT COUNT(*) FROM ( select count(*) from
dbo.DMFINVENTJOURNALENTITY group by inventlocationID, wmslocationid,
ITEMID, CONFIGID having count(*) > 1 )) )
;
Msg 7306, Level 16, State 2, Line 2
Cannot open the table ""C205105V"."VD_GPL"."AX__METRICS"" from OLE
DB provider "DB2OLEDB" for linked server "INDY2". Unknown provider error.
Here are the 2 statements.
Sent from my iPad
database.On Aug 11, 2015, at 9:37 AM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
Can you post the statement?
On Tue, Aug 11, 2015 at 9:33 AM, Darryl Freinkel
<dhfreinkel@xxxxxxxxx>
wrote:
I need to write some data from a Microsoft database to the IBM i
day.
The problem I have is I have a linked server that I can read from
all
TheHowever, I cannot write back to the linked server which is my IBM i.
serverscript is basically rejecting the 4 part file name, that is,
[linked
issue?name].[catalog name].[library name].[file name]
Has anyone experienced this issue and how did you work around the
list
TIA.
Darryl Freinkel.
Sent from my iPad
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,--
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,--
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.