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 IC81663 Status: Geschlossen

EXTENT RECLAIM ON MDC TABLES MAY RETURN SQL0984C AND CAUSE THE INSTANCE
CRASH.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
SQL0984C may occur when doing extent reclaim on MDC tables, such 
as: 
 
CALL SYSPROC.ADMIN_MOVE_TABLE('SCHEMA', 'TABLENAME', '', '', '', 
'', '', '', '', '', 'MOVE'); 
 
This may result in: 
 
SQL0984C  COMMIT or ROLLBACK was not successful. Subsequent SQL 
statements cannot be processed. 
 
The database then undergoes crash recovery. 
 
The following conditions must be met for the problem to occur: 
 
1) Extent reclaim (e.g. reorg, admin_move_table) of an MDC 
table. 
2) The table must be located in an old-type DMS tablespace, i.e. 
a DMS table space created before 9.7 and migrated to 9.7 
 
From db2diag.log, the error starts like this: 
2011-10-14-09.35.30.079025-660 I3934177A503       LEVEL: Error 
PID     : 475282               TID  : 13610       PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000         DB   : 
sample 
APPHDL  : 0-62052              APPID: *LOCAL.testdb.111013203449 
AUTHID  : testdb 
EDUID   : 13610                EDUNAME: db2agent (FDB) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapObj2Pool, 
probe:840 
MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND 
          "EMP MAP INFO NOT FOUND" 
 
2011-10-14-09.35.30.079198-660 I3934681A551       LEVEL: Error 
PID     : 475282               TID  : 13610       PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000         DB   : 
sample 
APPHDL  : 0-62052              APPID: *LOCAL.testdb.111013203449 
AUTHID  : testdb 
EDUID   : 13610                EDUNAME: db2agent (FDB) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapObj2Pool, 
probe:840 
DATA #1 : String, 119 bytes 
 Obj={pool:34;obj:1963;type:0} State=x37 Parent={34;1963}, 
EM=125038, PP0=125040 Page=1 Cont=0 Offset=125040 BlkSize=3 
 
The top stack trace: 
 
MarkDBBad 
sqldmpnd 
sqlptppl 
sqlptppl 
sqlpxcm1 
sqlrrcom_dps 
sqlrrcom 
sqlrr_commit
Problem-Zusammenfassung:
See APAR Description
Local-Fix:
1. Avoid extent reclaim such as  "reorg table <tablename> 
reclaim extents only allow write access" 
OR 
2. db2set DB2_HASH_PURGE_THRESH=0 
A side effect is a potentially slower performance when dropping 
small tables, accompanied with a possible latch 
contention. However, if small tables are not being dropped 
frequently, this workaround will be acceptable. Setting 
DB2_HASH_PURGE_THRESH=0 reverts the performance of dropping 
small tables to the same level as pre-9.7 releases.
verfügbare FixPacks:
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

Lösung
Problem first fixed in DB2 for Linux, UNIX, and Windows 9.7 Fix 
Pack 6
Workaround
See APAR Description
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84453 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.02.2012
06.06.2012
06.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.6 FixList