IBM Support

IT21926: WRONG TRIGGER IS BEING DROPPED FROM PACKED DESCRIPTOR RECORD IF USING LONGER SCHEMA NAME AND SAME TRIGGER NAME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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"
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 3 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21926

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2018-03-19

  • Last modified date

    2018-03-19

  • APAR is sysrouted FROM one or more of the following:

    IT21214

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
19 March 2018