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

CRASH RECOVERY FAIL WHEN FREEING DELETE PENDING EXTENTS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In rare condition, Crash recovery is failing when freeing delete 
pending extents 
 
db2diag.log is showing the following: 
2013-11-05-14.14.58.030000+060 I41604F509         LEVEL: Warning 
PID     : 2580                 TID  : 4028        PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 4028                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410 
MESSAGE : Crash recovery started. LowtranLSN 000001412BE0A4D4 
MinbuffLSN 
          000001411F37A40A 
 
2013-11-05-14.14.58.046000+060 E42115F462         LEVEL: Warning 
PID     : 2580                 TID  : 4028        PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 4028                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410 
MESSAGE : ADM1530E  Crash recovery has been initiated. 
 
2013-11-05-14.14.58.046000+060 I42579F536         LEVEL: Warning 
PID     : 2580                 TID  : 4028        PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 4028                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:1182 
MESSAGE : numWOCB set to 
DATA #1 : Hexdump, 8 bytes 
0x000000001A9568F0 : 8000 0000 0000 0000 
........ 
 
2013-11-05-14.14.58.061000+060 I43117F506         LEVEL: Warning 
PID     : 2580                 TID  : 4028        PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 4028                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000 
DATA #1 : <preformatted> 
Using parallel recovery with 3 agents 59 QSets 177 queues and 64 
chunks 
 
2013-11-05-14.14.58.077000+060 E43625F501         LEVEL: Warning 
PID     : 2580                 TID  : 11044       PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 11044                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, 
probe:880 
DATA #1 : <preformatted> 
Resetting max shredder memory to 14509152 from 18124800 
 
2013-11-05-14.15.08.842000+060 I44128F623         LEVEL: Warning 
PID     : 2580                 TID  : 11044       PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 11044                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbRedoFreeExtents, 
probe:820 
DATA #1 : String, 70 bytes 
Informational: Redoing FREE_PENDDEL but no extents are pending 
delete. 
DATA #2 : Hexdump, 8 bytes 
0x000000045F1FA348 : 0605 0F00 0040 FD00 
.....@.. 
 
2013-11-05-14.15.08.858000+060 I44753F507         LEVEL: Warning 
PID     : 2580                 TID  : 11044       PROC : 
db2syscs.exe 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
127.0.0.1.2237.131105131438 
AUTHID  : db2inst1 
EDUID   : 11044                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
DATA #1 : String, 19 bytes 
sqlbRedoFreeExtents 
DATA #2 : String, 4 bytes 
sqlb 
 
 
and trap file: 
 
Exception C0000005 Occurred 
Exception Address = 0000000001D1B1A0 
 
<sqlpCopyLsn> 
<C:\db2_v97fp8\ntx64\s130316\engn\include\sqlpglob.h:714> 
<sqlbReduceLastInitSMPExtent> <sqlbSMP.C:4510> 
<sqlbFindNewHighWaterMark> <sqlbSMP.C:4077> 
<sqlbRedoFreeExtents> <sqlblog.C:895> 
<sqlbRedo> <sqlblog.C:4032> 
<sqldmrdo> <sqldmrdo.C:875> 
<sqlpRecDbRedo> <sqlprfwd.C:2336> 
<sqlprProcDPSrec> <sqlprfwd.C:4368> 
<sqlpPRecReadLog> <sqlprfwd.C:6492> 
<sqlpParallelRecovery> <sqlprecm.C:1503> 
<sqleSubCoordProcessRequest> <sqlescgt.C:1006> 
<sqeAgent::RunEDU> <sqle_agent.C:3983> 
<sqlzRunEDU> <sqlz_edu_obj.C:35> 
<sqloEDUEntry> <sqloedu.C:3456>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 Cancun Release 10.5.0.4 (also known as * 
* Fix Pack 4) or higher.                                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Cancun Release 10.5.0.4(also known as Fix 
Pack 4).
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.11.2013
29.10.2014
29.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList