PH16564: GEN OF TABLESPACE OF ARCHIVE OR HISTORY COMPLEX NOT CONSISTENT INCLUDING ALTER ENABLE ARCHIVE/ADD VERSIONING STMTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a base table and its archive table, or a base table and
  its history table, each exists in a separate tablespace, GEN
  is not consistent as to how it produces the DDL.  Specifically,
  the ALTER for ENABLE ARCHIVE statement IS NOT included
  when generating DDL for the tablespace containing the base table
  in an archive complex, but the ALTER for ADD VERSIONING
  statement IS included in the DDL generated for the tablespace
  containing the base table in a history complex.  On the other
  hand, the ALTER for ENABLE ARCHIVE statement IS included
  when generating DDL for the tablespace containing the archive
  table, while the ALTER for ADD VERSIONING IS NOT included
  when generating DDL for the tablespace containing the history
  table.
  
  With this fix applied, the behavior of a GEN on either the base
  or archive table in an archive complex will match the behavior
  of a GEN on either the base or history table in a history
  complex. The DDL generated for a tablespace containing the base
  table in an archive or history complex WILL include the ALTER
  for the ENABLE ARCHIVE or ADD VERSIONING statement, while the
  DDL generated for a tablespace containing the archive or history
  table in an archive or history complex WILL NOT include the
  ALTER for the ENABLE ARCHIVE or ADD VERSIONING statement.
  

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.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Reverse engineering program (GEN)       *
  *                      generates DDL differently for           *
  *                      tablespaces in ARCHIVE complex          *
  *                      and tablespaces in HISTORY complex.     *
  ****************************************************************
  GEN presents different behaviors among tablespaces in
  ARCHIVE table and HISTORY table complexes, as follows:
  
  1. Tablespace that contains an base table for ARCHIVE complex:
     Includes tablespace and table DDLs for the base tables and
     the archive table, but DOES NOT include ALTER for ENABLE
     ARCHIVE statement.
  
  2. Tablespace that contains an archive table:
     Includes tablespace and table DDLs for the archive table and
     base table, and DOES include ALTER for ENABLE ARCHIVE
     statement.
  
  3. Tablespace that contains a base table for HISTORY complex:
     Includes tablesapce and table DDLs for the base tables and
     the history table, and DOES include ALTER for ADD VERSIONING
     statement.
  
  4. Tablespace that contains a history table:
     Includes tablespace and table DDLs for the the history table,
     and DOES NOT include ALTER for ADD VERSIONING statement.
  
  In order to have archive table complex behavior be consistent
  with history table complex behavior:
  
  Behavior #1 is fixed to include ALTER for ENABLE ARCHIVE
  statement.
  
  Behavior #2 is fixed to include only tablespace and table DDLs
  for the the archive table, without having ALTER for ENABLE
  ARCHIVE statement.
  
  As a result, the behavior of a GEN on either the base or
  archive table in an archive complex will match the behavior
  of a GEN on either the base or history table in a history
  complex. The DDL generated for a tablespace containing the
  base table in an archive or history complex WILL include
  the ALTER for the ENABLE ARCHIVE or ADD VERSIONING statement,
  while the DDL generated for a tablespace containing the
  archive or history table in an archive or history complex
  WILL NOT include the ALTER for the ENABLE ARCHIVE or
  ADD VERSIONING statement.
  

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:

  UI66931

Modules/Macros

• ADB2REP
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI66931

     UP19/12/25 P F912

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.