IBM Support

PM56653: CHANGE ACCUMULATION TOOL OBIDXLAT ISSUES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1. After OBIDXLAT WRITE_TO_VSAM on HASH tables, table space may
    contain broken pages. DB2 Image Copy on the Target table space,
    after OBIDXLAT WRITE_TO_VSAM may fail with X'00100042',
    ERROR CODE X'0C32'
    
    2. On OBIDXLAT WRITE_TO_VSAM, for a dropped Source TS and only a
    start Image Copy is specified and no Incremental Image Copies
    are specified, data from Source table space is not recovered to
    the Target Table Space.
    
    3. When a Job profile is setup with 'Start Spaces in
    Utility/Read only as 'U' and the job profile is build for an
    OBIDXLAT related object profile STOP database.tablespace before
    OBIDXLAT step and START database.tablespace after OBIDXLAT step
    is generated for the Source instead of Target.
    
    4. When setting up an object profile for OBIDXLAT, on GGC$OXLT
    panel if Target DBID/PSID are set to -1 and the object profile
    is saved, on going back to GGC$OXLT panel shows 65535 for Target
    DBID/PSID.
    
    5. When trying to update an object profile setup for OBIDXLAT on
    an AUXILIARY database.tablespace for XML, we get a GGCM520E
    message that the Target SSID/DBNAME/TSNAME are not entered.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Change Accumulation Tool.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. After OBIDXLAT WRITE_TO_VSAM on      *
    *                      HASH tables, table space may contain    *
    *                      broken pages. DB2 Image Copy on the     *
    *                      Target table space, after OBIDXLAT      *
    *                      WRITE_TO_VSAM may fail with             *
    *                      X'00100042', ERROR CODE X'0C32'         *
    *                      2. On OBIDXLAT WRITE_TO_VSAM, for a     *
    *                      dropped Source TS and only a start      *
    *                      Image Copy is specified and no          *
    *                      Incremental Image Copies are specified, *
    *                      data from Source table space is not     *
    *                      recovered to the Target Table Space.    *
    *                      3. When a Job profile is setup with     *
    *                      'Start Spaces in Utility/Read only as   *
    *                      'U' and the job profile is build for    *
    *                      an OBIDXLAT related object profile      *
    *                      STOP database.tablespace before         *
    *                      OBIDXLAT step and START                 *
    *                      database.tablespace after OBIDXLAT      *
    *                      step is generated for the Source        *
    *                      instead of Target.                      *
    *                      4. When setting up an object profile    *
    *                      for OBIDXLAT, on GGC$OXLT panel if      *
    *                      Target DBID/PSID are set to -1 and the  *
    *                      object profile is saved, on going back  *
    *                      to GGC$OXLT panel shows 65535 for       *
    *                      Target DBID/PSID.                       *
    *                      5. When trying to update an object      *
    *                      profile setup for OBIDXLAT on an        *
    *                      AUXILIARY database.tablespace for XML,  *
    *                      we get a GGCM520E message that the      *
    *                      Target SSID/DBNAME/TSNAME are not       *
    *                      entered.                                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM56653

  • Reported component name

    DB2 CHANGE ACCU

  • Reported component ID

    5655F5500

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-01-24

  • Closed date

    2012-02-23

  • Last modified date

    2012-04-03

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

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

    UK76472

Modules/Macros

  • GGC$BMSG
    GGC$BULD
    GGC$BULJ
    GGC$BUTH
    GGC$BUTR
    GGC$BUTS
    GGC$BUTU
    GGC$CALL
    GGC$EXCP
    GGC$EXPF
    GGC$IMPF
    GGC$OINC
    GGC$OPRI
    GGC$OPRT
    GGC$OPRU
    GGC$OPVE
    GGC$OPVL
    GGC$OXLT
    GGC$URBD
    GGC#BSTS
    GGC#BST7
    GGC#BST8
    GGC#BTMP
    GGC#DISP
    GGC#EDSP
    GGC#ERTA
    GGC#ERTI
    GGC#ERT8
    GGC#ERT9
    GGC#IX
    GGC#LGAP
    GGC#LOGR
    GGC#OBEX
    GGC#OPRI
    GGC#OPVD
    GGC#RANG
    GGC#SYSC
    GGC#TS
    GGC#UPRI
    GGC#UTED
    GGC#UTOB
    GGC@PROF
    GGCM51
    H25F210J
    

Fix information

  • Fixed component name

    DB2 CHANGE ACCU

  • Fixed component ID

    5655F5500

Applicable component levels

  • R210 PSY UK76472

       UP12/03/15 P F203

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0"}]

Document Information

Modified date:
30 March 2021