IBM Support

IT27946: DB2MOVE IN LOAD_ONLY MODE MAY LEAVE TABLES IN SET INTEGRITY PENDING

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When running db2move in 2 step mode (DDL_ONLY & LOAD_ONLY), not
    all integrity conditions are reactivated when foreign key
    constrains exist.
    After the LOAD_ONLY step some objects may remain in
    CHECK-PENDING state, so that it is necessary to do a
    manual 'SET INTEGRITY FOR ... IMMEDIATE CHECKED' to make the
    tables available again.
    
    Logfile COPYSCHEMA.err contains:
    SQL3608N Cannot check a dependent table "<schema>.<TAB_A" using
    the SET INTEGRITY statement while the parent table or underlying
    table "<schema>.TAB_B" is in the Set Integrity Pending state or
    if it will be put into the Set Integrity Pending state by the
    SET INTEGRITY statement. SQLSTATE=428A8
    

Local fix

  • Do one of the following:
    - provide the list of tables (with -tn or -tf option) in an
    order to specify parent tables before child tables or
    - manually run 'SET INTEGRITY FOR ... IMMEDIATE CHECKED' for the
    tables being left in Set Integrity Pending state or
    - use the one step mode DDL_AND_LOAD
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Version 11.1 Mod 4 FixPack 6.                 *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 Version 11.1 Mod4 FixPack 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT27946

  • 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

    2019-01-31

  • Closed date

    2021-03-16

  • Last modified date

    2021-03-16

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

    IT27896

  • 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

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

Document Information

Modified date:
18 March 2021