|
Problem IC61990
|
Status: Closed |
Roll forward or crash recovery fails with SQLD_BAD_LREC error |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
With DATA CAPTURE CHANGES enabled on a range partitioned table,
if a partition is added, attached, or detached, and that
operation is rolled back, an incorrect compensation log record
is written. Subsequent attempts to roll forward through these
log records, through crash recovery or roll forward or through
HADR, will fail.
The following message is recorded in the diag log:
2009-07-10-14.02.38.819875-240 I62003A612 LEVEL: Severe
PID : 2826256 TID : 11916 PROC
: db2sysc
INSTANCE: sample NODE : 000 DB :
SAMPLE
APPHDL : 0-10 APPID: <masked>
AUTHID : <masked>
EDUID : 11916 EDUNAME:db2redom (SAMPLE)
FUNCTION: DB2 UDB, data management,sqldRedo, probe:7320
RETCODE :ZRC=0x87040051=-2029780911=SQLD_BAD_LREC
"invalid logrecord encountered during redo/undo
unknown component"
DIA8572C An invalid log record has been
encountered,
the value was "". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users with DATA CAPTURE CHANGES enabled on range *
* partitioned tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* An incorrect log record is written during the rollback of an *
* ADD, ATTACH or DETACH partition operation on a range *
* partitioned table with DATA CAPTURE CHANGES enabled. *
* Rolling forward through these log records will fail with an *
* SQLD_BAD_LREC error reported in the db2diag.log. *
****************************************************************
* RECOMMENDATION: *
* Apply a fix pack that contains the fix. *
**************************************************************** |
| 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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
First fixed in DB2 version 9.7 fix pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.07.2009
05.01.2010
05.01.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
|
 |
