|
Problem IC62914
|
Status: Closed |
SQL0299N ON CREATE TABLESPACE AFTER CRASH DURING CREATE TABLESPACE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If DB2 crashes during a CREATE TABLESPACE statement, a
subsequent attempt to create the table space after the crash
might fail due to DB2 not properly cleaning up containers from
the crashed CREATE TABLESPACE statement. After the
second attempt to create the table space, the user will see
the message:
DB21034E The command was processed as an SQL statement because
it was not a valid Command Line Processor command. During SQL
processing it returned:
SQL0299N Container is already assigned to the table space.
SQLSTATE=42731
The db2diag.log will contain several messages showing that the
CREATE TABLESPACE failed with a ZRC of
SQLB_CONTAINER_ALREADY_ADDED and a stack similar to the
following:
sqlbDMSAddContainerRequest
sqlbASSetPoolContsForDMS
sqlbASDefineContainersForDMS
sqlbDMSCreatePool
sqlbCreatePool
sqldPoolCreate |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* If DB2 crashes during a CREATE TABLESPACE statement, a *
* *
* subsequent attempt to create the table space after the crash *
* *
* might fail due to DB2 not properly cleaning up containers *
* from *
* the crashed CREATE TABLESPACE statement. After the *
* second attempt to create the table space, the user will see *
* *
* the message: *
* *
* DB21034E The command was processed as an SQL statement *
* because *
* it was not a valid Command Line Processor command. During *
* SQL *
* processing it returned: *
* SQL0299N Container is already assigned to the table space. *
* *
* SQLSTATE=42731 *
* *
* The db2diag.log will contain several messages showing that *
* the *
* CREATE TABLESPACE failed with a ZRC of *
* SQLB_CONTAINER_ALREADY_ADDED and a stack similar to the *
* *
* following: *
* *
* sqlbDMSAddContainerRequest *
* sqlbASSetPoolContsForDMS *
* sqlbASDefineContainersForDMS *
* sqlbDMSCreatePool *
* sqlbCreatePool *
* sqldPoolCreate *
* *
* If this occurs, try to create the table space a third time. *
* The second *
* attempt to create the table space will have cleaned up the *
* containers *
* from the first crashed attempt. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
Try to create the table space a third time. The second attempt
to create the table space will have cleaned up the containers
from the first crashed attempt. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.09.2009
24.12.2009
24.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
