IBM Support

PM75103: POSSIBLE CKZ04817E ERROR PROCESSING VVCNS: RBA NOT IN VVCN STACK

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Possible CKZ04817E ERROR PROCESSING VVCNS: RBA NOT IN VVCN STACK
    This error is possible from a DB2GETBACKINFO command or a COPY
    command when the ICF catalogs are being backed up from the
    target volumes.  The problem happens when there is an empty
    block in the VVDS before a VVCN record.
    

Local fix

  • A  possible work around would be to move or dump all the data
    sets on the corresponding source volume, re-initailze the
    source volume, move or restore the data sets back to the volume,
    take a DB2 BACKUP SYSTEM and rerun the cloning.
    .
    Another possible work around would be to create 1 track data
    sets on the corresponing volume to get at least one NVR record
    into the empty VVDS block on the corresponding source, take a
    DB2 BACKUP SYSTEM, and rerun the cloning.  The number of data
    sets to allocate will depend on where in the VVDS the empty is
    and how much freespace there is in the blocks that are before
    the empty block.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Possible CKZ04817E ERROR PROCESSING     *
    *                      VVCNS: RBA NOT IN VVCN STACK. This      *
    *                      error is possible from a                *
    *                      DB2GETBACKINFO command or a COPY        *
    *                      command when the ICF catalogs are       *
    *                      being backed up from the target         *
    *                      volumes. The problem happens when       *
    *                      there is an empty block in the VVDS     *
    *                      before a VVCN record.                   *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM75103

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-16

  • Closed date

    2012-11-02

  • Last modified date

    2012-12-04

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

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

    UK83212

Modules/Macros

  •    CKZ00047
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R310 PSY UK83212

       UP12/11/08 P F211

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":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021