|
Problem IC81307
|
Status: Geschlossen |
DB2 ABEND ON DROP TABLESPACE COMMAND |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 FP4 and earlier. *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 will abend if a DROP TABLESPACE command is issued after *
* SMS table space file SQLTAG.NAM has been removed. 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 *
* *
* After the crash, DB2 will generate the stack trace similar *
* to *
* one below: *
* *
* 0 ossDumpStackTraceEx *
* 1 OSSTrapFile::dumpEx *
* 2 sqlo_trce *
* 3 sqloEDUCodeTrapHandler *
* 4 __restore_rt *
* 5 sqlbAdjustPathsForReleasedContainers *
* 6 sqlbSMSFreePoolContainers *
* 7 sqlbSMSDropPool *
* 8 sqlbDropPoolAct *
* 9 storMgrAction *
* 10 sqldmpnd *
* 11 sqlptppl *
* 12 sqlpxcm1 *
* 13 sqlrrcom *
* 14 sqlrr_commit *
* 15 sqljs_ddm_rdbcmm *
* 16 sqljsParseRdbAccessed *
* 17 sqljsParse *
* 18 sqljsSqlam *
* 19 sqljsDriveRequests *
* 20 sqljsDrdaAsInnerDriver *
* 21 sqljsDrdaAsDriver *
* 22 sqeAgent::RunEDU *
* 23 sqzEDUObj::EDUDriver *
* 24 sqlzRunEDU *
* 25 sqloEDUEntry *
* 26 start_thread *
* 27 __clone *
* *
* *
* The root cause of problem is the lack of one or more table *
* space *
* control files. The database should be considered as *
* inconsistent *
* in this case as at least one table space is damaged. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FPn *
**************************************************************** |
| 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 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
|
| Lösung |
Problem was fixed in DB2 v9.7 FPn |
| Workaround |
N/A |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84352
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.02.2012
04.06.2012
04.06.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.6
|
 |
