|
Problem IT21789
|
Status: Closed |
DB2 MIGHT INCORRECTLY TRY TO ADD CONTAINER WITH A DUPLICATE NAME
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The issue results in the following db2diag.log entry:
2016-10-09-21.11.59.258292+120 I1022150E689 LEVEL:
Error
PID : 53073 TID : 140509368542976 PROC :
db2sysc 0
INSTANCE: db2jkl NODE : 000 DB : JKL
APPHDL : 0-36330 APPID:
10.0.0.1.16828.161009134702
AUTHID : SAPJKL HOSTNAME: server
EDUID : 1536 EDUNAME: db2agent (JKL) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbDMSAddContainerRequest, probe:867
MESSAGE :
ZRC=0x8002003D=-2147352515=SQLB_CONTAINER_ALREADY_ADDED
"Duplicate container"
DATA #1 :
Container
/db2/JKL/sapdata1/db2jkl/NODE0000/JKL/T0000010/C0000004.LRG
already used by tablespace JKL#BTABD
Root cause might be:
In AS when a rebalance occurs via explicit rebalance or implicit
rebalance from ALTER TABLESPACE USING STOGROUP, if a disk error
occurs when allocating containers the ID for the next container
for the tablespace is supposed to be restored to the original
value before the container operations. However the value is
incorrectly restored. If the retry of the container operations
succeeds, the incorrect ID for the next container is written to
disk. If a new container is added and one already exists with
that container name the original db2diag.log message is hit. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 11.1 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT17876
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.08.2017
10.10.2017
10.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
