PH33349: DB2 OBJECT COMPARE DOES NOT INCLUDE PENDING DDL WHEN PROCESSING OBJECT CHANGES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Db2 Object Compare does not include pending DDL on a tablespace
  when processing a change to it (e.g., converting the tablespace
  to UTS PBG).
  
  The run job should have initially created an online reorg to
  materialize the pending DDL, or included the pending DDL in the
  tablespace create statement.
  
  If the pending change involves MAXPARTITIONS, for example, then
  this parm may be omitted from the table space definition when
  the run job is executed.  This can result in a SQLCODE -653
  error when subsequently attempting to create a view on the table
  in the table space:
  
  SQLERROR:-653 TABLE table-name IN
  PARTITIONED TABLE SPACE tspace-name
  IS NOT AVAILABLE BECAUSE ITS
  PARTITIONED INDEX HAS NOT BEEN
  CREATED
  
  Keyword:  SQLCODE653N
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the Db2 Administration Tool for     *
  *                 z/OS and Object Comparison Tool for z/OS who *
  *                 want to compare table spaces that have       *
  *                 pending changes to MAXPARTITIONS with        *
  *                 DDL statements with the same MAXPARTITIONS   *
  *                 value                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a user compares a source DDL       *
  *                      statement with MAXPARTITIONS to a       *
  *                      target table space in the catalog with  *
  *                      a pending MAXPARTITIONS change that     *
  *                      matches the source value, Compare does  *
  *                      not include the MAXPARTITIONS change in *
  *                      the definition of the table space that  *
  *                      it is to be dropped and recreated. This *
  *                      behavior results in a SQLCODE -653      *
  *                      when trying to create a view on the     *
  *                      table in the table space.               *
  ****************************************************************
  Compare should correctly process pending changes to
  MAXPARTITIONS when the source DDL has the same MAXPARTITIONS
  value as the pending change, in order to allow for the source
  objects to be correctly created. The incorrect handling of the
  pending change can result in a SQLCODE -653 when attempting to
  create a view on the table in the table space:
  
  SQLERROR:-653 TABLE table-name IN
  PARTITIONED TABLE SPACE tspace-name
  IS NOT AVAILABLE BECAUSE ITS
  PARTITIONED INDEX HAS NOT BEEN
  CREATED
  
  Keyword:  SQLCODE653N
  

Problem conclusion

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

  UI75095

Modules/Macros

• ADB2CME  ADB2CMR
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI75095

     UP21/04/28 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.