DB2 FOR LUW / DB2FORLUW / A50 - DB2

db2relocatedb or db2inidb ... relocate using <relocate.conf> 
might construct wrong container path name(s). 
 
This issue can happen under the following sceanrio: 
 
You might have one or more tablespace(s) that contains a mix of 
DMS and Automatic Storage managed containers. This can happen 
because that tablespace was later altered to be MANAGED BY 
AUTOMATIC STORAGE. But you haven't done the rebalance yet. 
 
And 
 
You try to relocate the container paths of such a tablespace 
using the CONT_PATH and STORAGE_PATH clause in the relocate 
config file. 
 
The relocate will run successfully but you might end up with 
wrong (corrupted) container path names. This will also cause 
tablespace activation issues like tablespace state going offline 
and invalid container tag id's. The issue is only with the DMS 
container path names, but not the Automatic Storage container 
path names.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************

Run ALTER TABLESPACE ... REBALANCE before the relocatedb step

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.5 Fix Pack 4.

not known / see Local fix

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

26.09.2013
09.09.2014
09.09.2014