Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

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
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 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 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.