|
Problem IC69232
|
Status: Geschlossen |
DB2PD -DBCFG AND GET DB CFG SHOW DETAIL WILL ALWAYS DISPLAY 0 AS CURRENT VALUE FOR LOGSECOND, WHEN IT SHOULD BE -1 |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
A database configured for infinite active logging, by having
LOGSECOND set to -1, will display the current in-memory value
for LOGSECAND always as 0, even after recycling the instance
or database.
The following commands show the behavior:
* db2pd -db <dbname> -dbcfg
* db2 get db cfg for <dbname> show detail
Due to the difference between the in-memory value and the
database config file value, CallCenter will report "effective
after database restart". |
| Problem-Zusammenfassung: |
USERS AFFECTED: All
PROBLEM DESCRIPTION:
See ERROR DESCRIPTION
PROBLEM SUMMARY:
See ERROR DESCRIPTION |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
Problem was first fixed in Version 9.7 Fix Pack 3. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.06.2010
24.09.2010
24.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
