Warings msgs for Update Or insert type in ODBC Stage

[Vijay Kumar]

Hi,
I am getting the following warning message for the ODBC stage, in which I am using Update or Insert strategy.

Code: Select all

jbGenerateKeyForAddress.BG.FilterGoodKeys.LnkTgtGoodKeys: DSD.BCIPut call to SQLExecute failed.

SQL statement:UPDATE COMET_ETL.XREF SET SOURCE_KEY = ? WHERE (GSFA_CUSTOMER_ID = ? AND DIVISION_ID = ? AND COUNTRY_ID = ?) 

2 Rows affected.

 

GSFA_CUSTOMER_ID = "BGC3160811550"

DIVISION_ID = "0"

COUNTRY_ID = "BG"

SOURCE_KEY = "ALEXSOFI32"

Yes, I have selected the three columns in the where clause as the keys.
Is this error is because of more than one record for the key columns????
or any other reason.
I don't want to have any warning msgs if it updates more than one record at a time.
Though the jobs is giving warnings the records are getting updated.
How to avoid these types of warning msgs??

Thanks & Regards
Vijay Kumar

[ray.wurlod]

When a database server generates any message (in this case "2 rows affected") DataStage logs it. This is the DataStage philosophy, on which I've posted at length before - search for "philosophy".

The only possible way to suppress these messages is to cause the database (or ODBC driver) not to generate them. Talk with your DBA about whether this is possible (for example by setting an environment variable).

[yaminids]

Vijay,

We have developed many jobs which update rows in a table and never received such warnings

Yamini
P.S. As Ray said may be our DBA did something in Oracle not to generate any messages

[chulett]

Guys - where was the 'O' word ever mentioned? Oracle doesn't return status messages like that, looks more like a DB2 thing to me.

[ray.wurlod]

Noted. How about the other "O" word - ODBC driver? Might the "2 rows affected" message have been generated by an ODBC driver?

[chulett]

Possibly... would need Vijay to pop back in and clarify the database and ODBC drivers in use here.

[Vijay Kumar]

Hi,
I am using ODBC stage to connect Oracle Database.
And we have enables NLS configuration for our Datastage and data base.

Let me know whether I can configure any settings in datastage to avoid such warnings.

Thanks in Advance

Vijay Kumar

[ray.wurlod]

No idea. I'm not an Oracle DBA. Why don't you ask your Oracle DBA?

[chulett]

Definitely have a chat with your DBA. In the meantime, unless you are using wire drivers with the ODBC stage and for some reason really want to stick with the ODBC stage, why not switch to OCI? You won't have these issues with the OCI stages.