DB2 FOR LUW / DB2FORLUW / 970 - DB2

Log records for an ALTER TABLESPACE operation may be skipped 
during redo (e. g. ROLLFORWARD, HADR Standby) if the on-disk 
table space control files indicate that the present version of 
the table space is newer than the log records. This situation 
can only happen under very rare timing conditions, for example 
after running several uncommitted ALTER TABLESPACE operations 
and then rolling them back in a way that some of the ALTERs can 
be skipped (older than minBuffLSN) and some can not (newer). 
This condition is hard to achieve. 
 
Due to an issue with checking whether we are in the redo mode 
(e. g. ROLLFORWARD, HADR Standby), DB2 may erroneously attempt 
to replay some of the log records that should have be skipped. 
This result in error SQLB_AS_CLAUSE_NOT_ALLOWED followed by a 
forced database shutdown. 
 
Sample db2diag.log: 
=================== 
2011-10-31-05.54.03.198238-240 I32448307E538        LEVEL: Error 
PID    : 25899                TID  : 139789672113920KTID : 26707 
PROC    : db2sysc 
INSTANCE: db2inst1              NODE : 000          DB  : SAMPLE 
APPHDL  : 0-131                APPID: *LOCAL.DB2.111031095401 
EDUID  : 494                  EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, sqlbAlterPool, probe:65 
MESSAGE : ZRC=0x800201A3=-2147352157=SQLB_AS_CLAUSE_NOT_ALLOWED 
         "A tablespace clause was not allowed in the command or 
statement." 
 
<...skipping...> 
 
2011-10-31-05.54.03.334110-240 I32451461E614        LEVEL: Error 
PID    : 25899                TID  : 139789672113920KTID : 26707 
PROC    : db2sysc 
INSTANCE: db2inst1              NODE : 000          DB  : SAMPLE 
APPHDL  : 0-131                APPID: *LOCAL.DB2.111031095401 
EDUID  : 494                  EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, recovery manager, sqlpRecDbRedo, probe:155 
MESSAGE : ZRC=0x800201A3=-2147352157=SQLB_AS_CLAUSE_NOT_ALLOWED 
         "A tablespace clause was not allowed in the command or 
statement." 
DATA #1 : <preformatted> 
REDO failed on LSO(LSN) 7094703215 (000000000162D898) 
 
<...skipping...> 
 
2011-10-31-05.54.03.699318-240 E32459292E967        LEVEL: 
Critical 
PID    : 25899                TID  : 139789646948096KTID : 26708 
PROC    : db2sysc 
INSTANCE: db2inst1              NODE : 000          DB  : SAMPLE 
APPHDL  : 0-131                APPID: *LOCAL.DB2.111031095401 
EDUID  : 495                  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. 
         "Automatic" FODC (First Occurrence Data Capture) has 
been invoked and 
         diagnostic information has been recorded in directory 
 
"/home/db2inst1/sqllib/db2dump/FODC_ForceDBShutdown_2011-10-31-0 
5.54.0 
         3.699116_0000/". Please look in this directory for 
detailed evidence 
         about what happened and contact IBM support if 
necessary to diagnose 
         the problem.

**************************************************************** 
* USERS AFFECTED:                                              * 
* See APAR description                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 for Linux, Unix, and Windows version 9.7 Fix  * 
* Pack 6.                                                      * 
****************************************************************

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 for Linux, Unix, and Windows version 
9.7 Fix Pack 6.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.03.2012
04.06.2012
04.06.2012

9.7.,
9.7.FP6