|
Problem IT05280
|
Status: Closed |
BAD PAGE ERROR "FOLLOWED REORGPOINTER BUT NO OLR IN PROGRESS!" FOLLOWING INPLACE TABLE REORG IN PURESCALE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
On a pureScale system with explicit hierarchical locking (EHL)
enabled, after performing an inplace table reorg on a table, a
subsequent insert, delete, or update operation on that table may
fail with SQLCODE -902. You will see a message in the
db2diag.log similar to the following; a bad page error will be
reported, and the database will be shut down.
2014-10-09-02.04.05.950674-240 I326019441A623 LEVEL:
Severe
PID : 14614612 TID : 292803 KTID :
6422981
PROC : db2sysc 0
INSTANCE: dbuser NODE : 000 DB : SAMPLE
APPHDL : 0-3404 APPID:
9.26.96.91.34765.141009064344
AUTHID : DBUSER HOSTNAME: serverxxx
EDUID : 292803 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldFetchOverflow,
probe:2098
MESSAGE : Followed REORGPOINTER but no OLR in progress!
DATA #1 : Hexdump, 8 bytes
0x0700000374FFC460 : 0000 0000 0030 001B
.....0.. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of explicit hierarchical locking in pureScale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
To avoid hitting this issue, disable explicit hierarchical
locking by setting the database configuration parameter
OPT_DIRECT_WORKLOAD to no. Once the problem is encountered,
DB2 support must be contacted to fix this issue, there is no
local fix. |
| Solution |
Problem was first fixed in DB2 UDB version 10.5 fix pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.10.2014
15.12.2014
15.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
