PM42531: DB2 OBJECT COMPARE WHEN TABLE IS REFERENCED BY MQT, PARTITIONING KEYS CANNOT BE ALTERED (MQT SHOULD BE DROPPED/RECREATED).

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 OBJECT COMPARE WHEN TABLE IS REFERENCED BY MQT, PARTITIONING
  KEYS CANNOT BE ALTERED (MQT SHOULD BE DROPPED/RECREATED).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare the source and target with  *
  *                 a partitioned table that has a dependent     *
  *                 materialized query table ( MQT ).            *
  ****************************************************************
  * PROBLEM DESCRIPTION: An ALTER TABLE..ALTER PARTITION         *
  *                      statement is generated when applying    *
  *                      a change and DB2 issues an SQLCODE =    *
  *                      -20183 / SQLCODEN20183 error:           *
  *                                                              *
  *                      THE PARTITIONED, ADD PARTITION, ADD     *
  *                      PARTITIONING KEY, ALTER PARTITION,      *
  *                      ROTATE PARTITION, OR PARTITION BY       *
  *                      RANGE CLAUSE SPECIFIED ON CREATE        *
  *                      OR ALTER FOR objname IS NOT VALID       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An ALTER TABLE..ALTER PARTITION statement is generated when
  applying a change and DB2 issues an SQLCODE = -20183 /
  SQLCODEN20183 error:
  
  THE PARTITIONED, ADD PARTITION, ADD PARTITIONING KEY, ALTER
  PARTITION, ROTATE PARTITION, OR PARTITION BY RANGE CLAUSE
  SPECIFIED ON CREATE OR ALTER FOR objname IS NOT VALID
  
  To correctly address this issue, the DB2 Object Comparison
  Tool should correct the DROP/CREATE sequences for the
  affected table and table space.
  

Problem conclusion

• The problem has been resolved.
  

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:

  UK69687

Modules/Macros

•    ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK69687

     UP11/07/15 P F107

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.