Troubleshooting
Problem
This solution describes how ibmslapd will start in config only mode if a DB2 fixpack is applied without having followed the post-install instructions from the DB2 fixpack readme, including the errors that will appear, and the resolution for the problem.
Symptom
If after having applied a DB2 fixpack, the following kinds of errors appear in the following two logs:
ibmslapd.log:
02/31/06 21:26:06 Error code -1 from odbc string:" SQLTables " .
02/31/06 21:26:07 Error code -1 from odbc string:" SQLFetch " .
02/31/06 21:26:07 Error code -1 from odbc string:" SQLFetch " .
02/31/06 21:26:07 Error code -1 from odbc string:" SQLFetch " .
db2cli.log:
02/31/06 21:26:06 native retcode = -443; state = "38553"; message = "[IBM][CLI Driver][DB2/6000] SQL0443N Routine "SYSIBM.SQLTABLES"(specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553"
02/31/06 21:26:07 native retcode = -99999; state = "24000"; message = "[IBM][CLI Driver] CLI0115E Invalid cursor state. SQLSTATE=24000"
02/31/06 21:26:07 native retcode = -99999; state = "24000"; message = "[IBM][CLI Driver] CLI0115E Invalid cursor state. SQLSTATE=24000"
02/31/06 21:26:07 native retcode = -99999; state = "24000"; message = "[IBM][CLI Driver] CLI0115E Invalid cursor state. SQLSTATE=24000"
Cause
DB2 databases and schema need to be rebound after a fixpack install.
Resolving The Problem
All the DB2 fixpack post-install instructions must be completed before starting ibmslapd.
For DB2 8.x these instructions are included in the fixpack readme.
For DB2 9.x, see the following set of instructions in the DB2 Infocenter:
Applying DB2 v9 fixpacks
If, after following the post-install instructions, the same errors above continue, then some step must have been missed or not completed successfully.
Product Synonym
ITDS;IDS;Directory Server;IBM Tivoli Directory Server;Tivoli Directory Server
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21217323