PM18094: LOCK ESCALATION AND RIDPOOL FAILED COUNTS IN TEP ARE INCORRECT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• "Lock Escalation Exclusive" and "Lock Escalation Shared" counts
  in the "System Key Events" workspace are changed to the TOTAL
  counts since the DB2 subsystem was started. After applying
  this fix the customer can easily define situation(s) to trigger
  on a high total count or a spike from one situation interval
  to the next. They will not have to concern themselves with
  the somewhat muddy concept of "sampling interval"
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   OMEGAMON collector                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The values for "Lock                    *
  *                      Escalation Exclusive", "Lock            *
  *                      Escalation Shared", and "RIDPool        *
  *                      Fallback No Storage" in the "System     *
  *                      Key Events" workspace are too low.      *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  The values for "Lock Escalation Exclusive", "Lock
  Escalation Shared", and "RIDPool Fallback No Storage" in the
  "System Key Events" workspace were for a sampling interval.
  
  PROBLEM CONCLUSION:
  Set "Lock Escalation Exclusive", "Lock
  Escalation Shared", and "RIDPool Fallback No Storage" to their
  total values since DB2 started.
  

Problem conclusion

• Set "Lock Escalation Exclusive", "Lock
  Escalation Shared", and "RIDPool Fallback No Storage" to their
  total values since DB2 started.
  
  KEYWORDS : LOCK ESCALATION EXCLUSIVE
             RIDPOOL FALLBACK NO STORAGE
             LOCK ESCALATION SHARED
  

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:

Modules/Macros

• DUMM8KO2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSN UK58872

     UP10/07/29 P F007

• R420 PSN UK58873

     UP10/07/29 P F007

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.