SQLSTATE=S0022, DBMS.CODE=-206

Krazykoolrohit · Post by **Krazykoolrohit** » Thu Aug 31, 2006 9:01 am

Hi,
I am having the following error whevever i run the job.

SQLSTATE=S0022, DBMS.CODE=-206
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]<column name> NOT COLUMN OF INSERTED/UPDATED TABLE, OR ANY TABLE IN A FROM CLAUSE

this job uses ODBC stage to connect to DB2. I have a similar job connecting to the same table which is working fine. but the other job uses bulk loader to load data.

Has anyone faced this before?

thanx,
rohit

meena · Post by **meena** » Thu Aug 31, 2006 9:16 am

Hi Rohit,
I think this is because of the SQL CODE. The message "SQLSTATE=S0022"
is for a invalid column name. Can you check for the column name and where clause in the SQL code.

SQLSTATE=S0022, DBMS.CODE=-206
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]<column name> NOT COLUMN OF INSERTED/UPDATED TABLE, OR ANY TABLE IN A FROM CLAUSE

If possible can you post your SQL code..

thumsup9 · Post by **thumsup9** » Thu Aug 31, 2006 9:16 am

Check the SQL that the Database is generating and see if it matches the columns on Table. This looks like a mismatch of columns.

Krazykoolrohit · Post by **Krazykoolrohit** » Thu Aug 31, 2006 9:22 am

meena wrote:Hi Rohit,
I think this is because of the SQL CODE. The message "SQLSTATE=S0022"
is for a invalid column name. Can you check for the column name and where clause in the SQL code.

SQLSTATE=S0022, DBMS.CODE=-206
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]<column name> NOT COLUMN OF INSERTED/UPDATED TABLE, OR ANY TABLE IN A FROM CLAUSE
If possible can you post your SQL code..

This table runs with the bulk loader with the same schema as it is in ODBC stage. The bulk loader works fine without any warnings but the ODBC stage does not. If there was a column mismatch, non of the two stages would have worked

meena · Post by **meena** » Thu Aug 31, 2006 9:40 am

Hi Rohit,
Are you using the same SQL code in both jobs. If no then can you post your SQL code.Because from the warning I still think it is the problem with the SQL code.

This table runs with the bulk loader with the same schema as it is in ODBC stage. The bulk loader works fine without any warnings but the ODBC stage does not. If there was a column mismatch, non of the two stages would have worked

Krazykoolrohit · Post by **Krazykoolrohit** » Thu Aug 31, 2006 9:50 am

meena wrote:Hi Rohit,
Are you using the same SQL code in both jobs. If no then can you post your SQL code.Because from the warning I still think it is the problem with the SQL code.

This table runs with the bulk loader with the same schema as it is in ODBC stage. The bulk loader works fine without any warnings but the ODBC stage does not. If there was a column mismatch, non of the two stages would have worked

The Sql code was self-generated. anyways, i deleted the ODBC stage and recreated from scratch including inporting schema from the table. it is working now. guess there was some column name mismatch (even though i was not able to spot it through naked eyes).

thanx anyways.