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

SQL0901 FOUND IN DB2DIAG.LOG INDICATING "BAD ALLOCATION IN
TABLESPACE" FROM "SQLBMOVEHIGHESTEXTENT"

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In an edge case scenario it is possible for an extent movement 
to encounter a situation where there is no more space available 
and allocates a new extent above the table space High Water 
Mark.  This is considered an error condition which will rollback 
the outstanding work in the transaction and writing a severe 
error in the db2diag.log: 
 
2013-01-22-11.05.53.261174-300 I108545E1594          LEVEL: 
Severe 
PID     : 6605                 TID : 46914481416512  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : X 
APPHDL  : 0-28                 APPID: *LOCAL.DB2.130122160600 
AUTHID  : DB2INST1             HOSTNAME: localhost 
EDUID   : 1119                 EDUNAME: db2agent (X) 
FUNCTION: DB2 UDB, buffer pool services, sqlbMoveHighestExtent, 
probe:2776 
MESSAGE : ZRC=0x82020001=-2113798143=SQLB_NONSEVERE_PRGERR 
          "non-severe BPS programming error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
63992 
DATA #2 : Hex integer, 1 bytes 
0x00 
DATA #3 : SQLB_EXTENT_MOVEMENT_CB, 
PD_TYPE_SQLB_EXTENT_MOVEMENT_CB, 64 bytes 
  extentDescriptors:     0x00002aabce611fc0 
  lowestExtentToMove:                  7990 
  highestExtentToMove:                 7999 
  currentExtent:                       7999 
  lastExtent:                    4294967295 
  numberOfExtentsMoved:                   2 
  numberOfExtentsLeft:                    0 
  currentN:                              10 
  totalMoveTime:                      26363 
  moveBatchSize:                         10 
  reduceContFreq:                       100 
DATA #4 : signed integer, 8 bytes 
0 
DATA #5 : SQLB_EXTENT_DESC, PD_TYPE_SQLB_EXTENT_DESC, 40 bytes 
  oldLocation:                  7999 
  newLocation:            4294967295 
  objectPageNum:               63936 
  Obj: {pool:0;obj:0;type:0} Parent={0;0} 
  extentLatch:    0x00002aabce611fd8 
DATA #6 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
8 
 
2013-01-22-11.05.53.261712-300 E110140E545           LEVEL: Info 
PID     : 6605                 TID : 46914481416512  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : X 
APPHDL  : 0-28                 APPID: *LOCAL.DB2.130122160600 
AUTHID  : DB2INST1             HOSTNAME: localhost 
EDUID   : 1119                 EDUNAME: db2agent (X) 
FUNCTION: DB2 UDB, buffer pool services, sqlbLockAndMoveExtents, 
probe:4892 
MESSAGE : ADM6008I  Extents within table space "TS1"  (ID "3") 
have been moved. 
          Reason code = "0". 
 
2013-01-22-11.05.53.263996-300 I110686E666           LEVEL: 
Severe 
PID     : 6605                 TID : 46914481416512  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : X 
APPHDL  : 0-28                 APPID: *LOCAL.DB2.130122160600 
AUTHID  : DB2INST1             HOSTNAME: localhost 
EDUID   : 1119                 EDUNAME: db2agent (X) 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbExtentMovementEntryPoint, probe:5416 
MESSAGE : ZRC=0x82020001=-2113798143=SQLB_NONSEVERE_PRGERR 
          "non-severe BPS programming error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : <preformatted> 
Error in extent movement iCoord
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 3  * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

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