|
Problem IC95250
|
Status: Closed |
INSPECT WITH THE INDEXDATA OPTION PANICS AFTER ENCOUNTERING AN INVALID RECORD ID |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5.0.3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
|
| Solution |
The problem is first fixed in DB2 version 10.5.0.3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
02.12.2013
02.12.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
