PM67936: OBJECT COMPARE TOOL DOES NOT ISSUE WARNING MSG WHEN CHANGE FROM NON-LARGE TS TO LARGE AND NOT ADJUSTING LIMIT KEY OF LAST PART

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Comparison Tool for z/OS does not issue warning msg
  when changing from a non-LARGE TS to LARGE and not adjusting
  limit key of the last partition to high values.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare index-controlled            *
  *                 partitioned table spaces between source      *
  *                 and target.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Object Comparison Tool for      *
  *                      z/OS does not issue a warning message   *
  *                      when an index-controlled partitioned    *
  *                      table space is changed from non-LARGE   *
  *                      to LARGE and the partitioning limit     *
  *                      key of the last partition is not set    *
  *                      to the highest possible value for an    *
  *                      ascending index key column, or set to   *
  *                      the lowest possible value for a         *
  *                      descending index key column.  When      *
  *                      running the APPLY jobs or Work          *
  *                      Statement List (WSL), some of the       *
  *                      data for the last partition of the      *
  *                      table is discarded during the LOAD      *
  *                      phase.                                  *
  *                                                              *
  *                      According to the rule of DB2, for       *
  *                      index-controlled partitioned table      *
  *                      space, the highest value of the key     *
  *                      in the last partition depends on        *
  *                      how the table space is defined.         *
  *                      For non-LARGE table space, the          *
  *                      highest value of the key that can be    *
  *                      placed in the table is the highest      *
  *                      possible value of the key. For          *
  *                      LARGE partitioned table space, the      *
  *                      value specified for the last partition  *
  *                      is the highest value of the key that    *
  *                      can be placed in the table. Any key     *
  *                      greater than the value that is          *
  *                      specified for the last partition are    *
  *                      out of range. Therefore, when           *
  *                      index-controlled table space is         *
  *                      converted from non-LARGE to             *
  *                      LARGE, the DB2 Object                   *
  *                      Comparison Tool should issue a          *
  *                      warning message in the compare          *
  *                      report to avoid the discarding of       *
  *                      data while applying the change.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The DB2 Object Comparison Tool for z/OS does not issue a
  warning message when an index-controlled partitioned
  table space is changed from non-LARGE to LARGE and the
  partitioning limit key of the last partition is not set to the
  highest possible value for an ascending index key column,
  or set to the lowest possible value for a descending index
  key column. When running the APPLY jobs or Work Statement
  List (WSL), some of the data for the last partition of the
  table is discarded during the LOAD phase.
  

Problem conclusion

• When an index-controlled partitioned table space is changed
  from non-LARGE to LARGE, the DB2 Object Comparison Tool will
  issue warning message ADB7161W in the OBJECT COMPARISON REPORT,
  and Compare will end with return code 4. The warning message
  will be:
  
  ADB7161W The tablespace uses index-controlled partitioning and
  has changed from non-LARGE to LARGE. Data in the last partition
  of the table might be discarded if the partitioning limit key
  is not set to the highest possible value for an ascending index
  key column or set to the lowest possible value for a descending
  index key column.
  
  User needs to review the generated APPLY jobs or WSL before
  applying the change, and update the limit key of the last
  partition, if necessary, to avoid the discarding of data
  during the LOAD phase.
  

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

•    ADB2CMF  ADB2CMP  ADB2CMR  ADB2CMT  ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK82941

     UP12/10/30 P F210

• RA20 PSY UK82942

     UP12/10/30 P F210

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.