DB2 FOR LUW / DB2FORLUW / 970 - DB2

During roll forward of a classic (offline) table reorg that 
included the 'USE tablespace' clause, if the specified temporary 
tablespace is in roll forward pending state, the replay of the 
reorg will fail.  This will not happen with a full database 
restore, but with any type of restore that involves specifying a 
subset of tablespaces that includes the specified system 
temporary tablespace; for example, 'RESTORE DATABASE <name> 
REBUILD WITH ALL TABLESPACES IN IMAGE EXCEPT (some other 
tablespace)', or 'RESTORE DATABASE <name> TABLESPACE', either 
with no listed table spaces (meaning all are to be restored) or 
with a list that includes the specified temporary tablespace. 
 
You will see severe error messages in the db2diag.log that 
include the error 'SQLB_NO_TEMP_AVAIL'.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Any using any type of restore that involves specifying a     * 
* subset of tablespaces that includes a temporary tablespace   * 
* used by reorg.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to Version 9.7 Fixpack 9 or later                     * 
****************************************************************

Perform a full database restore without the REBUILD or 
TABLESPACE clauses, if possible.

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 Version 9.7 Fixpack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC90146 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

08.02.2013
30.12.2013
30.12.2013

9.7.FP9