DB2 - Problem description
| Problem IC84137 | Status: Closed |
ADMIN_DROP_SCHEMA FAILED WHEN ONLY INOPERATIVE OBJECTS EXIST IN A SCHEMA | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
When only inoperative objects exist in a schema, the stored
procedure ADMIN_DROP_SCHEMA does not remove the schema and
dependent objects correctly.
Below is the script that creates a database and tests
ADMIN_DROP_SCHEMA. It first creates a table and a view, then
drops the table. This gives an error SQL0478N, and does not
remove the view.
--drop database tmp;
create database tmp;
connect to tmp;
call sysproc.sysinstallobjects('DB2AC', 'C', null, null);
create table sven.test(x integer not null, y integer);
create view sven.v as select * from sven.test;
drop table sven.test;
call sysproc.admin_drop_schema('SVEN', null, 'E', 'E');
select * from e.e;
list tables for schema sven; | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Versions Prior to V10.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Drop underlying objects and the schema manually using * * corresponding DROP statements. * **************************************************************** | |
| Local Fix: | |
Drop underlying objects and the schema manually using corresponding DROP statements. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.06.2012 06.11.2012 06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|