PM44926: ALT PRIMARY INDEX SCHEMA CHANGE TABLESPACE CHKP CHECKPENDING STA TUS AFTER CHANGE AS NO DB2 CHECK UTILITY BUILT SQLCODE162

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS ALT function did not build
  a DB2 CHECK utility for a Change Management change to the
  schema for a primary index of a table.
  .
  The ALTER TABLE child_table FOREIGN KEY parent (field)
  REFERENCES parent_table (field ) ON DELETE RESTRICT ENFORCED ;
  results in a message:
  DSNT404I SQLCODE = 162, WARNING:  TABLE SPACE table_space HAS
  BEEN PLACED IN CHECK PENDING
  

Local fix

• Workaround is to set AutoCheck to YES by going to the
  BP panel from option P off of the main menu or
  run the stand alone DB2 CHECK utility manually..
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool and     *
  *                 DB2 Object Comparison Tool for z/OS.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The CHECK DATA utility was not          *
  *                      generated when the user requested it    *
  *                      and the ALTER TABLE child_table         *
  *                      FOREIGN KEY parent (field)              *
  *                      REFERENCES parent_table (field)         *
  *                      ON DELETE RESTRICT ENFORCED;            *
  *                      statement results in a SQLCODE=162 /    *
  *                      SQLCODE162 message:                     *
  *                                                              *
  *                                                              *
  *                      DSNT404I SQLCODE = 162, WARNING:        *
  *                      TABLE SPACE table_space HAS             *
  *                      BEEN PLACED IN CHECK PENDING.           *
  *                                                              *
  *                      In this situation if the FOREIGN KEY is *
  *                      built with the ENFORCED clause or the   *
  *                      ENFORCE clause is left off the          *
  *                      statement (which means it will default  *
  *                      to ENFORCED), a CHECK DATA should be    *
  *                      generated for the child table in the    *
  *                      generated relationship.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The DB2 Object Compare program will now indicate that a CHECK
  DATA utility should be generated when an ALTER TABLE FOREIGN
  KEY statement is used, and the FOREIGN KEY is built with the
  ENFORCED clause or the ENFORCE clause is left off the Alter
  statement.
  

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

•    ADBGAJOB ADB2CMF  ADB2CMP  ADB2CMR  ADB2W1
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK75982

     UP12/02/08 P F202

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.