|
Problem IC69548
|
Status: Closed |
DB2PD -DBCFG AND GET DB CFG SHOW DETAIL WILL ALWAYS DISPLAY 0 AS CURRENT VALUE FOR LOGSECOND, WHEN IT SHOULD BE -1 |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* See APAR description *
****************************************************************
* PROBLEM DESCRIPTION: *
* See APAR description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB 9.8 FixPak 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
See APAR description |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.06.2010
29.07.2011
29.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
