PM66629: DROP AND CREATE USED RATHER THAN ALTER SEGSIZE FFA20 PM69923

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS uses a DROP and CREATE
  rather than an ALTER TABLESPACE SEGSIZE to implement a change.
  The Compare report shows:
  Compare tablespace source(>database<.>tablespace<) and
  target(>database<.>tablespace<)
      (D)Tablespace change from partitioned to partition-by-range
      (D)Field Tablespace TYPE changed from <normal> to PBR
      (D)Field DSSIZE changed from 0 to 2097152
    Tablespace >database<.>tablespace< will be dropped
    Tablespace will be recreated
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare source partition by range   *
  *                 table space to a target partitioned table    *
  *                 space which uses table-controlled            *
  *                 partitioning.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: On DB2 10 New Function Mode (NFM),      *
  *                      users can convert a classic             *
  *                      partitioned table space which uses      *
  *                      table-controlled partitioning to a      *
  *                      partition by range table space          *
  *                      using the ALTER (ALT) statement:        *
  *                                                              *
  *                      ALTER TABLESPACE >tsname<               *
  *                      SEGSIZE >nn<                            *
  *                                                              *
  *                      However, in the DB2 Object              *
  *                      Comparison Tool for z/OS, when          *
  *                      comparing source Partition-by-Range     *
  *                      (PBR) table space to target classic     *
  *                      partitioned table space, Compare        *
  *                      generates a report and APPLY job        *
  *                      to implement the change by a            *
  *                      DROP/CREATE of the table space,         *
  *                      instead of an ALTER tablespace          *
  *                      SEGSIZE.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  On DB2 10 NFM, users can convert a classic partitioned table
  space which uses table-controlled partitioning to a Partition
  by Range (PBR) table space using an ALTER statement:
  
  ALTER TABLESPACE >tsname< SEGSIZE >nn<
  
  However, in the DB2 Object Comparison Tool for z/OS, when
  comparing source Partition-by-Range (PBR) table space to
  target classic partitioned table space, Compare generates
  a report and APPLY job to implement the change by a
  DROP/CREATE of the table space, instead of an ALTER
  tablespace SEGSIZE.
  
  Compare reports:
  
  Compare tablespace source (>dbname<.>tsname<)
  and target (>dbname<.>tsname<)
      (D)Tablespace change from partitioned to
  partition-by-range
      (D)Field Tablespace TYPE changed from >normal<
   to PBR
      (D)Field DSSIZE changed from 0 to 2097152
     Tablespace >database<.>tablespace< will be dropped
     Tablespace will be recreated
  

Problem conclusion

• Problem has been resolved.
  
  NOTE: Altering the SEGSIZE to change the table space type from
  classic partitioned table space to PBR table space will result
  in a pending change. Besides the SEGSIZE change, if there are
  other changes that can not be processed when there is a pending
  change, running the APPLY job may fail with SQLCODEN20385 /
  SQLCODE=-20385.
  
  SQLCODE=-20385:
  THE STATEMENT CANNOT BE PROCESSED BECAUSE THERE ARE PENDING
  DEFINITION CHANGES FORCHANGES OBJECT object-name OF TYPE
  object- type (REASON reason-code)
  
  This will be fixed in APAR PM66849.
  

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:

  UK81360

Modules/Macros

•    ADB2CMF
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• RA10 PSY UK81360

     UP12/08/30 P F208

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.