DB2 - Problembeschreibung
Problem IC84352 | Status: Geschlossen |
DB2 ABEND ON DROP TABLESPACE COMMAND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
The fix was made to DB2 v10 FP1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2012 13.11.2012 13.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |