LinkedIn
Copied!

Table of Contents

Issue: CLI Catalog errors after upgrade of DB2 UDB to 8.1 Fix Pak 10

Symptom

When you upgrade to DB2 UDB Version 8.1 Fix Pak 10 (also called Version 8.2 Fix Pak 3) you will receive errors when calling a CLI Catalog function. The errors indicate that a datasource cannot be found.

A CLI Catalog function provides a generic interface to issue queries and returns consistent result sets across the DB2 family of servers. For example, SQLChar() returns characters specified by certain parameters:

SQLCHAR tbNamePattern[] = "ST%"; 

The above example returns all table names beginning with ST.

The following is an example of an error message that may appear when you call a CLI catalog function:

SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text SYSIBM:CLI:-805. SQLSTATE=38553

The CLI catalog functions execute routines on the DB2 UDB server and these routines use packages created by the db2schema.bnd bind file. Since this bind file was renamed in Version 8.1 FP 10, it is not getting bound to all the databases on your server. This is the cause of the errors.

Solution

To eliminate these errors you need to bind the db2schema.bnd file locally against each database, using the following commands from the command prompt:

IMPORTANT: Perform these steps in a local connection to the database.

db2 terminate
db2 connect to <database-name>
db2 bind <path>/db2schema.bnd blocking all grant public sqlerror continue
db2 terminate

where:

  • <database-name> is the name of the database to which the utilities will be bound
  • <path> is the full path name of the directory where the bind files are located.

For more information, see these IBM Web resources:

 
Pega Platform 7.1.1 - 8.3.1 System Architect System Administrator System Administration
Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.