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 IC65904 Status: Geschlossen

DROP SCHEMA RETURNS SQL0901N WITH REASON "UNKNOW OBJECT TYPE"
INSTEAD OF SQL0478N

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When dropping a schema (ie. DROP SCHEMA <schemaName> RESTRICT), 
you are required to have all objects removed from that schema 
prior to being allowed to drop it. 
 
This APAR addresses an issue where the DROP SCHEMA statement 
returns SQL0901N with reason "Unknow object type" instead of 
returning the expected sqlcode SQL0478N with the name and type 
of the object that still remains in the schema.  This occurs 
when there remains one or more tables that are either a) a 
Created Global Temporary Table (CGTT) or b) a table that is in 
detached state due to an alter table detach operation.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA through to Fix Pack 1 servers, on     * 
* Linux, Unix or Windows platforms.                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Created Global Temporary tables along with tables in         * 
* detached state were missing functionality for returning the  * 
* correct SQL0478N error.                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update your instance to DB2 Version 9.7 Fix Pack 2 or see    * 
* local fix for more details.                                  * 
****************************************************************
Local-Fix:
Identify all the table objects remaining in the SYSCAT.TABLES 
catalog view which belong to this schema, and drop each one of 
them. You can identify these objects with the following query: 
 
select tabschema, tabname, type from syscat.tables where 
tabschema='<schemaName>'
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.01.2010
08.04.2010
08.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList