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

INSPECT WITH THE INDEXDATA OPTION PANICS AFTER ENCOUNTERING AN INVALID
RECORD ID

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When running the INSPECT command with the INDEXDATA option, the 
INSPECT tool might crash and bring down the database if it 
encounters a record ID in the index that points to a page beyond 
the end of the table space in which the table resides.  The 
following message will appear in the db2diag.log: 
 
2013-03-11-13.15.08.375329-240 I4470761E572        LEVEL: Error 
PID     : 19456                TID  : 469975076641 PROC:db2sysc 
0 
INSTANCE: db2inst1             NODE : 000          DB   : sample 
APPHDL  : 0-25448              APPID: 10.191.38.43.38338.1303111 
AUTHID  : ABCDEF 
EDUID   : 643                  EDUNAME: db2agent (LDDW) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbLatchPoolRange, 
probe:20 
MESSAGE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR 
          "Page number exceeds max -8100" 
          DIA8709E Segmented table page number was too high. 
 
There will also be a signal #6 with the following functions on 
the stack: 
 
sqle_panic 
sqlb_panic 
sqlbLatchPoolRange 
sqlbReadPage 
sqlbGetPageFromDisk 
sqlbfix 
sqldFetchDirect 
... 
sqlirdk 
sqldIndexFetch 
sqldRowFetch 
dartScanINXDAT 
... 
dartInspect 
sqlrinspect 
sqlrr_inspect 
 
The fix will have INPSECT report the error without bringing down 
the database.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.0.9.                              * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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
The problem is first fixed in DB2 version 9.7.0.9.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95250 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.04.2013
16.12.2013
16.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.0.9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList