PI10310: OBJECT COMPARE IS NOT GENERATING ADD VERSIONING STATEMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Compare Tool for z/OS is not generating the Add
  Versioning Statement when the Alter statement in the DDL is
  specified prior to the History Table being created.
  For example:
  CREATE TABLE..  TEMPORAL_TABLE
    ALTER TABLE .. ADD VERSIONING ..
      CREATE TABLE .. HISTORY_TABLE
  The objects without the versioning statement are created.
  

Local fix

• Move the Alter Table Add Versioning statement after the
  Create History Table statement.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool      *
  *                 for z/OS who specify a DDL file as the       *
  *                 compare source, and there is an ALTER        *
  *                 TABLE ADD VERSIONING statement in the file   *
  *                 but the specified history table was not      *
  *                 defined at the time the statement was        *
  *                 issued.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When specifying a DDL file as a         *
  *                      compare source which has an ALTER       *
  *                      TABLE ADD VERSIONING statement to       *
  *                      specify a temporal table, the           *
  *                      statement was invalid because it        *
  *                      specified a history table that was      *
  *                      not defined at the time the             *
  *                      statement was issued.  After the        *
  *                      compare, if the temporal table needs    *
  *                      to be created or recreated, the DDL     *
  *                      for the temporal table is erroneously   *
  *                      generated without an ADD VERSIONING     *
  *                      statement in the CHANGE file.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A temporal table was defined via an ALTER TABLE ADD VERSIONING
  statement on the source and this table needs to be created or
  recreated after the compare, but only the DDL of the temporal
  table was generated in the CHANGE file.  An ADD VERSIONING
  statement was not generated because the ALTER TABLE ADD
  VERSIONING statement was not defined at the time the
  statement was issued.
  

Problem conclusion

• Problem has been resolved. If an ALTER TABLE ADD VERSIONING
  statement specified a history table which was not defined at
  the time the statement was issued, DB2 Object Compare will
  stop processing and issue a RC=12 / Return code 12 with the
  following error message ADB7205E / msgadb7205e:
  
  ADB7205E The ALTER TABLE ADD VERSIONING statement cannot be
  processed, because the history table history_table_qualifier.
  history_table_name was not defined at the time the ADD
  VERSIONING statement was issued in the DDL file.
  

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

•    ADBCCMM  ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA20 PSY UI19337

     UP14/07/08 P F407

• RB10 PSY UI19338

     UP14/07/08 P F407

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.