PM72650: DB2 ADMIN TOOL ALT COMMAND PRODUCES REBIND PACKAGE SYNTAX WITHOUT TRIGGER KEYWORD WHEN COMPLEX RI AND TRIGGER PRESENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 ADMIN TOOL ALT COMMAND PRODUCES REBIND PACKAGE SYNTAX
  WITHOUT TRIGGER KEYWORD WHEN COMPLEX RI AND TRIGGER PRESENT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool or      *
  *                 DB2 Object Comparison Tool for z/OS who      *
  *                 request rebind processing as a part of the   *
  *                 Compare, Alter (ALT) or Change Management    *
  *                 (CM) functions.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When users request rebind processing    *
  *                      as part of the Compare, ALT or Change   *
  *                      Management functions in the DB2         *
  *                      Administration Tool or DB2 Object       *
  *                      Comparison Tool, the batch restart      *
  *                      program ADBTEP2 will produce the        *
  *                      REBIND statements automatically for     *
  *                      the affected packages of parent and     *
  *                      child tables if a foreign key           *
  *                      relationship is established with        *
  *                      ON DELETE of CASCADE or SET NULL.       *
  *                      However, for the affected trigger       *
  *                      packages, ADBTEP2 produces the          *
  *                      wrong REBIND statements without         *
  *                      the keyword TRIGGER which causes        *
  *                      the following error:                    *
  *                      .                                       *
  *                      ADB5148I Auto-Rebind statements         *
  *                               now being performed.           *
  *                      ADB5044I *** INPUT STATEMENT:           *
  *                      REBIND PACKAGE(schema.trigger)          *
  *                      DSNT264I  #ssid- DSNTBRB2 REBIND        *
  *                                ERROR USING userid            *
  *                                AUTHORITY PACKAGE             *
  *                                ssid.schema.trigger.()        *
  *                                IS A TRIGGER PACKAGE          *
  *                      DSNT233I  #ssid- UNSUCCESSFUL           *
  *                                REBIND FOR PACKAGE =          *
  *                                ssid.schema.trigger.()        *
  *                      ADB5121E Command failed:REBIND          *
  *                               PACKAGE(schema.trigger)        *
  *                      ADB5185E The run is ending due to       *
  *                               errors.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The batch restart program ADBTEP2 omits the keyword TRIGGER in
  the REBIND statements for the affected trigger packages when
  users request rebind processing as a part of the Compare, ALT
  or Change Management functions in the DB2 Administration Tool
  or DB2 Object Comparison Tool for z/OS.
  

Problem conclusion

• Problem has been resolved.
  
  Note that if users have applied APAR PM67504's PTF UK81227, the
  sequence of statements in the changes file will be changed to
  generate an ALTER TABLE ... ADD FOREIGN KEY statement first,
  and then the CREATE TRIGGER statement. In this case, ADBTEP2
  will not generate the REBIND statements for the trigger
  packages due to the following reasons:
  
  1- No trigger package exists when processing the ALTER TABLE
  ... ADD FOREIGN KEY statement.
  
  2- There is no need to rebind trigger packages because
  they are newly created when DB2 executes the CREATE
  TRIGGER statements after executing the ALTER TABLE ...
  ADD FOREIGN KEY statement.
  

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:

  UK83821

Modules/Macros

•    ADBTEPR
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA20 PSY UK83821

     UP12/11/30 P F211

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.