|
Problem IT26871
|
Status: Closed |
TABLE SPACE OFFLINE AFTER "ALTER TABLESPACE ... MANAGED BY AUTOMATIC STORAGE" COMMAND
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The problem can be reproduced with these steps:
1) A non-automatic storage table space TS1 has a container named
/home/db2inst1/db2inst1/NODE0000/SAMPLE/T0000004/C0000000.LRG,
which is the same name/path as if it were created as an
automatic storage table space.
2) ALTER TABLESPACE TS1 MANAGED BY AUTOMATIC STORAGE
-> It fails with SQL0299N
3) ALTER TABLESPACE TS1 MANAGED BY AUTOMATIC STORAGE
-> It succeeds
4) Check db2diag.log. The table space is offline due to the
following message:
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 : |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher *
**************************************************************** |
| Local Fix: |
Before altering the table space to automatic storage make sure
the container name is different than if it was an automatic
storage table space container. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT26339
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.11.2018
16.01.2020
16.01.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
