IBM Support

PI39114: CHECK DATA UTILITY GETS A 00C90101 DSNIFDPO 5001 ABEND

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running a CHECK DATA utility on thirteen tablespaces,
    after all tables have displayed the "DSNU739I DSNUKDAT - CHECK
    TABLE tbname COMPLETE" message, the utility abends with message
    DSNU017I DSNUGBAC UTILITY DATA BASE SERVICES MEMORY EXECUTION
    ABENDED, REASON=X'00C90101'.
    
    Breaking the CHECK DATA up, to process fewer tablespaces at a
    time, allows them to complete successfully.
    
    RC00C90101 MODDSNIFDPO ERQUAL5001
    

Local fix

  • Break the CHECK DATA command up, into multiple CHECK DATA
    commands, each processing a small number of the original
    tablespaces.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS users of CHECK DATA      *
    *                 utility                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIFDPO:5001    *
    *                      occurred during CHECK DATA with the FOR *
    *                      EXCEPTION option specified on multiple  *
    *                      table spaces, one of which contained a  *
    *                      table with an XML column.               *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available.         *
    ****************************************************************
    User ran CHECK DATA against a list of table spaces.  One of the
    table spaces contained a table with an XML column and a
    referential constraint.  The FOR EXCEPTION keyword specified the
    exception table which also contained an XML column.
    
    The ABEND04E RC00C90101 at DSNIFDPO ERQUAL5001 happened when
    CHECK DATA attempted to copy XML data into the exception table,
    because the internal structure for the XML table was not set up
    correctly.
    
    This problem happens intermittently.
    

Problem conclusion

  • CHECK DATA utility was changed to set up the internal structure
    of the XML table correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI39114

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-15

  • Closed date

    2015-06-03

  • Last modified date

    2015-07-01

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

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

    UI28193

Modules/Macros

  • DSNUKSRI
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI28193

       UP15/06/23 P F506

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":"10.1","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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2015