DB2 FOR LUW / DB2FORLUW / A50 - DB2

The problem could be reproduced with these steps

1) a NON-AS tablespace TBSP4 had a container named
/home/db2inst1/db2inst1/NODE0000/SAMPLE/T0000004/C0000000.LRG,
which is the same name/path as if it were created as an AS
tablespace

2) ALTER TABLESPACE TBSP4 MANAGED BY AUTOMATIC STORAGE
    it failed with sql0299n

3) ALTER TABLESPACE TBSP4 MANAGED BY AUTOMATIC STORAGE
   it succeed

4) Then check storage+tablespace,  the tablespace is offline.

5) in db2diag.log, we can find


2018-09-08-13.17.33.889445-300 I415126465A684      LEVEL: Error

PID    : 20316290            TID : 21576         PROC : db2sysc
0

INSTANCE: db2inst1            NODE : 000          DB  : SAMPLE

APPHDL : 0-353               APPID: *LOCAL.db2inst1.180908171848

AUTHID : DB2INST1            HOSTNAME: db2host1

EDUID  : 21576               EDUNAME: db2agent (SAMPLE) 0

FUNCTION: DB2 UDB, buffer pool services,
sqlbDMSAddContainerRequest, probe:867

MESSAGE :
ZRC=0x8002003D=-2147352515=SQLB_CONTAINER_ALREADY_ADDED

         "Duplicate container"

DATA #1 : 

6) and check the tablespace SQLSPCS.1/SQLSPCS.2, the container
definition for this tablespace is corrupted.

****************************************************************
* USERS AFFECTED:                                              *
* All Users                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to latest Db2 V11.1 fix pack.                        *
****************************************************************

before alter tablespace to AS, make sure the container name is
different with the one as if it is a AS tablespace container.

not known / see Local fix

forerunner  : 
follow-up : IT26871 

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

18.09.2018
07.11.2018
07.11.2018