PH17149: CM BATCH OBJECT COMPARE DROP HISTORY TABLE ANALYZE ADB7220E INDEX CANNOT BE DROPPED; RUN JOB SQLCODE = -669 / SQLCODEN669

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR addresses two issues involved in CM Batch Object
  Compare processing a DROP of a HISTORY table:
  
  1.   When  the following DDL statements imported to create the
  change:
  
  ALTER TABLE <BASE TB> DROP VERSIONING;
  DROP TABLESPACE <HISTORY TS>;
  
  Analyze may fail with error ADB7220E/msgadb7220e:
  
  ADB7220E The index >indexname< cannot be
  explicitly dropped as there is a primary
  key or unique key defined on it which is
  not in the current processing scope.
  
  2.  When the following DDL is imported to create a change:
  
  ALTER TABLE <BASE TB> DROP VERSIONING;
  DROP TABLE <HISTORY TB>;
  DROP TABLESPACE <HISTORY TS>;
  
  The Analyze is successful, but the Run job may fail with
  the following SQL error when attempting to DROP the tablespace:
  
  DSNT408I SQLCODE = -669, ERROR:  THE OBJECT CANNOT BE
  EXPLICITLY DROPPED.  REASON 0001
  DSNT418I SQLSTATE   = 42917 SQLSTATE RETURN CODE
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool for      *
  *                 z/OS who use temporal and history tables.    *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Issue 1:                                *
  *                      Dropping the versioning from the base   *
  *                      table and then dropping the history     *
  *                      table's tablespace via explicit drops   *
  *                      through imported DDL may result         *
  *                      in error ADB7220E during the analyze    *
  *                      process.                                *
  *                                                              *
  *                      Issue 2:                                *
  *                      Dropping the versioning from the base   *
  *                      table and then dropping the history     *
  *                      table and its tablespace via explicit   *
  *                      drops through imported DDL may result   *
  *                      in a SQL -669 error when trying to run  *
  *                      the wsl that results from the analyze.  *
  ****************************************************************
  Issue 1:
  Analyzing imported DDL that explicitly drops the base table's
  versioning as well as the history table's tablespace may result
  in the following error:
  
  ADB7220E The index >indexname< cannot be
  explicitly dropped as there is a primary
  key or unique key defined on it which is
  not in the current processing scope.
  
  The index is in the tablespace that is
  explicitly dropped, so it should not raise a scope error.
  
  Issue 2:
  The run job for a wsl that explicitly drops the base table's
  versioning as well as the history table and its tablespace
  may result in SQL error -669:
  
  DSNT408I SQLCODE = -669, ERROR: THE OBJECT CANNOT BE
  EXPLICITLY DROPPED. REASON 0001
  DSNT418I SQLSTATE = 42917 SQLSTATE RETURN CODE
  

Problem conclusion

• The problems have 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:

Modules/Macros

• ADB2CM2  ADB2CM3  ADB2CME  ADB2CMF  ADB2CMO  ADB2CMP  ADB2CMR
  ADB2CMS  ADB2CMT  ADB2CMU  ADB7000  ADBCCMM
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI67441

     UP20/01/21 P F001

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.