Instance fails to start if system date is modified
A directory server instance might fail to start if the system date is modified.
Suppose that the system date is set to a previous date. For example, it might be set to one month before the date when the directory server instance was configured on the system. If such a significant change is made to the system date, then the directory server instance might fail to start. The following error messages can be seen:
GLPRDB001E Error code -1 from function:" SQLTables ".
GLPRDB001E Error code -1 from function:" SQLFetch ".
GLPRDB001E Error code -1 from function:" SQLFetch ".
GLPRDB001E Error code -1 from function:" SQLFetch ".
GLPSRV064E Failed to initialize be_config.In this scenario, the directory server instance is run with server
trace set to ON and the debug level is set. The following error messages
can be seen in the server trace:
188:22:35:24 T1 retrieving SQLGetDiagRec info
188:22:35:24 T1 Error - map_rc_fnc: henv=0,hdbc=0,hstmt=10001,native
retcode = -443; state = "38553"; message = "[IBM][CLI Driver][DB2/SUN64]
SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned
an error SQLSTATE with diagnostic text "SYSIBM:CLI:-727". SQLSTATE=38553"These
error messages can also be seen in the db2diag.log file.