DB2 - Problem description
Problem IT21926 | Status: Closed |
WRONG TRIGGER IS BEING DROPPED FROM PACKED DESCRIPTOR RECORD IF USING LONGER SCHEMA NAME AND SAME TRIGGER NAME. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Wrong trigger is being dropped from packed descriptor record if using longer schema name and same trigger name due to incorrect schema comparison. This is causing further issues when one is trying to drop tables on which triggers were defined. Repro steps: create table table1(i int) create table table2(i int) create table table3(i int) create trigger MYLONGSCHEMA1.trig after insert on table1 for each row insert into table2 values 1 create trigger MYLONGSCHEMA11.trig after insert on table1 for each row insert into table2 values 1 drop trigger MYLONGSCHEMA11.trig --> this step causes the catalog and trigger packed descriptor inconsistency drop table table1 --> this step fails incorrectly with a SQL0204 but should succeed create trigger MYLONGSCHEMA11.trig after insert on table2 for each row insert into table3 values 1 drop table table1 --> this step fails with -901 "Trigger Record Not Found" drop table table2 --> this step fails with -901 "Trigger Record Not Found" | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.08.2017 19.03.2018 19.03.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |