DB2 - Problem description
Problem IC73831 | Status: Closed |
LOGIC ERROR WITH REVALIDATION OF RECURSIVE COMPILED TRIGGERS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
After a recursive compiled trigger has been invalidated, a subsequent statement that revalidates the trigger may return SQL0917N "Bind package failed". Example: create table T1(c1 integer, c2 integer) % create trigger TRIG01 after update of C2 on T1 referencing old row as O new row as N for each row when (O.C2 is null) begin -- An UPDATE of T1 is required here to reproduce the failure: update T1 set T1.C2 = N.C2 where T1.C1 = N.C1; end % -- Invalidate T1's dependents (including TRIG01): alter table T1 alter column C2 set data type bigint % reorg table T1 % -- Now compile an SQL statement that references TRIG01. -- SQL917N is incorrectly returned. update T1 set C2 = 10 where C1 < 10 % connect reset % terminate % | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * SERIAL only * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * * Apply v9.7 Fixpack 6. * **************************************************************** | |
Local Fix: | |
Drop and recreate the trigger. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in v9.7 Fixpack 6. At minimum this fix should be applied to the server side. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.01.2011 05.06.2012 05.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |