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

A TRAP MAY OCCUR DURING ROLLFORWARD USING COMPRESSION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
While running roll forward to end of logs, a panic was hit at 
sqldReorgCopyPhase, probe:9972, Dictionary already built, 
incorrect reorgFlags.  This can happen when table row 
compression is being used.  The runtime operational sequence of 
events include: load replace resetdictionary followed by reorg 
table keepdictionary. 
 
 
 
db2diag.log 
2010-01-12-13.12.25.955582-300 I2103123E1547         LEVEL: 
Severe 
PID     : 12612                TID  : 46942809745728 KTID : 
11900 
PROC    : db2sysc 0 
INSTANCE: svtdbm9              NODE : 000          DB   : 
TESTDB2 
APPHDL  : 0-653                APPID: *N0.svtdbm9.100112180227 
AUTHID  : SVTDBM9 
EDUID   : 359                  EDUNAME: db2redom (TESTDB2) 0 
FUNCTION: DB2 UDB, data management, sqldReorgCopyPhase, 
probe:9972 
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR 
          "non-severe dms programming error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : String, 46 bytes 
Dictionary already built, incorrect reorgFlags 
DATA #2 : String, 8 bytes 
sqldreor 
CALLSTCK: 
  [0] 0x00002AB106C7EF87 pdLog + 0x1C5 
  [1] 0x00002AB10AE05DBC sqlzSetAndLog901 + 0x3A0 
  [2] 0x00002AB1074922A4 _Z18sqldReorgCopyPhaseP13SQLD_REORG_CB 
+ 0x1D6 
  [3] 0x00002AB10743E622 /home/svtdbm9/sqllib/lib64/libdb2e.so.1 
+ 0x25B4622 
  [4] 0x00002AB10743F772 /home/svtdbm9/sqllib/lib64/libdb2e.so.1 
+ 0x25B5772 
  [5] 0x00002AB10744588E 
_Z10sqldomRedoP8sqeAgentP10SQLDOM_LRHP9SQLP_LSN8P15SQLD_RECOV_IN 
FO 
+ 0x242 
  [6] 0x00002AB10742B3BF 
_Z8sqldmrdoP8sqeAgentP9SQLP_LSN8PcmmmmP8SQLP_TIDP15SQLD_RECOV_IN 
FO 
+ 0x6EB 
  [7] 0x00002AB109701611 
_Z13sqlpRecDbRedoP8sqeAgentP8SQLP_ACBP9SQLP_DBCBP10SQLP_FRAPPP11 
SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT 
+ 0x775 
  [8] 0x00002AB109705D31 
_Z15sqlprProcDPSrecP10SQLPR_PRCBjP20SQLPR_PR_QUEUE_ENTRY + 0x55B 
  [9] 0x00002AB10970C9A4 
_Z15sqlpPRecReadLogP8sqeAgentP8SQLP_ACBP9SQLP_DBCB + 0x407A
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A trap may occur during roll forward recovery to end of logs * 
* operations when table row compression is being used.  The    * 
* runtime operational sequence of events include: load replace * 
* resetdictionary followed by reorg table keepdictionary.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.07.003                              * 
****************************************************************
Local Fix:
available fix packs:
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 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 Version 9.07.003
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2010
16.09.2010
16.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.7.003
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList