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
SQLSTATE=S0022, DBMS.CODE=-206
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
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.
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.
If possible can you post your 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
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
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.
If possible can you post your 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
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
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.
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
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
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).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
thanx anyways.