PH40534: DB2 OBJECT COMPARE WSL SQLCODE = -625 / SQLCODEN625 ADDING PK TOTABLE W/ NEW COLUMN BEFORE COLUMN ADDED TO INDEX

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The primary key of the table is being altered via Object Compare
  to include a new column. The corresponding index needs the
  column as well, since the new column is referenced in the
  primary key.  However, the resulting WSL tries to add the
  primary key to the table before adding the newly-referenced
  column to the index, resulting in a -625 error:
  
  ADB7955E SQL error:
  ADB7955E  DSNT408I SQLCODE = -625, ERROR:  TABLE >tablename<
  DOES NOT
  ADB7955E           HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF
  THE PRIMARY OR UNIQUE KEY
  ADB7955E  DSNT418I SQLSTATE   = 55014 SQLSTATE RETURN CODE
  ADB7955E  DSNT415I SQLERRP    = DSNXIAB1 SQL PROCEDURE DETECTING
  ERROR
  ADB7955E  DSNT416I SQLERRD    = 25  0  0  -1  0  0 SQL
  DIAGNOSTIC INFORMATION
  ADB7955E  DSNT416I SQLERRD    = X'00000019'  X'00000000'
  X'00000000'  X'FFFFFFFF'
  ADB7955E           X'00000000'  X'00000000' SQL DIAGNOSTIC
  INFORMATION
  
  
  
  Keyword:  SQLCODEN625;msgadb7955e
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  *                 and Db2 Object Comparison Tool for z/OS      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Adding a column to the primary key of   *
  *                      a table might result in SQL error code  *
  *                      -625.                                   *
  ****************************************************************
  When adding a column to the primary key of a table with
  a corresponding index key defined as UNIQUE, the index key
  definition might not be updated first. This situation can cause
  the following error:
  
  ADB7955E ADBTEP2 DSNT408I SQLCODE = -625, ERROR: TABLE
  ADB7955E ADBTEP2          >tbschema<.>tbname< DOES NOT HAVE AN
  ADB7955E ADBTEP2          INDEX TO ENFORCE THE UNIQUENESS OF THE
  ADB7955E ADBTEP2          PRIMARY OR UNIQUE KEY
  
  Search Keywords: SQLCODE625N MSGADB7955E
  

Problem conclusion

• The 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:

  UI78598

Modules/Macros

• ADB2CM3
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI78598

     UP21/12/18 P F112

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.