PK57249: DEADLOCK WHILE ALTERING A TRUSTED CONTEXT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 defect 97431 d97431
  Deadlock occurs when Altering a Trusted Context.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of trusted context.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A set of CREATEs and ALTERs of trusted  *
  *                      contexts, with COMMITs in between,      *
  *                      caused a deadlock situation and         *
  *                      resulted in SQLCODE911 RC00C90088.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When attempting a set of ALTERs for trusted context(s),
  the first ALTER will be successful, then if a COMMIT is issued,
  a subsequent ALTER may result in a deadlock against the Build
  Trusted Context Cache.
  
  Sample of the syslog:
  DSNT375I  - PLAN=DSNTEP3 WITH 671
          CORRELATION-ID=ALTTRCTX
          CONNECTION-ID=BATCH
          LUW-ID=USIBMSY.SYEC1DB2.C15113B540A9=15
          THREAD-INFO=ADMF001:*:*:*
          IS DEADLOCKED WITH PLAN=         WITH
          CORRELATION-ID=022.TCCBLD04
          CONNECTION-ID=V91A
          LUW-ID=USIBMSY.SYEC1DB2.C15113F6885B
          THREAD-INFO=SYSOPR:*:*:*
          ON MEMBER V91A
   DSNT501I  - DSNILMCL RESOURCE UNAVAILABLE 672
             CORRELATION-ID=ALTTRCTX
              CONNECTION-ID=BATCH
              LUW-ID=USIBMSY.SYEC1DB2.C15113B540A9=0
              REASON 00C90088
              TYPE 00000D01
              NAME 00000006.00000830
   This resulted in SQL code of -911 with reason 00C90088
   on the alter. This can also occur for CREATEs.
  
   The deadlock was caused between the trusted context cache
   build process and commit processing when they both try to
   access the same catalog tables in different orders.
  

Problem conclusion

• Code has been fixed to avoid the deadlock by accessing the
  objects in the same order. Users may now receive a timeout
  instead of a deadlock.
  
  Additional Keywords:
  SQLCREATE
  SQLALTER
  

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:

  UK41879

Modules/Macros

• DSNXIATX DSNXICTX
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK41879

     UP08/12/10 P F812

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.