IBM Support

PI45883: DB2 ADMIN OBJECT COMPARE FAILED PARSING TRIGGER DDL: ADB2PA: THE FOLLOWING STATEMENT COULD NOT BE PARSED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When importing a change which contains a search-condition
    clause and the column name in the search condition is
    qualified by table OWNER and table name, the job fails
    with the following error because the CREATE TRIGGER stmt
    contains double quotes:
    
    Missing semicolon after triggered action
    ADB2PA:  The following statmeent could not be parsed:
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Administration Tool for     *
    *                 z/OS who import a change which contains      *
    *                 a search-condition clause and the column     *
    *                 name in the search condition is qualified    *
    *                 by table OWNER and table name.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 Admin imports a change which        *
    *                      contains a search-condition             *
    *                      clause and the column name in the       *
    *                      search condition is qualified by        *
    *                      table OWNER and table name:             *
    *                                                              *
    *                      For example:                            *
    *                      CREATE TRIGGER ...                      *
    *                      WHEN (>table_schema<.                   *
    *                      >table_name<.>column_name<              *
    *                      = >table_name<.>column_name<)           *
    *                      ...                                     *
    *                                                              *
    *                      and the import job fails with the       *
    *                      following error:                        *
    *                                                              *
    *                      Missing semicolon after triggered       *
    *                      action                                  *
    *                      ADB2PA: The following statement         *
    *                      could not be parsed :                   *
    *                                                              *
    *                      Token number =     nn, Token = ..       *
    *                      Unsuccessful parse of DDL statement.    *
    *                        ADB2CID - Now terminating             *
    *                      ADB0006E ADBCCM - Error(s) found.       *
    *                      Please review output.                   *
    *                                                              *
    *                      because the CREATE TRIGGER              *
    *                      statement contains double periods:      *
    *                                                              *
    *                      CREATE TRIGGER                          *
    *                      >schema<.>triggername< AFTER            *
    *                      update OF...                            *
    *                                                              *
    *                      (>schema<..>col_name<                   *
    *                      !=>schema<..>col_name<)                 *
    *                        ;END                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Import job fails when parsing the CREATE TRIGGER statement
    because it contains double periods between the schema and
    column name.
    

Problem conclusion

  • Problem has been resolved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI45883

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-29

  • Closed date

    2015-11-16

  • Last modified date

    2015-12-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI33003 UI33004 UI33005

Modules/Macros

  •    ADB2PA7
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • RA20 PSY UI33004

       UP15/11/20 P F511

  • RB10 PSY UI33005

       UP15/11/20 P F511

  • RB20 PSY UI33003

       UP15/11/20 P F511

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 December 2015