PM67206: OC DROP / CREATE ON NUMPARTS DIFFERENCE IN DB2 V9 AND V10 CM9 MODE FOR PBG UTS ONLY WHEN NUMPARTS EXCEEDS 1 FFA20 PM72977

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Compare Tool for z/OS reports differences when
  NUMPARTS is greater than 1 and the compare uses Source as DDL
  file and Target as DB2 catalog.
  .
  DDL command is used to create DDL Source file, and only under
  DB2 v9 and DB2 v10 CM mode, the DDL file omits NUMPARTS,
  causing a default value of 1 even though the DB2 catalog
  contains NUMPARTS greater than 1. The omission of NUMPARTS in
  the DDL file is due to DB2 restrictions at these DB2 levels
  and affects only PBG UTS (Partition By Growth Universal Table
  Space ) object types.
  .
  Reported difference appears similar to:
  .
  Compare tablespace source(>srctsname<) and target(>trgtsname<)
      (D)Field NUMPARTS changed from 5 to 1
    Tablespace >trgtsname< will be dropped
    Tablespace will be recreated
  .
  Customer wishes to avoid DROP / CREATE scenario for PBG UTS
  compares in DB2 v9 and v10 CM9 environments when the only real
  difference is NUMPARTS greater than 1 in the DB2 catalog.
  

Local fix

• Use NUMPARTS in IGNORE file
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare source Partition-by-Growth  *
  *                 (PBG) tablespace from DDL with target        *
  *                 Partition-by-Growth (PBG) tablespace from    *
  *                 DB2 catalog with NUMPARTS > 1 on DB2 9 New   *
  *                 Function Mode (NFM) or DB2 10 Compatibility  *
  *                 Mode (CM) 9 subsystems.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: In the DB2 Object Comparison Tool for   *
  *                      z/OS, when comparing source PBG         *
  *                      tablespace DDL with target PBG          *
  *                      tablespace from DB2 catalog with        *
  *                      NUMPARTS > 1 on DB2 9 New Function      *
  *                      Mode (NFM) or DB2 10 Compatibility      *
  *                      Mode (CM) 9, Compare will generate      *
  *                      the following reports:                  *
  *                                                              *
  *                      Compare tablespace source               *
  *                      (>srctsname<) and target(>trgtsname<)   *
  *                       (D)Field NUMPARTS changed from n to 1  *
  *                       Tablespace >trgtsname< will be         *
  *                       dropped                                *
  *                       Tablespace will be recreated           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Compare should not detect and report differences in NUMPARTS
  for PBG tablespace in DB 9 NFM and DB2 10 CM9 since
  MAXPARTITIONS and NUMPARTS cannot be specified together for
  PBG tablespace, it results in a SQLCODE = -628 / SQLCODEN628:
  
  SQLCODE = -628, ERROR:  THE CLAUSES ARE
  MUTUALLY EXCLUSIVE
  SQLSTATE   = 42613 SQLSTATE RETURN CODE
  

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:

  UK82090

Modules/Macros

•    ADB2CMF
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK82090

     UP12/09/27 P F209

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.