By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,007 Members | 1,248 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,007 IT Pros & Developers. It's quick & easy.

-805 with ODBC access to SAMPLE database

P: n/a
I've used DB2 LUW V7 a long time ago. Now i'm back and installed DB2
V8.2.2 PE and CONNPE. The DB2 stuff like CC works fine. I can access
the sample db and also select records. Than i've defined the SAMPLE DB
as an ODBC datasource. But i'f i start my ODBC application, which
connects and than does a ODBC SQLTables function, it returns
with:

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES"(specific
name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
SAMPLE

-805 means a package was not found, but i've bind/rebind CLI/ODBC
packages, which doesn't help.

Btw. before i've done anything. I've also upgraded to fixpack 14.

Any help is appreciated.

Regards

Erwin Marschalk

Feb 3 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Feb 3, 5:36 pm, "ErwinMars" <erwin.marsch...@gmx.netwrote:
I've used DB2 LUW V7 a long time ago. Now i'm back and installed DB2
V8.2.2 PE and CONNPE. The DB2 stuff like CC works fine. I can access
the sample db and also select records. Than i've defined the SAMPLE DB
as an ODBC datasource. But i'f i start my ODBC application, which
connects and than does a ODBC SQLTables function, it returns
with:

[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES"(specific
name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
SAMPLE

-805 means a package was not found, but i've bind/rebind CLI/ODBC
packages, which doesn't help.

Btw. before i've done anything. I've also upgraded to fixpack 14.

Any help is appreciated.

Regards

Erwin Marschalk
Have you followed the instructions in the fixpak? I dont know about
fixpak 14, but something like (check the instructions), might help

db2updv8 -d $db
db2 "BIND /home/system/db2inst1/sqllib/bnd/@db2ubind.lst BLOCKING ALL
GRANT PUBLIC ACTION ADD"
db2 "BIND /home/system/db2inst1/sqllib/bnd/db2schema.bnd BLOCKING ALL
GRANT PUBLIC sqlerror continue"

/Lennart
Feb 3 '07 #2

P: n/a
On 3 Feb., 20:18, "Lennart" <Erik.Lennart.Jons...@gmail.comwrote:
On Feb 3, 5:36 pm, "ErwinMars" <erwin.marsch...@gmx.netwrote:


I've used DB2 LUW V7 a long time ago. Now i'm back and installed DB2
V8.2.2 PE and CONNPE. The DB2 stuff like CC works fine. I can access
the sample db and also select records. Than i've defined the SAMPLE DB
as an ODBC datasource. But i'f i start my ODBC application, which
connects and than does a ODBC SQLTables function, it returns
with:
[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES"(specific
name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
SAMPLE
-805 means a package was not found, but i've bind/rebind CLI/ODBC
packages, which doesn't help.
Btw. before i've done anything. I've also upgraded to fixpack 14.
Any help is appreciated.
Regards
Erwin Marschalk

Have you followed the instructions in the fixpak? I dont know about
fixpak 14, but something like (check the instructions), might help

db2updv8 -d $db
db2 "BIND /home/system/db2inst1/sqllib/b...@db2ubind.lst BLOCKING ALL
GRANT PUBLIC ACTION ADD"
db2 "BIND /home/system/db2inst1/sqllib/bnd/db2schema.bnd BLOCKING ALL
GRANT PUBLIC sqlerror continue"

/Lennart- Zitierten Text ausblenden -

- Zitierten Text anzeigen -
I've checked in the meatime the readme, i found and in the Information
Center the infos about Fixpack V8.2 FP 4 and 3. The only manual bind
information i found is about the Query Patroller. Nothing about ODBC/
CLI.

I checked also the catalog, because the ODBC SQLTables function
results in a CALL "SYSIBM.SQLTABLES" . The routine is in the catalog
and i run it with call "SYSIBM"."SQLTABLES" (NULL, NULL, NULL, NULL,
NULL) from CC, but i got the same results.

Erwin

Feb 4 '07 #3

P: n/a
On 4 Feb., 11:52, "ErwinMars" <erwin.marsch...@gmx.netwrote:
On 3 Feb., 20:18, "Lennart" <Erik.Lennart.Jons...@gmail.comwrote:


On Feb 3, 5:36 pm, "ErwinMars" <erwin.marsch...@gmx.netwrote:
I've used DB2 LUW V7 a long time ago. Now i'm back and installed DB2
V8.2.2 PE and CONNPE. The DB2 stuff like CC works fine. I can access
the sample db and also select records. Than i've defined the SAMPLE DB
as an ODBC datasource. But i'f i start my ODBC application, which
connects and than does a ODBC SQLTables function, it returns
with:
[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES"(specific
name "TABLES") has returned an error
SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
SAMPLE
-805 means a package was not found, but i've bind/rebind CLI/ODBC
packages, which doesn't help.
Btw. before i've done anything. I've also upgraded to fixpack 14.
Any help is appreciated.
Regards
Erwin Marschalk
Have you followed the instructions in the fixpak? I dont know about
fixpak 14, but something like (check the instructions), might help
db2updv8 -d $db
db2 "BIND /home/system/db2inst1/sqllib/b...@db2ubind.lst BLOCKING ALL
GRANT PUBLIC ACTION ADD"
db2 "BIND /home/system/db2inst1/sqllib/bnd/db2schema.bnd BLOCKING ALL
GRANT PUBLIC sqlerror continue"
/Lennart- Zitierten Text ausblenden -
- Zitierten Text anzeigen -

I've checked in the meatime the readme, i found and in the Information
Center the infos about Fixpack V8.2 FP 4 and 3. The only manual bind
information i found is about the Query Patroller. Nothing about ODBC/
CLI.

I checked also the catalog, because the ODBC SQLTables function
results in a CALL "SYSIBM.SQLTABLES" . The routine is in the catalog
and i run it with call "SYSIBM"."SQLTABLES" (NULL, NULL, NULL, NULL,
NULL) from CC, but i got the same results.

Erwin- Zitierten Text ausblenden -

- Zitierten Text anzeigen -
Thanks to everyone and to all the guys, which are asking and answering
in other topics. I found in another topic, that SYSIBM.SQLTABLES is
part of the db2schema.dll and because of that, db2schema.bnd needs to
bind. db2schema.bnd is forgotten in the *.lst files, which are
selected, if you bind ODBC/CLI with the bind utility. So i bound it
manually and now everything works.

Erwin

Feb 4 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.