IBM Support

PK41482: WSL CLONE WITH CATALOG REPLACE OPTION CREATES INCORRECT SECONDARY ALLOCATION OF ZERO FOR INDEXES CREATED IN DB2 V5

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In DB2 Administration Tool using Work Statement List ( WSL )
    Clone operation with catalog replace option can result in
    secondary allocation of zero ( 0 ) for indexes created in
    DB2 v5 or earlier, because Admin is choosing SECQTYI instead of
    SQTY value for small indexes, where SQTY > SECQTYI = 0 .
    .
    Indexes created under DB2 v6 or later display correct secondary
    allocation values, as SECQTYI field is populated with correct
    secondary allocation value by DB2 v6 or later.
    .
    Additional symptoms: overwrite option secqty panel ADB2W1Q index
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 Admin  Tool users  attempting to do      *
    *                 WSL CLONE  with catalog  replace option      *
    *                 results in  zero  secondary  allocation      *
    *                 when the old DB2 objects tables/indexes      *
    *                 has zero  SECQTYI in  the  both  tables      *
    *                 SYSIBM.SYSTABLEPART & SYSIBM.SYSINDEXPART.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: For tables/indexes  created in DB2V5 or *
    *                      earlier,and later migrated up to higher *
    *                      versions, Admin  chooses SECQTYI  value *
    *                      for the secondary allocation instead of *
    *                      SQTY value when SQTY>SECQTYI=0.         *
    ****************************************************************
    * RECOMMENDATION: Apply The PTF.                               *
    ****************************************************************
    For tables/indexes created in V5 versions,secondary allocation
    will be taken from SQTY value.
    

Problem conclusion

  • The problem has been solved by applying the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK41482

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-03-16

  • Closed date

    2007-07-03

  • Last modified date

    2007-09-04

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

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

Modules/Macros

  •    ADB2WCL
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • R710 PSY UK26806

       UP07/08/09 P F708

  • R720 PSY UK26807

       UP07/08/10 P F708

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

Document Information

Modified date:
04 September 2007