PI74911: DROP VERSIONING NOT GENERATED BY ANALYZE WHEN BASE OR HISTORY TABLE IS DROPPED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Change Management Analyze processing may not generate a DROP
  VERSIONING DDL statement when the base or history table is
  dropped.  This may lead to the following error if the
  tablespace is dropped:
  DSNT408I SQLCODE = -669, ERROR:  THE OBJECT CANNOT BE
  EXPLICITLY DROPPED.
            REASON 0001
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool         *
  *                 for z/OS and DB2 Object Comparison           *
  *                 Tool for z/OS who use the Change             *
  *                 Management (CM) function to drop             *
  *                 tablespaces containing temporal              *
  *                 and history tables.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: A DROP VERSIONING statement is not      *
  *                      generated.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When analyzing a change which includes an explicit drop of
  the tablespaces, a DROP VERSIONING statement is not generated
  before dropping tablespaces containing temporal and history
  tables.
  
  A DROP TABLESPACE statement is generated first for the
  temporal table space, followed by a DROP TABLESPACE
  statement for the history table space, resulting in a
  SQLCODE=-669 / SQLCODEN669 error during execution:
  
  DSNT408I SQLCODE = -669, ERROR:  THE OBJECT CANNOT
  BE EXPLICITLY DROPPED.
  
  When changing the order of the DROP TABLESPACE statements
  without adding a DROP VERSIONING statement, a SQLCODE=-478
  / SQLCODEN478 is observed:
  
  DSNT408I SQLCODE = -478, ERROR:  ALTER, DROP, OR REVOKE
           AFFECTING OBJECT TYPE  TABLE CANNOT BE PROCESSED
           BECAUSE OBJECT object_name OF TYPE TABLE
           IS DEPENDENT ON IT
  

Problem conclusion

• Problem has been resolved by generating an ALTER TABLE DROP
  VERSIONING statement before dropping table spaces containing
  temporal and history tables.
  

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:

  UI45186 UI45187

Modules/Macros

•    ADB2CMO  ADB2CMP
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB20 PSY UI45186

     UP17/03/07 P F703

• RC10 PSY UI45187

     UP17/03/07 P F703

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.