Precise 8.5 APM 7-2.pptVIP

* Flow: Performance trending alert was issued in instance WebSrvP3 on SunP3 Next Step: Inquire more information regarding the alert * Flow: An Activities Performance trending Alert was issues at the 21, Apr 2004 14:05. Next Step: Drill to Inform/Foresight to learn about the page behavior and deviation from norm. * Flow: The trending alert is based on Foresight performance view that are based on performance data that has been collected and stored in the Performance Warehouse. In this analysis we are looking at the response time of cart page. It is clear that from April 21’th there has been an increase in the average response time which triggered the “Performance Trending” alert. The exception threshold is expressed as a percentage of the baseline and is set in the report parameters. Next Step: Integrated environment allows as to launch in context to Indepth/Web, from Foresight report. * Flow: Once we have learned about the performance trending alert on Page Cart, we drill down in context into “Indepth/Web” Here, we find that most of Cart page was spent in Server time. Next: We should continue investigation using Insight/Pro, that will be able to identify , and pinpoint over the problematic tier. * Flow: Insight/Pro correlates activities among tiers and provides them percentages. A specific statement (64204.04393.34519.52949) is responsible for 72.95% of the response time. Next: Launch to Indepth/Oracle. * Flow: Oracle-specific product Indepth/Oracle focuses us on the specific statement. We see the statement usage patterns, the SQL text and the list of Oracle instances using it (RAC environment). We can easily identify instance that uses heavily this statement. Next: We should drill into the instance, and learn about the full instance activity. * Flow: Having breakdown of Oracle time into the various SQL statements the system executed. This graph lets us compare the execution times of all statements to help rank them according to their contribut