• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 Balachandran_Chandrasekaran commented Permalink

Hi, thanks for this article.. I find this very useful as it helps me to quickly point me in the right direction during performance problems. <div>&nbsp;</div> If you don't mind, could you clarify/confirm me few more things as I don't find explicit text book definitions of these fields in Information Center? <br /> (FYI - I also read this page http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.wn.doc%2Fdoc%2Fc0055023.html) <div>&nbsp;</div> 1. Can I say total request time = processing time+ RQST_WAIT_TIME_PERCENT ? <br /> 2. Is Processing Time=(SECTION_PROC_TIME_PERCENT+COMPILE_PROC_TIME_PERCENT+TRANSACT_END_PROC_TIME_PERCENT+UTILS_PROC_TIME_PERCENT) <div>&nbsp;</div> 3. Is RQST_WAIT_TIME_PERCENT = (IO_WAIT_TIME_PERCENT+ <br /> LOCK_WAIT_TIME_PERCENT+AGENT_WAIT_TIME_PERCENT+ NETWORK_WAIT_TIME_PERCENT) ? <div>&nbsp;</div> 4. Could you clarify what is the difference between RQST_WAIT_TIME_PERCENT ACT_WAIT_TIME_PERCENT of sysibmadm.mon_db_summary table?

2 LouiseCooper commented Permalink

Hi Bala <div>&nbsp;</div> Sorry for the delay replying to you, and thank you very much for reading the blog, I am glad you found it useful. <div>&nbsp;</div> So, answers to your questions. <div>&nbsp;</div> 1. Yes I believe so. <br /> 2. Yes I believe so. <br /> 3. I think you are right - do the percentages add up to 100 in your environment? <br /> 4. <div>&nbsp;</div> RQST_WAIT_TIME_PERCENT: time working on requests TOTAL_WAIT_TIME / TOTAL_RQST_TIME <br /> ACT_WAIT_TIME_PERCENT: time executing activities TOTAL_ACT_WAIT_TIME / TOTAL_ACT_TIME <div>&nbsp;</div> Requests: <div>&nbsp;</div> http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.mon.doc%2Fdoc%2Fc0055387.html&amp;resultof%3D%2522%2572%2565%2571%2575%2565%2573%2574%2573%2522%2520%2522%2572%2565%2571%2575%2565%2573%2574%2522%2520 <div>&nbsp;</div> A request is a directive to a database agent to perform some work that expends database resources. Sources of the request can include: <br /> A directive issued directly by an external application, such as an OPEN or EXECUTE directive. These are referred to as application requests. <br /> A directive issued by a coordinator agent to a subagent at the same or a different database member. <br /> A directive issued by an agent at a different database member. <div>&nbsp;</div> Activity monitor elements, also known as activity metrics, are a subset of request monitor elements. Use activity metrics to monitor the subset of data server processing related to executing activities, especially processing done to execute SQL statement sections. <div>&nbsp;</div> Activities: <div>&nbsp;</div> http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.wlm.doc%2Fdoc%2Fc0052330.html&amp;resultof%3D%2522%2561%2563%2574%2569%2576%2569%2574%2579%2522%2520%2522%2561%2563%2574%2569%2576%2522%2520 <div>&nbsp;</div> Each time your DB2® data server executes the access plan for an SQL or XQuery statement or executes the load utility a corresponding activity is created. <div>&nbsp;</div> The following statements or commands trigger activities on your data server: <br /> All DML statements <br /> All DDL statements <br /> The CALL statement <br /> The load utility <div>&nbsp;</div> The life cycle of an activity for a DML statement does not include processing that occurs before or outside of access plan execution. This implies that activity-based monitoring does not cover operations such as connecting to the database or compiling SQL into an access plan.

Add a Comment Add a Comment