IBM Support

LI74417: DBA7617 ERROR WHEN ALTOBJ ADMIN ROUTINE IS CALLED AFTER ALTERING THE TABLE DEFINITION (ADDING CONSTRAINT TO TABLE)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ALTOBJ SQL admin routine fails with DBA7617N when a Unique
    constraint is added to the table.
    
    Steps to reproduce the problem
    
    --create database tmp;
    --connect to tmp;
    
    drop table db2.test;
    CREATE TABLE db2.test (
       address_linked_person_id integer NOT NULL,
       address_id          integer NOT NULL,
       person_id           integer NOT NULL,
       linked_person_type  integer NOT NULL
    );
    
    ALTER TABLE db2.test
    ADD CONSTRAINT alp_uk
    UNIQUE(address_id,person_id,linked_person_type);
    
    call sysproc.altobj('VALIDATE', 'CREATE TABLE DB2.TEST(
       ADDRESS_LINKED_PERSON_ID INTEGER NOT NULL,
       ADDRESS_ID          INTEGER NOT NULL,
       PERSON_ID           INTEGER NOT NULL,
       LINKED_PERSON_TYPE  INTEGER NOT NULL,
       X                   INTEGER NOT NULL
    )', null, ?);
    
    It fails with DBA7617N error
    

Local fix

Problem summary

  • Users affected:All
    
    ERROR DESCRIPTION:
    ALTOBJ SQL admin routine fails with DBA7617N when a Unique
    constraint is added to the table.
    
    Steps to reproduce the problem
    
    --create database tmp;
    --connect to tmp;
    
    drop table db2.test;
    CREATE TABLE db2.test (
       address_linked_person_id integer NOT NULL,
       address_id          integer NOT NULL,
       person_id           integer NOT NULL,
       linked_person_type  integer NOT NULL
    );
    
    ALTER TABLE db2.test
    ADD CONSTRAINT alp_uk
    UNIQUE(address_id,person_id,linked_person_type);
    
    call sysproc.altobj('VALIDATE', 'CREATE TABLE DB2.TEST(
       ADDRESS_LINKED_PERSON_ID INTEGER NOT NULL,
       ADDRESS_ID          INTEGER NOT NULL,
       PERSON_ID           INTEGER NOT NULL,
       LINKED_PERSON_TYPE  INTEGER NOT NULL,
       X                   INTEGER NOT NULL
    )', null, ?);
    
    It fails with DBA7617N error
    
    LOCAL FIX:
    None
    

Problem conclusion

  • first fixed in v95 fp5
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI74417

  • 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

    2009-04-13

  • Closed date

    2009-12-17

  • Last modified date

    2009-12-17

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

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

    LI74418

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • 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:
17 December 2009