|
Problem IC66994
|
Status: Geschlossen |
DB2PD SHOWS INCORRECT VALUES FOR LOGSECOND, AS A UNSIGNED INTEGER |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 980 - 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: *
* See error description *
****************************************************************
* RECOMMENDATION: *
* Problem fixed in DB2 Version 9.8 FixPack 3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Lösung |
Problem fixed in DB2 Version 9.8 FixPack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.03.2010
03.01.2011
03.01.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.8.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.8.0.3
|
 |
