PI12793: CHANGES WHICH REQUIRE DROP VERSIONING / ADD VERSIONING DO NOT ST ART THE EFFECTED TABLESPACE IN READ ONLY/RO STATUS FIRST.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS' Change Management function
  does not start effected tablespaces in read only status when a
  change involves DROP VERSIONING and ADD VERSIONING thus opening
  a window for dataloss should activity occur between the time the
  two statements are issued.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool      *
  *                 for z/OS who alter a temporal table where    *
  *                 the change needs to first remove the         *
  *                 VERSIONING and then add VERSIONING back      *
  *                 after altering the temporal table.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using Change Management (CM) to    *
  *                      alter a temporal table, first the       *
  *                      DROP VERSIONING statement needs to      *
  *                      be executed, then the ADD VERSIONING    *
  *                      statement needs to be executed after    *
  *                      the table has been altered, but the     *
  *                      temporal table and history table        *
  *                      were not put into Read-only ( RO )      *
  *                      status before the DROP VERSIONING       *
  *                      statement completed.  Therefore,        *
  *                      during the period when the DROP         *
  *                      VERSIONING statement is executed        *
  *                      until the ADD VERSIONING statement      *
  *                      is executed, there is a potential       *
  *                      for data loss because no historical     *
  *                      data will be recorded into the          *
  *                      history table after the DROP            *
  *                      VERSIONING statement has been           *
  *                      issued.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using Change Management (CM) to alter a temporal table,
  first the DROP VERSIONING statement needs to be executed, then
  the ADD VERSIONING statement needs to be executed after the
  table has been altered, but the temporal table and history
  table were not put into Read-only ( RO ) status before the
  DROP VERSIONING statement completed.  Therefore, during the
  period when the DROP VERSIONING statement is executed until
  the ADD VERSIONING statement is executed, there is a potential
  for data loss because no historical data will be recorded into
  the history table after the DROP VERSIONING statement has been
  issued.
  

Problem conclusion

• Problem has been resolved.
  

Temporary fix

• *********
  * HIPER *
  *********
  

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

•    ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA20 PSY UI20892

     UP14/08/29 P F408

• RB10 PSY UI20893

     UP14/08/30 P F408

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.