IBM Support

PK49588: REPAIR DBD TEST REPORTS ERRORS ON OBDKPAD, OBDDUPPARTS, OBDDFIXPAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • REPAIR DBD TEST reports errors on OBDKPAD, OBDDUPPARTS,
    OBDDFIXPAD.
    
    DSNU924I    DSNUEDDR - DBDS DIFFER AT OFFSET X'00000025'
    OBDDUPPARTS
    DSNU904I    DSNUEDDR -     EXISTING VALUE  X'66'
    DSNU905I    DSNUEDDR -     REBUILT  VALUE  X'7E'
    DSNU939I    DSNUEDDR - DBD HEADER HAD DIFFERENCES WHICH WERE NOT
    IN A NAMED FIELD
    DSNU912I    DSNUEDDR - DBD HEADER CHECKING COMPLETE -- 2 ERRORS
    WERE FOUND
    
    DSNU901I    DSNUEDFT - OBD X'000C' AN INDEX FANSET OBD HAS THE
    FOLLOWING DIFFERENCES
    DSNU920I    DSNUEDFT -   OBDS DIFFER AT OFFSET X'00000083'
    OBDKPAD
    DSNU904I    DSNUEDFT -     EXISTING VALUE  X'BF'
    DSNU905I    DSNUEDFT -     REBUILT  VALUE  X'40'
    DSNU906I    DSNUEDFT -     EXISTING VALUE   '.'
    DSNU907I    DSNUEDFT -     REBUILT  VALUE   ' '
    DSNU913I    DSNUEDDR - OBD X'000C' COMPARISON COMPLETE -- 1
    ERRORS WERE FOUND
    
    These errors will not cause any problems, and can be ignored.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: REPAIR DBD TEST/DIAGNOSE report errors  *
    *                      on field OBDFINUM, OBDFIAPD, OBDINNUM   *
    *                      and some others.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A database is used in CM mode, and then DB2 is migrated to ENFM
    or NFM.  After migration, REPAIR DBD TEST/DIAGNOSE on the
    database may report errors shown above.  After a restart of
    DB2, it will not have the problem again.
    

Problem conclusion

  • This problem is fixed.
    

Temporary fix

Comments

  • ž**** PE08/05/16 PTF IN ERROR. SEE APAR PK65834  FOR DESCRIPTION
    ž**** PE08/05/16 PTF IN ERROR. SEE APAR PK65834  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK49588

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-23

  • Closed date

    2007-12-14

  • Last modified date

    2008-07-26

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

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

    UK32489

Modules/Macros

  • DSNDDBDC DSNDOBD  DSNGDART DSNGDBFI DSNGDBIX
    DSNGDCDB DSNGDCPD DSNGECHK DSNGEDLC DSNGEDSS DSNGEPUF DSNUEDDR
    DSNUEDFI DSNUEDFS DSNUEDFT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK32489

       UP08/01/17 P F801

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

Document Information

Modified date:
26 July 2008