|
Problem IC75205
|
Status: Closed |
THE INSTANCE MAY CRASH WHEN TRYING TO ADD A TABLE SPACE CONTAINER THAT HAS BEEN USED PREVIOUSLY BY THE SAME DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When attempting to add a table space using a file or path
container, and the container has previously been used by the
same database, the instance may crash a similar stack as below:
0 sqlbDMSAddContainerRequest
1 sqlbDMSCreatePool
2 sqlbSetupPool
3 sqlbCreatePool
4 sqldPoolCreate
5 sqlrlcts
6 sqlnq_create_tablespace_end
7 sqlnq_create_tablespace_stmt
8 sqlnp_smactn
9 sqlnp_parser
10 sqlnp_main
This happens when the user attempts to use either a path
containing a stale container tag file (SQLNAM.TAG), or a file
container that has previously been used by the database, but is
not in use any longer (for example old tablespace container
restored from a filesystem backup). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* THE INSTANCE MAY CRASH WHEN TRYING TO ADD A TABLE SPACE *
* CONTAINER THAT HAS BEEN USED PREVIOUSLY BY THE SAME DATABASE *
****************************************************************
* PROBLEM DESCRIPTION: *
* When attempting to add a table space using a file or path *
* container, and the container has previously been used by the *
* same database, the instance may crash a similar stack as *
* below: *
* *
* *
* 0 sqlbDMSAddContainerRequest *
* 1 sqlbDMSCreatePool *
* 2 sqlbSetupPool *
* 3 sqlbCreatePool *
* 4 sqldPoolCreate *
* 5 sqlrlcts *
* 6 sqlnq_create_tablespace_end *
* 7 sqlnq_create_tablespace_stmt *
* 8 sqlnp_smactn *
* 9 sqlnp_parser *
* 10 sqlnp_main *
* *
* This happens when the user attempts to use either a path *
* containing a stale container tag file (SQLNAM.TAG), or a *
* file *
* container that has previously been used by the database, but *
* is *
* not in use any longer (for example old tablespace container *
* restored from a filesystem backup). *
****************************************************************
* RECOMMENDATION: *
* Problem first fixed in DB2 UDB 9.7 FixPack 5. *
**************************************************************** |
| Local Fix: |
For path containers, remove the old tag file (SQLTAG.NAM). For
file containers, avoid using old container files containing a
stale tag. Use a brand new file instead. |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.03.2011
23.12.2011
23.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
