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

DATABASE MARKED BAD WHEN RUNNING AN ALTER TABLESPACE OPERATION WHILE THE
TABLESPACE IS IN A "REORGANIZATION IN PROGRESS" STATE

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
While the REORG utility is using a DMS temporary tablespace in 
order to store the REORG temporary data, a tablespace alter is 
issued against the same tablespace, either directly by the user, 
or in the form of the RESTORE/ROLLFORWARD DATABASE 
command, or in an HADR environment when the ALTER TABLESPACE 
log record reaches the Standby database. 
 
The connection will terminate with SQL1034C, and the database 
will be marked bad. The following messages will be written into 
the DB2 diagnostic log. The important eyecatcher is the presence 
of "134217727" (which translates to 0x7FFFFFF) in 
"sqlb_locate_extent, 
probe:235", indicating an overflow in the extent number. 
 
2010-09-28-14.33.42.152419-240 I504522A520        LEVEL: Error 
PID     : 507908               TID  : 25566       PROC : db2sysc 
0 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-35481              APPID: *LOCAL.DB2.100928182744 
EDUID   : 25566                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_locate_extent, 
probe:232 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
 
2010-09-28-14.33.42.162562-240 I505043A440        LEVEL: Error 
PID     : 507908               TID  : 25566       PROC : db2sysc 
0 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-35481              APPID: *LOCAL.DB2.100928182744 
EDUID   : 25566                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_locate_extent, 
probe:232 
DATA #1 : String, 28 bytes 
Displaying maps for pool <pool_id_displayed_here> 
 
<...skipping...> 
 
2010-09-28-14.33.42.164124-240 I506206A567        LEVEL: Severe 
PID     : 507908               TID  : 25566       PROC : db2sysc 
0 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-35481              APPID: *LOCAL.DB2.100928182744 
EDUID   : 25566                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_locate_extent, 
probe:235 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
DATA #1 : unsigned integer, 4 bytes 
134217727 
 
<...skipping...> 
 
2010-09-28-14.33.42.168488-240 I508365A515        LEVEL: Error 
PID     : 507908               TID  : 25566       PROC : db2sysc 
0 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-35481              APPID: *LOCAL.DB2.100928182744 
EDUID   : 25566                EDUNAME: db2redom (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbAlterPool, 
probe:110 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
 
The problem can manifest itself in several ways as explained 
below: 
 
A: In a HADR standby or when running a rollforward operation: 
1. The database must be replaying an ALTER TABLESPACE log 
record. 
2. The failing tablespace must be DMS temporary. 
3. The state of the failing tablespace (as displayed for example 
by LIST APPLICATIONS) must be "Reorganization in progress", i.e. 
0x400. 
 
B: Under regular runtime: 
1. Tablespace must be in a "Reorg in progress" state, i.e 0x400. 
2. An ALTER TABLESPACE is issued against the same tablespace 
 
 
Workaround: 
1) For ROLLFORWARD/HADR: if possible, restore the database from 
a backup image not 
containing any ALTER TABLESPACE log records created while the 
REORG utility may have been running. 
 
2) Regular runtime: restart the REORG utility and let it finish. 
The tablespace state will change back to "Normal" (0x0). At this 
point any ALTER TABLESPACE attempts should finish successfully.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DATABASE MARKED BAD WHEN RUNNING AN ALTER TABLESPACE         * 
* OPERATION                                                    * 
* WHILE THE TABLESPACE IS IN A "REORGANIZATION IN PROGRESS"    * 
* STATE                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 Fixpack 7                                * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Fixed in V9.5 Fixpack 7
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC75199 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2010
27.06.2011
27.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP7
Problem behoben lt. FixList in der Version
9.5.0.8 FixList