DB2 FOR LUW / DB2FORLUW / A50 - DB2

Under rare scenarios, DB2 might produce a SQL0901N error message 
if the following conditions are true 
1. The statement is an alter 
2. Delimited table name inside the alter statement has trailing 
spaces 
3. The table is a dependent object for a trigger 
 
Example: 
Create table "Table1234" (c1 DECIMAL(16,0) NOT NULL GENERATED 
ALWAYS AS IDENTITY ( 
            START WITH +1 
            INCREMENT BY +1 
            MINVALUE +1 
            MAXVALUE +9999999999999999 
            NO CYCLE 
            CACHE 20 
            NO ORDER ), 
            c2 GRAPHIC(1) NOT NULL WITH DEFAULT 'i'); 
 
create trigger "trigger1234" 
no cascade before update of c2 on "Table1234" referencing old as 
"deleted" new as "inserted" 
for each row mode db2sql 
begin atomic 
    if ("deleted".c2 <> 'i' 
        and "inserted".c2 <> 'i') then 
     SIGNAL SQLSTATE '75000' SET MESSAGE_TEXT= 'Error';-- 
    end if;-- 
end; 
 
alter table "Table1234 " alter column c1 drop identity; 
 
SQL0901N The SQL statement failed because of a non-severe system 
error. 
Subsequent SQL statements can be processed. (Reason "table not 
found 
in dep list during alt/drop".) SQLSTATE=58004

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 3                   * 
****************************************************************

Workaround: 
Make sure that the table names referenced in the trigger and the 
alter statement are an exact match.

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 10.5 and Fix Pack 3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.08.2013
27.02.2014
27.02.2014