IBM Support

PI63013: CHECK DATA RECEIVED MESSAGE DSNU733I WHEN THE FOREIGN KEY IN CHILD TABLE ALL HAVE NULL VALUE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RI constraint defined for the FOREIGN key with
    'ON DELETE SET NUll'. The CHECK DATA received message DSNU733I
    and set the table in CHKP when all the foreign key in child
    table have NULL value.  The NULL value should be acceptable.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS CHECK DATA utility users *
    ****************************************************************
    * PROBLEM DESCRIPTION: MSGDSNU733I erroneously issued during   *
    *                      a CHECK DATA utility, leaving the       *
    *                      table space in CHECK PENDING (CHKP)     *
    *                      when the indexed foreign key (FK) is    *
    *                      null.                                   *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    A CHECK DATA utility was run on a dependent table with an
    indexed foreign key defined with ON DELETE SET NULL.  The index
    key included a variable column, but the foreign key did not.
    Rows were deleted from the parent table, causing null foreign
    key values.  The CHECK DATA utility issued DSNU733I - ROW
    (RID=X'nnnnnnnnnn') HAS NO PARENT FOR table in error, and
    placed the table space in CHKP, ending with RC4.  Null values
    should not have been flagged as a referential integrity error.
    
    The message was issued in error because CHECK DATA was not
    checking for nulls correctly.
    

Problem conclusion

  • CHECK DATA utility code has been modified to correctly check
    for null indexed foreign keys.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI63013

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-24

  • Closed date

    2016-07-07

  • Last modified date

    2016-08-02

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

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

    UI39225

Modules/Macros

  • DSNUKIFK
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI39225

       UP16/07/22 P F607

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2016