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

BAD PAGE ERROR "FOLLOWED REORGPOINTER BUT NO OLR IN PROGRESS!"
FOLLOWING INPLACE TABLE REORG IN PURESCALE.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
Problem was first fixed in DB2 UDB version 10.5 fix pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.10.2014
15.12.2014
15.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList