DB2 - Problembeschreibung
Problem IC80012 | Status: Geschlossen |
SYSPROC.ADMIN_DROP_SCHEMA FAILS WITH SQL0478 IN DATABASE ENABLED FOR ORACLE COMPATIBILITY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Calling ADMIN_DROP_SCHEMA will return -478 / SQL0478 in the error schema and error table in databases created with Oracle compatibility features enabled. To Reproduce: db2set DB2_COMPATIBILITY_VECTOR=ORA db2stop db2start /* Oracle compatibility must be enabled for this database */ db2 "create db test" db2 "connect to test" db2 "create table s.t(c1 int)" db2 "call sysproc.admin_drop_schema('S', NULL, 'E', 'E')" /* Select from the error schema and error table, this contains * -478/SQL0478 error because the call to ADMIN_DROP_SCHEMA failed */ db2 "select * from e.e" /* succeeds after the schema name is padded with 7 blanks */ db2 "call sysproc.admin_drop_schema('S ', NULL, 'E', 'E')" db2 "terminate" db2stop | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 Fixpack 6. * **************************************************************** | |
Local-Fix: | |
Pad the schema name with blanks if it is less than 8 characters. For example if the schema name is REX, then it should be padded with 5 blank chars so that the total length is 8 characters. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
This was first fixed in v9.7 Fixpack 6. This is a server side fix which must be applied to the DB2 database server. | |
Workaround | |
See LOCAL FIX. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84347 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.11.2011 04.06.2012 04.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |