DB2 - Problem description
Problem IC75045 | Status: Closed |
PARAMETER LOGSECOND HAS WRONG VALUE ON SYSIBMADM.DBCFG | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If the database parameter LOGSECOND is set to -1, fetch from administration view SYSIBMADM.DBCFG return wrong value 65535. You can check this using the following query: db2 "select substr(name, 1, 10), substr(value, 1, 10), substr(deferred_value, 1, 10) from sysibmadm.dbcfg where name = 'logsecond'" | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users running DB2 v9.7 FP4 and earlier. * **************************************************************** * PROBLEM DESCRIPTION: * * If the database parameter LOGSECOND is set to -1, fetch from * * * * administration view SYSIBMADM.DBCFG return wrong value * * 65535. * * You can check this using the following query: * * * * * * * * db2 "select substr(name, 1, 10), substr(value, 1, 10), * * * * substr(deferred_value, 1, 10) from sysibmadm.dbcfg where * * name = * * 'logsecond'" * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 FP5. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
The problem was fixed in DB2 v9.7 FP5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.03.2011 06.03.2012 06.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |