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 IC78465 Status: Closed

ROLLFORWARD FROM LOGS AFTER TRUNCATE ON XML TABLE MAY FAIL WITH DB MARKED
BAD

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
While doing a Restore->Rollforward from logs, if there is a 
Truncate on XML Table as part of those logs a user may encounter 
Database MARKED BAD due to missing XML Dictionary. 
 
This will typically result in similar db2diag info (below) if 
the logs which we are recovering from include the TRUNCATE log 
record and either an INSERT, IMPORT, LOAD record which was 
executed afterwards. 
 
 
2011-02-02-00.14.59.911000+540 I5597490F522       LEVEL: Severe 
PID     : 4264                 TID  : 4680        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : SAMPLE 
APPHDL  : 0-4025               APPID: *LOCAL.DB2.101031134609 
EDUID   : 4680                 EDUNAME: db2redow (SAMPLE) 
FUNCTION: DB2 UDB, Common Storage Layer, 
sqldcsl_redoMultiRowInsert, 
probe:89 
MESSAGE : Update count (probeID = current update count) 
incorrect duirng 
redo! 
DATA #1 : unsigned integer, 4 bytes 
0 
 
2011-02-02-00.15.00.004000+540 I5600304F500       LEVEL: Severe 
 
PID     : 4264                 TID  : 4680        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : SAMPLE 
 
APPHDL  : 0-4025               APPID: *LOCAL.DB2.101031134609 
 
EDUID   : 4680                 EDUNAME: db2redow (SAMPLE) 
 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging 
fu, probe:0 
 
MESSAGE : SQLD_TCB: 
 
DATA #1 : String, 39 bytes 
 
Perm Table(3:12)=TBSPACEID=3.TABLEID=12
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW V97 and Newer Releases                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR Description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 FP5 or newer.                                 * 
****************************************************************
Local Fix:
available fix packs:
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 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
Fix provided in v97 FP5 and newer releases.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.09.2011
17.01.2012
17.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList