ODBC Issues - SQL0443 SQLSTATE=38553

[Jason Gyetko]

I'm running DB2 v8.1 FP5 and am trying to link tables via ODBC from Access
2002 to my DB2 database. Access lets me connect to the database and returns
a list of all tables I can select from, but when I select one and choose OK
(to link or import) I immediately get the following message:

ODBC--call failed.

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLCOLUMNS" (specific
name "COLUMNS") has returned an error SQLSTATE with diagnostic text
"SYSIBM:CLI:-727". SQLSTATE=38553 (#-443)

I ran the db2ubind & db2cli binds successfully and attempted to run the
db2schema bind, but received the following errors:

LINE MESSAGES FOR db2schema.bnd
------ -------------------------------------------------------------
SQL0061W The binder is in progress.
2775 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
3838 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4026 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4219 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4364 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4381 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous errors.
SQL0091N Binding was ended with "8" errors and "0" warnings.

Can anybody tell me what I'm missing or what I'm doing wrong? Any thoughts
would be greatly appreciated. Thanks.

[Jason Gyetko]

To get the db2schema bind to work, I had to increase the STMTHEAP to 60000.
Once the bind was successful, the ODBC error was resolved.

"Jason Gyetko" <jg*****@epower-inc.com> wrote in message
news:Mx*****************@newssvr17.news.prodigy.co m...

I'm running DB2 v8.1 FP5 and am trying to link tables via ODBC from Access
2002 to my DB2 database. Access lets me connect to the database and returns a list of all tables I can select from, but when I select one and choose OK (to link or import) I immediately get the following message:

ODBC--call failed.

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLCOLUMNS" (specific
name "COLUMNS") has returned an error SQLSTATE with diagnostic text
"SYSIBM:CLI:-727". SQLSTATE=38553 (#-443)

I ran the db2ubind & db2cli binds successfully and attempted to run the
db2schema bind, but received the following errors:

LINE MESSAGES FOR db2schema.bnd
------ -------------------------------------------------------------
SQL0061W The binder is in progress.
2775 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
3838 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4026 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4219 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4364 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4381 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous errors.
SQL0091N Binding was ended with "8" errors and "0" warnings.

Can anybody tell me what I'm missing or what I'm doing wrong? Any thoughts would be greatly appreciated. Thanks.

[Jason Gyetko]

FYI: Once I changed the STMTHEAP size back to its original value of 512,
the ODBC error returned, so I made it 1024 and now it appears to be working
again. Not sure if it was the bind or the STMTHEAP increase that resolved
the ODBC error.

"Jason Gyetko" <jg*****@epower-inc.com> wrote in message
news:Mx*****************@newssvr17.news.prodigy.co m...

I'm running DB2 v8.1 FP5 and am trying to link tables via ODBC from Access
2002 to my DB2 database. Access lets me connect to the database and returns a list of all tables I can select from, but when I select one and choose OK (to link or import) I immediately get the following message:

ODBC--call failed.

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLCOLUMNS" (specific
name "COLUMNS") has returned an error SQLSTATE with diagnostic text
"SYSIBM:CLI:-727". SQLSTATE=38553 (#-443)

I ran the db2ubind & db2cli binds successfully and attempted to run the
db2schema bind, but received the following errors:

LINE MESSAGES FOR db2schema.bnd
------ -------------------------------------------------------------
SQL0061W The binder is in progress.
2775 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
3838 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4026 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4219 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4364 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4381 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous errors.
SQL0091N Binding was ended with "8" errors and "0" warnings.

Can anybody tell me what I'm missing or what I'm doing wrong? Any thoughts would be greatly appreciated. Thanks.

[Fan Ruo Xin]

SQL0101N The statement is too long or too complex. SQLSTATE=54001
When you're getting this error code, you do need to increase stmtheap size.
but I don't know why db2schema bind need a bigger stmt heap size (>512).

"Jason Gyetko" <jg*****@epower-inc.com> wrote in message
news:tY*****************@newssvr17.news.prodigy.co m...

FYI: Once I changed the STMTHEAP size back to its original value of 512,
the ODBC error returned, so I made it 1024 and now it appears to be working again. Not sure if it was the bind or the STMTHEAP increase that resolved
the ODBC error.

"Jason Gyetko" <jg*****@epower-inc.com> wrote in message
news:Mx*****************@newssvr17.news.prodigy.co m...

I'm running DB2 v8.1 FP5 and am trying to link tables via ODBC from Access 2002 to my DB2 database. Access lets me connect to the database and

returns

a list of all tables I can select from, but when I select one and choose

OK

(to link or import) I immediately get the following message:

ODBC--call failed.

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLCOLUMNS" (specific name "COLUMNS") has returned an error SQLSTATE with diagnostic text
"SYSIBM:CLI:-727". SQLSTATE=38553 (#-443)

I ran the db2ubind & db2cli binds successfully and attempted to run the
db2schema bind, but received the following errors:

LINE MESSAGES FOR db2schema.bnd
------ -------------------------------------------------------------
SQL0061W The binder is in progress.
2775 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
3838 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4026 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4219 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4364 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
4381 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous errors.
SQL0091N Binding was ended with "8" errors and "0" warnings.

Can anybody tell me what I'm missing or what I'm doing wrong? Any

thoughts

would be greatly appreciated. Thanks.