home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98005 Status: Geschlossen

DROPPING ALL INDEXES FROM INDEX OBJECT FOLLOWING REORG INDEX RECLAIM
EXTENTS MAY RETURN SQL1034C AND CAUSE INSTANCE ABEND

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
SQL1034C may occur when doing extent reclaim on index object and 
dropping all indexes within it, such as: 
 
REORG INDEXES ALL FOR TABLE T1 CLEANUP RECLAIM EXTENTS 
DROP INDEX INDX1 
... 
DROP INDEX INDXN 
 
This may result in: 
 
SQL1034C  The database is damaged.  All applications processing 
the database 
have been stopped.  SQLSTATE=58031 
 
The database then must undergo crash recovery. 
 
The following conditions must be met for the problem to occur: 
 
1) Extent reclaim of an index object. 
2) The index must be located in an old-type DMS tablespace, i.e. 
a DMS table space created before 9.7 and migrated to the current 
release. 
 
From db2diag.log, the error starts like this: 
 
2013-08-15-14.57.27.937959-240 I167322E4722          LEVEL: 
Severe 
PID     : 16643                TID : 46913369925952  KTID : 
16664 
PROC    : db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-44                 APPID: 
*LOCAL.db2inst1.130815185723 
AUTHID  : DB2INST1             HOSTNAME: myhostname 
EDUID   : 18                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbPurgeOrFlushAllPagesInSmallRange, probe:8555 
MESSAGE : ZRC=0x8402001A=-2080243686=SQLB_EMP_MAP_INFO_END "EMP 
MAP INFO END" 
DATA #1 : String, 38 bytes 
Error mapping object page to pool page 
 
The top stack trace: 
 
sqlbPurgeOrFlushAllPagesInSmallRange 
sqlbPurgeObjectLocal 
sqlbPurgeObject 
sqldmpnd 
sqlptppl 
sqlpxcm1 
sqlrrcom_dps 
sqlrrcom 
sqlrr_commit
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 for Linux, UNIX, and Windows Fix Pack 4  * 
****************************************************************
Local-Fix:
1. Avoid extent reclaim, OR 
2. db2set DB2_HASH_PURGE_THRESH=0. A side effect is a 
potentially slower performance when dropping small objects, 
accompanied with a possible latch contention. However, if small 
objects are not being dropped frequently, this workaround will 
be acceptable. Setting DB2_HASH_PURGE_THRESH=0 reverts the 
performance of dropping small objects to the same level as 
pre-9.7 releases.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 10.1 for Linux, UNIX, and Windows Fix 
Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.11.2013
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList