IBM Support

PH52152: SQLCODE666 ON DROP TABLE USERID.DSN_PROFILE_TABL WITH MESSAGE DROP TABLE CANNOT BE EXECUTED BECAUSE DB2AI FOR ZOS IN PROGRESS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SQLCODE666 ON DROP TABLE USERID.DSN_PROFILE_TABL with message
    DROP TABLE CANNOT BE EXECUTED BECAUSE DB2AI FOR ZOS IS IN
    PROGRESS .
    Additional keywords: Db2ZAI
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 12 and 13 for z/OS users                                 *
    *    of Db2ZAI for z/OS(Db2ZAI)                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When Db2ZAI is active, SQLCODE -666                          *
    * was incorrectly issued on DROP of                            *
    * schema.DSN_PROFILE_TABLE, where                              *
    * schema is not 'SYSIBM'.                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    For Db2's Profile Manager function, the tables and indexes of
    Profile Manager, including DSN_PROFILE_TABLE table, are
    defined with 'SYSIBM' schema.
    Db2ZAI utilizes Profile Manager tables and indexes for one
    of Db2ZAI functionalities. To prevent an interruptive DDL
    change that can cause various problems, Db2 issues
    SQLCODE -666 on DROP and ALTER statements and SQLCODE -750
    on RENAME statement against Profile Manager tables and indexes
    when Db2ZAI is active.
    In the reported case, DROP was attempted against
    schema.DSN_PROFILE_TABLE, where schema is not 'SYSIBM', but
    Db2 incorrectly issued SQLCODE -666.
    

Problem conclusion

  • Db2 has been changed to issue SQLCODE -666 and SQLCODE -750 on
    DROP/ALTER and RENAME statements (respectively) against
    Profile Manager tables and indexes only with 'SYSIBM' schema
    when Db2ZAI is active.
    Additional Keywords: DB2AIV1R4/K DB2AIV1R5/K
                         SQLCODE666  SQLCODE750
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH52152

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-01-25

  • Closed date

    2023-02-20

  • Last modified date

    2023-03-01

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

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

Modules/Macros

  • DSNXIATB DSNXIRIX DSNXIAIX DSNXIRTB DSNXIART DSNXIDIX DSNXIDTS
    DSNXIDDB DSNXIDTB DSNXIDRT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI90616

       UP23/02/28 P F302

  • RD10 PSY UI90617

       UP23/02/28 P F302

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":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 March 2023