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 IC65990 Status: Geschlossen

DB2PD SHOWS INCORRECT VALUES FOR LOGSECOND, AS A UNSIGNED INTEGER

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
The LOGSECOND db cfg parameter is set to -1 but when looking at 
the db2pd output it shows 65535 which is incorrect. 
 
Take database Sample as an example. 
First, update the value of LOGSECOND as -1: 
DB2 UPDATE DATABASE CONFIGURATION FOR sample USING LOGSECOND -1 
Then run below command to get the value of LOGSECOND, it would 
show 65535 instead of -1. 
db2pd -db sample -dbcfg | \grep -i LOGSECOND
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The LOGSECOND db cfg parameter is set to -1 but when looking * 
* at the db2pd output it shows 65535 which is incorrect.       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The LOGSECOND db cfg parameter is set to -1 but when looking * 
* at the db2pd output it shows 65535 which is incorrect.       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 6                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem fixed in DB2 Version  9.5 FixPack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.02.2010
18.05.2010
18.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version