home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63999 Status: Closed

THE LOG FILE COUNTER INCREASES BEYOND IT'S MAX VALUE OF 256
CAUSING THE ROLLFORWARD TO FAIL.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When transactions are spanning way too many log files, lowtran 
is not updated correctly on disk, thus causing the log file 
counter to exceed it's defined maximum value of 256 which in 
turn causes the rollforward to fail. 
 
Typical messages in db2diag.log for this issue are as follows: 
 
2008-11-05-06.08.33.543414+000 I2916333237A513    LEVEL: Warning 
PID     : 284126               TID  : 1           PROC : 
db2redom (SAMPLE) 0 
INSTANCE: db2inst1               NODE : 000         DB   : 
SAMPLE 
APPHDL  : 0-2116               APPID: 
*LOCAL.db2inst1.081105053829 
AUTHID  : db2inst1 
FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:805 
MESSAGE : INFO ONLY: Too many logs, need to reclaim. Head extent 
is 
DATA #1 : Hexdump, 4 bytes 
0x078000002001093C : 000A E62E 
-- 
--- 
2008-11-05-06.14.02.228083+000 I2916770449A467    LEVEL: Severe 
PID     : 135220               TID  : 1           PROC : 
db2agent (SAMPLE) 0 
INSTANCE: db2inst1               NODE : 000 
APPHDL  : 0-2117               APPID: 
*LOCAL.db2inst1.081105061402 
AUTHID  : db2inst1 
FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:450 
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services.
Problem Summary:
THE LOG FILE COUNTER INCREASES BEYOND IT'S MAX VALUE OF 256 
CAUSING THE ROLLFORWARD TO FAIL.
Local Fix:
No local fix.
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
Fixed in DB2 V9.7 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
10.03.2010
10.03.2010
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 FixList