IBM Support

LI72664: SQL0901 WHEN TRYING TO DROP A TABLE OR CONSTRAINT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If at any time in the past, one of the following statements were
    run on the parent table of a foreign key dependency
    relationship:
    - drop table
    - alter table drop primary key
    - alter table drop unique key
    - alter table drop column
    
    AND, if the above command had encountered an error that caused
    it to fail, then it's possible to run into this situation
    where the parent table is missing the constraints in the
    catalogs.
    
    The defect is caused because when the command to remove the
    object failed, it did not handle the error code correctly and
    instead of preventing the attempt to remove the constraint on
    the parent table, the removal of the constraint succeeds (and
    the removal of the object itself is correctly failed).
    
    If this happened, the database will end up with a child table
    that still has references to the parent tables key, but the
    parent table no longer has that constraint defined.
    
    Any attempt to drop the child object now will give an error
    message like this in the db2diag.log:
    
    2007-04-29-03.50.41.595222-240 I5082      LEVEL: Severe
    PID     : 9579                 TID  : 18  PROC : db2agent (DB) 0
    INSTANCE: inst                 NODE : 000 DB   : DB
    APPHDL  : 0-135                APPID: PA044AB2.E704.070429075001
    AUTHID  : inst
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 44
     sqlerrmc: Constraint not found in Parent table RI desc
     sqlerrp : SQLRL286
     sqlerrd : (1) 0x00000000      (2) 0x00000000     (3) 0x00000000
               (4) 0x00000000      (5) 0xFFFFFFC4     (6) 0x00000000
     sqlwarn : (1)      (2)      (3)      (4)         (5)       (6)
               (7)      (8)      (9)      (10)        (11)
    
    The catalog tables at this point are not correct, and it's
    not possible to drop the object.  The only way to fix this would
    be to engage support who may be able to provide a manual
    fix.
    

Local fix

Problem summary

  • see problem description
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 1
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI72664

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-06

  • Closed date

    2008-05-29

  • Last modified date

    2008-05-29

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

    LI72568

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 May 2008