PK32112: GOC IGNORE OF LIMITKEYS DOES NOT IGNORE CHANGE OF PARTITION LIMITKEY CONTINUES TO BE GENERATED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer runs Object Compare and specifies in the ignore file to
  ignore limitkeys of sysindexpart but partitioned limitkeys are
  still changed or altered and reported  ( generated  ).
  Example of what is generated:
  Compare index source(DB2OPER.X0EH0104) and target(DB2OPER.
   X0EH0104)
      Part 1
        (A)Change limitkey from : 2000000.
                             to : 5000000.
  

Local fix

• Please apply the PTF when it becomes available.
  The GOC manual will be changed by this apar.
  See GOC chapter 3.5.1 Understanding ignore fields -
  
  Values of some properties are duplicated in the catalog by
  keeping them in internal and external formats.  Whenever a
  value has two formats, Object Compare is using only the
  field which keeps the external format.
  
  The fields for internal and external formats have different
  names.  For example,
   High value of limit key of a partition is represented by
   two fields:
      Sysindexpart.limitkey (internal format)
      Systablepart.limitkey (external format)
  
  To ignore the Limitkey of partitions, the external format
  should be used in the ignore specifications
  (i.e. Systablepart.limitkey)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool, who     *
  *                 use IGNORE file, may be affected.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The changes to the Partition Limitkeys  *
  *                      for part indexes were not ignored even  *
  *                      when the ignore SYSINDEXPARTS Limitkey  *
  *                      was specified in the IGNORE file.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See Problem Description.
  

Problem conclusion

• Apply the fix.
  

Temporary fix

Comments

APAR Information

• 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

• R710 PSY UK20017

     UP06/11/30 P F611

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.