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

IN RARE TIMING SCENARIOS, LOAD UTILITY INTO A RANGE PARTITIONED TABLE MAY
TRAP WITH BAD PAGE ERROR IN SQLB_VERIFY_PAGE

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
When using Load utility to add data into a range partitioned 
table, a BAD PAGE error can be reported by one of the db2lbm 
processes. 
db2diag.log will include an entry similar to this:: 
 
2010-02-05-02.24.11.305740+540 I60623A3957        LEVEL: Severe 
PID     : 1151192              TID  : 511867      PROC : db2sysc 
0 
INSTANCE: XXXXXXXX             NODE : 000         DB   : XXXXX 
APPHDL  : 0-18593              APPID: 
XXX.XXX.XXX.XXX.41515.100204113503 
AUTHID  : XXXXX 
EDUID   : 511867               EDUNAME: db2lbm0 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, 
probe:2 
MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad" 
          DIA8400C A bad page was encountered. 
 
Stack trace generated by error may contain entries like this: 
 
sqlb_verify_page 
[...] 
sqluDirectRead 
sqluTransformSendToCopyRequest 
sqluSetCBitsAndWriteBuf 
sqlulBMCont 
sqlulbuf 
sqloEDUEntry 
 
 
The problem may be more suseptible when the COPY YES option is 
used. 
Per usual Load recovery usage, execute a Load Terminate to bring 
the table back to consistent state, then you can try the Load 
again.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See the APAR description.                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.5 fix pack 6.                   * 
****************************************************************
Local-Fix:
Use DISK_PARALLELISM 1 to avoid the problem (this may have some 
performance impact). 
Avoiding COPY YES option may also reduce the probability of 
hitting the problem.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.04.2010
17.05.2010
17.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version