IBM Support

PM19162: WHEN IGNORE PARTITIONING IS USED, DIFFERENCES IN PARTITIONING INDEX FOUND AND INDEX IS IDENTICAL. FFA10 PM32111.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using DB2 Object Comparison Tool for z/OS, IGNORE
    keyword PARTITIONING finds difference in indexpart LIMITKEYS
    even when the limitkeys are identical.
    

Local fix

  • Add IGNORE LIMITKEY
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
    *                 z/OS who compare the same index and IGNORE   *
    *                 PARTITIONING is specified.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the DB2 Object Comparison Tool was *
    *                      run on two identical databases with     *
    *                      different owners, and IGNORE            *
    *                      PARTITIONING is specified, the DB2      *
    *                      Object Compare Tool found a difference  *
    *                      in the INDEXPART LIMITKEY when they     *
    *                      were identical.  For example:           *
    *                                                              *
    *                      Compare index source index1 and         *
    *                      target index2                           *
    *                        Part 1                                *
    *                          (A)Change limitkey from : ' '       *
    *                      to 'D'                                  *
    *                                                              *
    *                      The above message should not be         *
    *                      issued.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When IGNORE PARTITIONING is specified, the DB2 Object
    Comparison Tool reported a difference in the INDEXPART LIMITKEY
    when they were identical.
    

Problem conclusion

  • The difference of two identical INDEXPART LIMITKEYs will not be
    reported as a difference.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM19162

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-23

  • Closed date

    2011-04-01

  • Last modified date

    2011-05-02

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

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

Modules/Macros

  • GOC2CMF
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • R720 PSY UK66435

       UP11/04/08 P F104

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

Document Information

Modified date:
02 May 2011