PM36129: CHANGE IN INDEX NAME ENFORCING PRIMARY KEY IN TABLE RESULT IN SQLCODEN623

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Administration Tool for z/OS, using Change Management
  to Analyze then Run a scenario where the enforcing index for
  the primary key is renamed, Run fails with -623.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare a source and target with    *
  *                 different primary index names.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the only difference between a      *
  *                      source and target is a primary index    *
  *                      name, Object Compare issues warning     *
  *                      message: "Drop of index would require   *
  *                      drop of the primary key on the table.   *
  *                      This could lead to loss of referential  *
  *                      integrity" and a new index is created.  *
  *                      When executing the apply JCL, the       *
  *                      customer will see both the old          *
  *                      primary index and a new index in the    *
  *                      target and error message:               *
  *                                                              *
  *                      SQLCODE = -623,                         *
  *                      ERROR:  A CLUSTERING INDEX              *
  *                      ALREADY EXISTS ON TABLE                 *
  *                      table_name                              *
  *                      SQLSTATE   = 55012 SQLSTATE             *
  *                      RETURN CODE                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  To correctly address this issue, Object Compare should
  generate DDL to drop the primary key first, drop the target
  primary index, create a new index, and restore the primary key.
  

Problem conclusion

• 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:

  UK67050

Modules/Macros

•    ADB2CMF  ADB2CMP  ADB2CMR  ADB2CMS  ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK67050

     UP11/04/27 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.