home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC75045 Status: Geschlossen

PARAMETER LOGSECOND HAS WRONG VALUE ON SYSIBMADM.DBCFG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
The problem was fixed in DB2 v9.7 FP5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.03.2011
06.03.2012
06.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList