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

INPLACE REORG FAILS IN SQLDFIX2OR3PAGES RESULTING IN AN INSTANCE CRASH

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
An inplace table reorg may fail in sqldFix2or3Pages() resulting 
in an instance crash due.  You will 
see the following message in the db2diag.log: 
 
2011-11-03-01.01.59.957800-240 I280843A489        LEVEL: Severe 
PID     : 3116                 TID  : 2200940046672PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-17390              APPID: *LOCAL.DB2.111103050148 
AUTHID  : DB2INST1 
EDUID   : 201                  EDUNAME: db2reorg (SAMPLE) 0 
FUNCTION: DB2 UDB, data management, sqldFix2or3Pages, probe:470 
MESSAGE : ZRC=0x00002712=10002 
DATA #1 : <preformatted> 
Check Page for space failed 
 
An example stack: 
 
  0x00000200012C933E _Z16sqldFix2or3PagesP13SQLD_DFM_WORKS0_S0_i 
+ 0x0a7a 
  0x00000200012A82EA _Z20sqldFillNormalRecordP13SQLD_DFM_WORKS0_ 
+ 0x0512 
  0x00000200012BABFA 
_Z11sqldOLRFillP8SQLD_CCBPiS1_P18SQLD_OLR_INTERRUPT + 0x0cca 
  0x00000200012BF564 
_Z20sqldOnlineTableReorgP8sqeAgenttthmitPciS1_iP9SQLP_LSN8S3_s + 
0x3548 
  0x000002000141047E _Z26sqleIndCoordProcessRequestP8sqeAgent + 
0x0742 
  0x000002000143C43C _ZN8sqeAgent6RunEDUEv + 0x08e4
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any using inplace reorg                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fixpack 1                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 Fixpack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
05.11.2012
05.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList