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

TURNING OFF AUTO-RESIZE WHILE THE SAME TABLE SPACE IS BEING EXTENDED MAY
RESULT IN UNREPLAYABLE LOG RECORD SEQUENCE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Assume a scenario like this: 
 
1) A DMS or AUTOMATIC STORAGE (for permanent data) table space 
partially filled with data, AUTORESIZE enabled. 
2) The user issues ALTER TABLESPACE ... REDUCE (optionally: 
MAX), causing the table space to shrink. 
3) The user attempts to insert new data, hence the table space 
will start to grow (AUTORESIZE enabled). 
4) While the grow operation is still in progress, the user 
issues ALTER TABLESPACE ... AUTORESIZE OFF from another session. 
5) The grow operation will finish now. 
 
If the timing is correct, these steps will result in a sequence 
of log records ordered in a way that cannot be replayed. If 
there is an attempt to replay this sequence (e.g. during 
ROLLFORWARD, HADR Standby, crash recovery), error 
"SQLB_NOT_ALLOWED_ROLLFORWARD_P" will be reported in the DB2 
diagnostic log, and the database will be shut down. Example: 
 
db2diag.log 
=========== 
2013-03-10-04.00.38.231675-240 I22886351E1467        LEVEL: 
Error 
PID     : 27644                TID : 140359422174976 KTID : 
27711 
PROC    : db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: *LOCAL.DB2.130310075939 
HOSTNAME: myhostname 
EDUID   : 62                   EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, sqlbExtendObject, 
probe:387 
MESSAGE : 
ZRC=0x80020033=-2147352525=SQLB_NOT_ALLOWED_ROLLFORWARD_P 
          "Access not allowed. Tblspc RF Pending." 
 
<...skipping...> 
 
2013-03-10-04.00.38.242071-240 I22887819E554         LEVEL: 
Severe 
PID     : 27644                TID : 140359422174976 KTID : 
27711 
PROC    : db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: *LOCAL.DB2.130310075939 
HOSTNAME: myhostname 
EDUID   : 62                   EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, data management, sqldomRedo, probe:1795 
RETCODE : 
ZRC=0x80020033=-2147352525=SQLB_NOT_ALLOWED_ROLLFORWARD_P 
          "Access not allowed. Tblspc RF Pending." 
 
<...skipping...> 
 
2013-03-10-04.00.38.747509-240 E22902916E1003        LEVEL: 
Critical 
PID     : 27644                TID : 140359455729408 KTID : 
27703 
PROC    : db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: *LOCAL.DB2.130310075939 
HOSTNAME: myhostname 
EDUID   : 54                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqleDoForceDBShutdownFODC, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: 
          "ForceDBShutdown". The instance may have been shutdown 
as a result.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 for Linux, UNIX, and Windows Fix * 
* Pack 3                                                       * 
****************************************************************
Local-Fix:
Avoid replaying the unexpected log record sequence. If restoring 
or in an HADR Standby environment, use a backup image created 
after the table space has been resized (i.e. after step 5 
described above). No applicable workaround in the case of crash 
recovery.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 10.1 for Linux, UNIX, and 
Windows Fix Pack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.04.2013
03.10.2013
03.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList