|
Problem IC64656
|
Status: Closed |
DB CONFIG UPDATE ALLOWS LOGPRIMARY + LOGSECOND TO EXCEED LIMIT OF 256 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The Logprimary database configuration parameter is not allowed
to exceed 256 when Logsecond is set to -1. If Logsecond is not
set to -1, however, the sum of Logprimary and Logsecond is not
allowed to exceed 256.
There is a situation which allows the sum of these values to
exceed 256, which may then lead to unexpected behaviour in
DB2's logging infrastructure.
The following steps will reproduce this problem:
1. Activate the database with Logprimary and Logsecond set to
values 20 and 100 respectively.
LOGPRIMARY = 20
LOGSECOND = 100
2.
Update Logprimary to a smaller value such as 10. This value is
deferred, as Logprimary is not dynamically updateable, hence
the current value of Logprimary is still 20.
update db cfg using logprimary 10
3.
Update Logsecond where the deferred value of Logprimary plus
Logsecond will still respect being equal to or below 256.
update db cfg using logsecond 246
The update statement outlined in step 3 should be blocked, as
the current value of Logprimary plus Logsecond exceeds the
limit of 256. Running the database in this state could result
in
unexpected behaviour. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 systems on all Linux, Unix, and Windows platforms at *
* service levels from Version 9.7 GA. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The Logprimary database configuration parameter is not *
* allowed *
* to exceed 256 when Logsecond is set to -1. If Logsecond is *
* not *
* set to -1, however, the sum of Logprimary and Logsecond is *
* not *
* allowed to exceed 256. *
* *
* There is a situation which allows the values to exceed 256, *
* *
* which may then lead to unexpected behaviour in DB2's logging *
* *
* infrastructure. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 1 or see "Local Fix" *
* portion for other suggestions. *
**************************************************************** |
| Local Fix: |
If updating Logprimary to a lower value, ensure to disconnect
all applications so that the new value takes effect before
deciding to update Logsecond. If recycling the database is not
an option, manually calculate the sum between the current value
of Logprimary and Logsecond when dynamically increasing the
value of Logsecond. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
The complete fix for this problem first appears in DB2 Version
9.7 Fix Pack 1 and all the subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.11.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
