home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84352 Status: Closed

DB2 ABEND ON DROP TABLESPACE COMMAND

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 will abend if a DROP TABLESPACE command is issued after the 
SMS table space file SQLTAG.NAM has been renamed. The error 
message below is the symptom of the crash: 
 
$ db2 drop tablespace SYSTOOLSTMPSPACE 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the specified request because of an error or a forced 
interrupt.  SQLSTATE=55032 
 
The trap file generated during the abend will contain a stack 
trace similar to the one below: 
 
sqlbAdjustPathsForReleasedContainers 
sqlbSMSFreePoolContainers 
sqlbSMSDropPool 
sqlbDropPoolAct 
 
The root cause of the problem is the renaming of the SQLTAG.NAM 
file. Note that it is not allowed to manipulate database control 
files manually. The database should be considered inconsistent 
in this case as at least one table space is damaged.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running DB2 v9.10 GA                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10 FP1                                       * 
****************************************************************
Local Fix:
Rename the SQLTAG.NAM file back, or perform a table space level 
restore if this file cannot be recovered otherwise.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The fix was made to DB2 v10 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
13.11.2012
13.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList