IBM Support

PI32790: DEADLOCK BETWEEN CATMAINT AND RTS DAEMON

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While running the CATMAINT utility for a SCHEMA RENAME, the
    utility deadlocked with RTS:
    
    DSNU590I  -ssid 268 14:20:20.87 DSNUESCM - RESOURCE NOT
    AVAILABLE,
    REASON=X'00C90088', ON DSNDB06 PROHIBITS PROCESSING
    DSNU012I    268 14:20:21.80 DSNUGBAC - UTILITY EXECUTION
    TERMINATED,
    HIGHEST RETURN CODE=8
    
    DSNT375I  -ssid PLAN=DSNUTIL WITH  887
            CORRELATION-ID=corrid
            CONNECTION-ID=UTILITY
            LUW-ID=xxx.xxxxxxxx.xxxxxxxxxxxx=x
            THREAD-INFO=DB2ADM:UTILITY:DB2ADM:SSDB2CAT:*:*  :*:*
            IS DEADLOCKED WITH PLAN=         WITH
            CORRELATION-ID=014.RTSTST00
            CONNECTION-ID=ssid
            LUW-ID=yyyyyyy.yyyyyyyy.yyyyyyyyyyyy
            THREAD-INFO=SYSOPR:*:*:*:*:*  :*:*
            ON MEMBER ssid
    
    RC00C90088
    MSGDSNT375I
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CATMAINT Users using SCHEMA, OWNER       *
    *                 or VCAT option.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Running CATMAINT with the SCHEMA,       *
    *                      OWNER or VCAT option can deadlocked     *
    *                      with real-time statistics daemon.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Real-time statistics daemon was getting a shared DBD lock
    on DSNDB06 and then an exclusive table lock on
    SYSIBM.SYSTABLESPACESTATS. On the other hand, CATMAINT
    utility was getting the table lock first and then the exclusive
    DBD lock. This may result in a deadlock situation.
    

Problem conclusion

  • DB2 code has been modified so that the CATMAINT utility
    (with the SCHEMA, OWNER or VCAT option) will get the locks
    in proper order to avoid the deadlock.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI32790

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-15

  • Closed date

    2015-06-09

  • Last modified date

    2015-07-01

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

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

    UI28362 UI28363

Modules/Macros

  •    DSNUESCM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI28362

       UP15/06/25 P F506

  • RB10 PSY UI28363

       UP15/06/25 P F506

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"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 May 2020