Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
– Accumulated wait time for global locks<br />
– Accumulated wait time for read activity by another thread<br />
– Accumulated wait time for write activity by another thread<br />
– Accumulated wait for latch request (DB2 10 only)<br />
More granular wait time distribution<br />
Before DB2 10, several wait times were accounted as “Other Wait Time” in the statement<br />
cache details. Also, lock and latch wait times were not differentiated.<br />
With DB2 10, IFCID 316 offers the following additional counters:<br />
► Average wait time for latch request<br />
► Average wait time for page latch request<br />
► Average wait time for drain lock<br />
► Average wait time for drain waiting for claims to be released<br />
► Average wait time for log writer<br />
With these counters, you can take advantage of better problem analysis, especially when<br />
tracking down insert performance problems. SAP DBA Cockpit shows the new counters when<br />
running on DB2 10. Figure 3-7 shows an example from a high volume INSERT scenario<br />
where page latch contention accounts for most the total processing times of the statement.<br />
Figure 3-7 Statement Cache: Details of average wait time distribution<br />
P-Lock activity display within group buffer pool activity<br />
Sometimes, physical lock (P-Lock) activity is critical when analyzing complex problems in<br />
data sharing environments. The SAP DBA Cockpit now includes an additional panel in the<br />
Group Buffer Pool Details section that shows counters for P-lock requests, P-lock<br />
suspensions, and P-lock negotiations.<br />
44 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System
Change language