home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC70813 Status: Closed

WHEN AUTO_REVAL IS SET TO DEFERRED ALTER TABLE DROP COLUMN WILL RETURN
SQL0478N

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Dropping a column using the ALTER TABLE command fails with 
SQL0478N if the database configuration parameter AUTO_REVAL is 
set to DEFERRED. 
 
Reproduction scenario: 
 
 
$ db2 "create table t1 (c1 int ,c2 int)" 
DB20000I  The SQL command completed successfully. 
$ db2 "create index ixt1 on t1(c1,c2)" 
DB20000I  The SQL command completed successfully. 
$ db2 "alter table t1 drop column c2" 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
 
SQL0478N  DROP, ALTER, TRANSFER OWNERSHIP or REVOKE on object 
type "COLUMN" cannot be processed because there is an object 
"IXT1", of type "INDEX", which depends on it.  SQLSTATE=42893
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Database having AUTO_REVAL database configuration is set to  * 
* DEFERRED.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Dropping a column using the ALTER TABLE command fails with   * 
*                                                              * 
* SQL0478N if the database configuration parameter AUTO_REVAL  * 
* is                                                           * 
* set to DEFERRED.                                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* Reproduction scenario:                                       * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* $ db2 "create table t1 (c1 int ,c2 int)"                     * 
*                                                              * 
* DB20000I  The SQL command completed successfully.            * 
*                                                              * 
* $ db2 "create index ixt1 on t1(c1,c2)"                       * 
*                                                              * 
* DB20000I  The SQL command completed successfully.            * 
*                                                              * 
* $ db2 "alter table t1 drop column c2"                        * 
*                                                              * 
* DB21034E  The command was processed as an SQL statement      * 
* because                                                      * 
* it was not a valid Command Line Processor command.  During   * 
* SQL                                                          * 
* processing it returned:                                      * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL0478N  DROP, ALTER, TRANSFER OWNERSHIP or REVOKE on       * 
* object                                                       * 
* type "COLUMN" cannot be processed because there is an object * 
*                                                              * 
* "IXT1", of type "INDEX", which depends on it.                * 
* SQLSTATE=42893                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 4.                       * 
****************************************************************
Local Fix:
Set AUTO_REVAL to DISABLED to work as CASCADE drop.
available fix packs:
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

Solution
Problem was first fixed in Version 9.7 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2010
05.05.2011
05.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList