PM10431: MISSING / INCORRECT VALUE CLAUSE FOR LIMIT KEY WHEN IGNORE USED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS does not create the
  correct syntax for limit keys when a PARTITIONING MASK is used.
  .
  The DDL may contain:
   (PART 1 VALUES(),
  PART 2 VALUES(),
   PART 3 VALUES(),
  or
  
  or:
  (PART 1,
   PART 2,
   PART 3,
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison               *
  *                 Tool for z/OS who use ignore                 *
  *                 partitioning when comparing                  *
  *                 objects.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: There were 2 problems reported          *
  *                      when using ignore partitioning:         *
  *                                                              *
  *                      1.DB2 Object Compare                    *
  *                      reported an indextype                   *
  *                      change based on partitioning            *
  *                      differences.  The index was             *
  *                      dropped and recreated                   *
  *                      with the correct number of              *
  *                      parts but without the                   *
  *                      limit key values.                       *
  *                                                              *
  *                      2.The partitioned table                 *
  *                      was recreated with blank                *
  *                      limit key values.                       *
  ****************************************************************
  * RECOMMENDATION: Apply The PTF.                               *
  ****************************************************************
  1.DB2 Object Compare reported an indextype
  change based on partitioning differences, although
  partitioning is ignored. The index should not be
  dropped and recreated.  If recreated for a
  different reason, the index partitioning information
  should be taken from the target.
  
  2.The partitioned table was recreated with
  blank limit key values if ignore partitioning was
  used.
  

Problem conclusion

• 1.The index will not be dropped if the indextype is
  changed based on partitioning differences and
  partitioning is ignored.
  
  2.The partitioned table is recreated correctly
  when ignore partitioning has been specified.
  

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  GOC2CMR  GOC2CMT
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK56303

     UP10/04/28 P F004

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.