Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
After an instrance crash due to a problem with the free_blk_ptr (see APAR IZ20871). Crash recovery may fail due to an invalid value in the associated log record. The system cannot continue with crash recovery because of a validation check that finds the log record values do not match the current target page. The db2diag.log will indicate the following message. 2008-03-28-12.22.37.287849-240 I187556927E591 LEVEL: Severe PID : 26449 TID : 183030155104PROC : db2redow (SAMPLE) 0 INSTANCE: DB2INST1 NODE : 000 DB : NAGCPI01 APPHDL : 0-7 APPID: *LOCAL.DB2INST1.080328162202 AUTHID : DB2INST1 FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1897 MESSAGE : Free Space does not match during redo! DATA #1 : Hexdump, 26 bytes 0x0000000DB37FA8A0 : 01A2 0700 0500 0000 CD00 B0FF A200 1E2B ...............+ 0x0000000DB37FA8B0 : 1201 F600 0000 CD00 8100 This issue can happen on the following platforms; LinuxAMD64 Windows x86 -64bit
Local fix
If this occurs during crash recovery, recover the DB by restoring and then rolling forward to a point in time prior to the invalid log record.
Problem summary
After an instrance crash due to a problem with the free_blk_ptr (see APAR IZ20871). Crash recovery may fail due to an invalid value in the associated log record. The system cannot continue with crash recovery because of a validation check that finds the log record values do not match the current target page. The db2diag.log will indicate the following message. 2008-03-28-12.22.37.287849-240 I187556927E591 LEVEL: Severe PID : 26449 TID : 183030155104PROC : db2redow (SAMPLE) 0 INSTANCE: DB2INST1 NODE : 000 DB : NAGCPI01 APPHDL : 0-7 APPID: *LOCAL.DB2INST1.080328162202 AUTHID : DB2INST1 FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1897 MESSAGE : Free Space does not match during redo! DATA #1 : Hexdump, 26 bytes 0x0000000DB37FA8A0 : 01A2 0700 0500 0000 CD00 B0FF A200 1E2B ...............+ 0x0000000DB37FA8B0 : 1201 F600 0000 CD00 8100 This issue can happen on the following platforms; LinuxAMD64 Windows x86 -64bit LOCAL FIX: If this occurs during crash recovery, recover the DB by restoring and then rolling forward to a point in time prior to the invalid log record.
Problem conclusion
First fixed in DB2 UDB V9.1 fixpak 5
Temporary fix
Comments
APAR Information
APAR number
LI73356
Reported component name
DB2 UDE ESE LIN
Reported component ID
5765F4104
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-17
Closed date
2008-07-07
Last modified date
2008-07-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDE ESE LIN
Fixed component ID
5765F4104
Applicable component levels
R910 PSN
UP
Document Information
Modified date:
15 October 2021