|
Problem IC65990
|
Status: Closed |
DB2PD SHOWS INCORRECT VALUES FOR LOGSECOND, AS A UNSIGNED INTEGER |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
Problem fixed in DB2 Version 9.5 FixPack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.02.2010
18.05.2010
18.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
