|
Problem IC82348
|
Status: Closed |
DATABASE CAN BE MARKED BAD DURING RECOVERY OR HADR REPLAY WHEN XML DATA IS IN THE TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Symptoms:
Db2diag.log
2012-02-06-11.49.04.158495+540 I27449A462 LEVEL: Error
PID : 6488090 TID : 10025 PROC : db2sysc0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-8 APPID: *LOCAL.DB2.120204182517
EDUID : 10025 EDUNAME: db2redow (SAMPLE) 0
FUNCTION: DB2 UDB, Common Storage Layer, sqldcsl_pageInfo,
probe:411
MESSAGE : pageType
DATA #1 : pageType, PD_TYPE_CSL_PAGETYPE, 1 bytes
HLSM Page
2012-02-06-11.49.04.158701+540 I27912A471 LEVEL: Error
PID : 6488090 TID : 10025 PROC : db2sysc0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-8 APPID: *LOCAL.DB2.120204182517
EDUID : 10025 EDUNAME: db2redow (SAMPLE) 0
FUNCTION: DB2 UDB, Common Storage Layer, sqldcsl_pageInfo,
probe:415
MESSAGE : expected pageType
DATA #1 : pageType, PD_TYPE_CSL_PAGETYPE, 1 bytes
Data Page
[...]
2012-02-06-11.49.04.225710+540 E43842A932 LEVEL: Critical
PID : 6488090 TID : 9254 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-8 APPID: *LOCAL.DB2.120204182517
EDUID : 9254 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::MarkDBBad, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"DBMarkedBad". The instance may have been shutdown as
a result.
"Automatic" FODC (First Occurrence Data Capture) has
been invoked and diagnostic information has been recorded in
directory
"/var/log/db2inst1/FODC_DBMarkedBad_2012-02-06-11.49.04.211710_0
000/"
.Please look in this directory for detailed evidence
about what happened and contact IBM support if necessary to
diagnose the problem.
Stack:
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000000EDBB70 pthread_kill + 0xB0
0x09000000026BFAD8 sqloDumpEDU + 0x54
0x0900000002541A34 MarkDBBad__16sqeLocalDatabaseFi + 0x340
0x09000000027F8264 sqlpReplayMaster__FP8sqeAgent + 0x4CC
0x0900000001DAC750 sqleIndCoordProcessRequest__FP8sqeAgent +
0x2C4
0x0900000005437E08 RunEDU__8sqeAgentFv + 0x1E8
0x0900000005435320 EDUDriver__9sqzEDUObjFv + 0xDC
0x0900000005435204 sqlzRunEDU__FPcUi + 0x24
0x090000000543E4E4 sqloEDUEntry + 0x264
</StackTrace>
The related log records in this transaction should all reflect
the same object type (XML) and same object attributes. But in
this case, one of the log records contains the wrong object
information when it is written at runtime. If this bad log
record is later replayed, during either roll forward or HADR
replay scenarios, an error will be returned indicating the
mismatch. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* users prior to DB2 V97 fp5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97 fp6 *
**************************************************************** |
| Local Fix: |
In HADR environments, backup the primary database and use that
copy to reinitialize the standby database.
For roll forward cases, the table cannot be recovered after you
roll forward past the bad log record. IBM Support can guide you
to recover using filtered recovery to filter out the bad table
and then drop it later. |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 v97fp6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC82728
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.03.2012
12.06.2012
12.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
