SQL0443N Routine "SYSIBM.SQLCOLUMNS" has returned an error

During the export process from DB2 LUW database you can see error “SQL0443N Routine “SYSIBM.SQLCOLUMNS” (specific name “COLUMNS”) has returned an error SQLSTATE with diagnostic text “SYSIBM:CLI:-727””.

The case is connected with the access to SYSIBM schema for DB2ADMIN user. The general cause is that db2schema.bnd file needs to be re-bound to the database server.

Another possible cause is that the SELECT privilege was revoked from a set of system catalog tables. When the user tries to execute one of DB2's schema API's such as SYSIBM.SQLTABLES or SYSIBM.SQLCOLUMNS the execution will fail with a -551 error.

First of all try to increase the STMTHEAP size (for example, from 2048 to 4096).

Also to resolve the error try to perform the following steps on your server machine:

 db2 terminate 
 db2 CONNECT TO <database> 
 db2 BIND <DISK>:\IBM\SQLLIB\bnd\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE 
 db2 BIND <DISK>:\IBM\SQLLIB\bnd\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD 
 db2 BIND <DISK>:\IBM\SQLLIB\bnd\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD 
 db2 terminate 

If the problem persists, make sure that your user has appropriate rights for making SELECTS to below system tables.

  • SYSIBM.SQLTABLES
  • SYSIBM.SYSTABLES
  • SYSIBM.SQLTABLETYPES
  • SYSIBM.SQLTABLEPRIVILEGES
  • SYSIBM.SYSCOLUMNS
  • SYSIBM.SQLSPECIALCOLUMNS
  • SYSIBM.SQLCOLPRIVILEGES
  • SYSIBM.SYSDUMMY1
  • SYSIBM.SQLPRIMARYKEYS
  • SYSIBM.SQLSTATISTICS
  • SYSIBM.FOREIGNKEYS
  • SYSIBM.SYSINDEXES
  • SYSIBM.SQLPROCEDURES
  • SYSIBM.SQLPROCEDURECOLS
  • SYSIBM.SYSROUTINES
  • SYSIBM.SYSROUTINEPARMS
  • SYSIBM.SQLTYPEINFO
  • SYSIBM.SQLUDTS
  • SYSIBM.SQLSCHEMAS
  • SYSIBM.SYSRELS
  • SYSIBM.SYSKEYCOLUSE
  • SYSIBM.SYSTABCONST
  • SYSIBM.SYSDATATYPES

If your current user doesn't have enough permissions, you can assign them using the GRANT statement. Example:

 
 db2 "GRANT SELECT ON TABLE SYSIBM.SQLTABLES TO USER DB2INST1";
 

If all the steps described above do not help to solve the issue and the problem persists after all these manipulations, please reinstall DB2 DBMS.



More about Ispirer Systems