|
Problem IC69548
|
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 / 980 - 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: *
* See APAR description *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB 9.8 FixPak 4. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Lösung |
See APAR description |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 29.06.2010
29.07.2011
29.07.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.8.
|
| Problem behoben lt. FixList in der Version |
| 9.8.0.4
|
 |
