Hi,
Datastage Server Details:
OS: Windows server 2003
Database: Oracle10g
System DSN Created:-
Driver Used: Oracle in Oraclient10g_home1
Issue:- Job had DRS stage uisng ODBC as output. Job is getting aborted on warning messages without any Fatal Errors.
When same job is executed using Oracle in DRS stage, job is getting executed successful.
I can see there is some problem with the ODBC settings. Can anyone please suggest me the ODBC settings to be used while creating the system DSN.
Error while using ODBC in DRS stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
Hi Chulett,
The warning message received was "..Transformer_0: SQLExecute: No row was found for UPDATE", "'..Transformer_0: At row 19, link "DSLink4"
Row rejected.'
It was basically an update job, When using ODBC in DRS stage after some warning messages the job is getting aborted.
But when Oracle is selected in DRS stage, even though warning messages are received the job is not getting aborted (Which is what we require).
For Warning messages, job should not get aborted. Any idea on this pelase
The warning message received was "..Transformer_0: SQLExecute: No row was found for UPDATE", "'..Transformer_0: At row 19, link "DSLink4"
Row rejected.'
It was basically an update job, When using ODBC in DRS stage after some warning messages the job is getting aborted.
But when Oracle is selected in DRS stage, even though warning messages are received the job is not getting aborted (Which is what we require).
For Warning messages, job should not get aborted. Any idea on this pelase
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
Hi Chulett,
I agree with what you had said. But because of this why job is getting aborted. Warnings should not abort the job right?
In All the places as common practice we are using ODBC.
For making the changes mentioned by you, as the code is already in production, I need to go with minimum changes.
So can you suggest, changing the ODBC to Oracle will have any further implications or Not.
I agree with what you had said. But because of this why job is getting aborted. Warnings should not abort the job right?
In All the places as common practice we are using ODBC.
For making the changes mentioned by you, as the code is already in production, I need to go with minimum changes.
So can you suggest, changing the ODBC to Oracle will have any further implications or Not.
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am