home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC73139 Status: Geschlossen

DROPPING TEMPORARY TABLESPACES IN WHICH TABLE INDEXES ARE DEFINE D TO USE
CAN SUBSEQUENTLY LEAD TO THE DATABASE BEING MARKED BAD

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Specifying table indexes to be created in temporary table spaces 
should be blocked by SQL0284N, but currently it is not. If a 
temporary table space is defined for which table indexes should 
reside, then dropping the temporary table space later on will 
cause subsequent actions on the table to mark the database bad. 
 
Sample output: 
 
drop tablespace tmpsys 
DB20000I  The SQL command completed successfully. 
 
select * from t 
SQL1034C  The database is damaged.  All applications processing 
the database have been stopped.  SQLSTATE=58031 
 
Other operations like DROP would be blocked similarly. 
 
drop table t 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1034C  The database is damaged.  All applications processing 
the database have been stopped.  SQLSTATE=58031
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA though Fix Pack 3 servers on Linux,   * 
* Unix, and Windows platforms specifying a temporary table     * 
* space for the INDEX IN clause for the CREATE TABLE           * 
* statement.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When creating a table, a temporary table space cannot be     * 
* specified for which the indexes on the table should be       * 
* created. If a temporary table space is specified and later   * 
* on dropped, any action on the table will cause the database  * 
* to abnormally stopped with SQL1034C.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 4 or see "Local Fix" * 
* portion for work-arounds.                                    * 
****************************************************************
Local-Fix:
If the temporary table space is dropped, recreate the temporary 
table space with the same name and follow the below step. 
If the temporary table space exists, drop and recreate the 
table, and ensure the table space name specified INDEX in clause 
is NOT a temporary table space. 
 
DO NOT attempt to drop the table unless the temporary table 
space exists.
verfügbare FixPacks:
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 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
The complete fix for this problem first appears in DB2 LUW 
Version 9.7 Fix Pack 4 and all the subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC73202 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.12.2010
28.04.2011
28.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList