PM87557: APPLY JOB FAILS SQLCODEN601 AFTER 'NEW HISTORY TABLE >SCHEMA<.>T ABLE< WILL BE ADDED' MESSAGE IN OBJECT COMPARISON REPORT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS' APPLY job fails with a
  SQLCODE -601 / SQLCODEN601:
  sqlerror on CREATE     command, EXECUTE    function
   DSNT408I SQLCODE = -601, ERROR:  THE NAME (VERSION OR VOLUME
  SERIAL NUMBER) OF
            THE OBJECT TO BE DEFINED OR THE TARGET OF A RENAME
  STATEMENT IS
            IDENTICAL TO THE EXISTING NAME (VERSION OR VOLUME
  SERIAL NUMBER)
            DICTF.TTGP500HSAG OF THE OBJECT TYPE TABLE
   DSNT418I SQLSTATE   = 42710 SQLSTATE RETURN CODE
   DSNT415I SQLERRP    = DSNXISB1 SQL PROCEDURE DETECTING ERROR
   DSNT416I SQLERRD    = 345  0  0  -1  0  0 SQL DIAGNOSTIC
  INFORMATION
   DSNT416I SQLERRD    = X'00000159'  X'00000000'  X'00000000'
  X'FFFFFFFF'
            X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION
  
  ADB5185E The run is ending due to errors.
  after the GOC2CMP - Compare DB2 Objects  / OBJECT COMPARISON
  REPORT shows a message:
  Table >schema<.>table< not found on target
    New Table >schema<.>table< will be added
    New history Table >schema<.>history_table< will be added
  
  as the DB2 Object Comparison Tool for z/OS does not note the
  history table already existed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare system-period temporal      *
  *                 tables and history tables.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 Object Comparison Tool for z/OS     *
  *                      adds the history table to the target    *
  *                      together with the temporal table when   *
  *                      Compare detects the temporal table is   *
  *                      on the source only.  Object Compare     *
  *                      does not check whether the history      *
  *                      table already exists on the target.     *
  *                      Hence, when the history table is on     *
  *                      target already, the APPLY job will      *
  *                      fail with a SQLCODE=-601 / SQLCODEN601  *
  *                      and ADB5185E / msgadb5185e:             *
  *                                                              *
  *                      DSNT408I SQLCODE = -601, ERROR:         *
  *                      THE NAME (VERSION OR VOLUME             *
  *                      SERIAL NUMBER) OF THE OBJECT            *
  *                      TO BE DEFINED OR THE TARGET OF A        *
  *                      RENAME STATEMENT IS IDENTICAL           *
  *                      TO THE EXISTING NAME (VERSION           *
  *                      OR VOLUME SERIAL NUMBER)                *
  *                      >tbschema<.>tbname< OF THE              *
  *                      OBJECT TYPE TABLE                       *
  *                                                              *
  *                      ADB5185E The run is ending due to       *
  *                      errors.                                 *
  *                                                              *
  *                      Comparison report similar as:           *
  *                                                              *
  *                      Table >schema<.>table< not              *
  *                      found on target                         *
  *                      New Table >schema<.>table<              *
  *                      will be added                           *
  *                       New history Table                      *
  *                       >schema<.>history_table<               *
  *                        will be added                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 Object Comparison Tool for z/OS adds the history table to
  the target together with the temporal table when compare
  detects the temporal table is on the source only.  Object
  Compare does not check whether the history table already
  exists on the target. Hence, when the history table is on
  target already, the APPLY job will fail with SQLCODE=-601 /
  SQLCODEN601 and ADB5185E / msgadb5185e.
  

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:

Modules/Macros

• ADBCCMM  ADB2CMF  ADB2CMP  ADB2CMR  ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK96053

     UP13/07/26 P F307

• RA20 PSY UK96054

     UP13/07/26 P F307

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.