IBM Support

PM97071: DETECT BROKEN DBD01 DATA PROBLEM AND TO PREVENT DAMAGE TO DBD01 DURING MIGRATION TO V10 ENFM

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Migration job DSNTIJEN  fails
DBD for DSNDB06 is corrupted

Local fix

  • n/a

Problem summary

  • ****************************************************************
* USERS AFFECTED: Users of the DSNTIJEN job for DB2 10 for     *
*                 z/OS.                                        *
****************************************************************
* PROBLEM DESCRIPTION: Broken directory database data can      *
*                      cause problems during the DB2 10 for    *
*                      z/OS ENFM process.                      *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available          *
****************************************************************
Invalid length data in the DBD01 directory table space for a
database can lead to lost database data during ENFM processing.

When processing DBD01 table space rows ENFM processing relies
on length data to determine how data should be merged up to form
the BLOB that is being created. In the reported case the length
value was twice what it should have been and so the ENFM process
continued to merge up BLOB data. The additional bytes merged
into the BLOB value came from other database rows. This
effectively lost the database information for those databases
that were merged into the BLOB.

In the reported scenario DSNDB06 was one of the databases
'lost' during the ENFM process and this disabled the DB2
subsystem.

Problem conclusion

  • DB2 ENFM processing code has been changed so that it will now
detect the invalid DBD length situation. If the ENFM process
determines that there is a DBD length problem then it will issue
a DSNU777I message that indicates the name of the broken
database as follows:

  DSNU777I  DSNUECML - REORG ENFM STATUS -
            DETECTED BROKEN DATABASE DURING ENFM - dbname

The ENFM process will then abend (REASON=X'00E40600') to prevent
any damage from being done to the directory data and subsystem.

Additional keywords: ABEND04E RC00E40600 MSGDSNU777I

Temporary fix

  • *********
* HIPER *
*********

Comments

  • ž**** PE14/01/31 FIX IN ERROR. SEE APAR PI07855  FOR DESCRIPTION

APAR Information

  • APAR number

    PM97071

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-16

  • Closed date

    2013-09-29

  • Last modified date

    2014-01-31

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

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

    UK98047

Modules/Macros

  • DSNUECML

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK98047

       UP13/10/15 P F310 ½

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:
31 January 2014

Page Feedback