You are on page 1of 2

{{{ This is a thorough and systematic performance review and a comprehensive report will be given.

No changes or tuning will be done during the activity. From the detailed report we could do another engagement acting on the bottlenecks found. -------------------------------------------------------------------------------The Tuning Document 1) Infrastructure Overview 2) Recommendations 3) Performance Summary 4) Operating System Performance Analysis - CPU - Memory - Swap - Storage - Network 5) Oracle Performance Analysis Database Bottlenecks - this includes but not limited to the following: - Stresser of the database server's components (CPU,IO,Memory,Network) on lo w and peak periods using Linear Regression Analysis - ETL period / Ad hoc reports affecting database server performance - Issues on particular wait events - Configuration issues, example would be Parallelism parameters - Long running SQLs - etc. 6) Application Top SQLs - Top SQLs - Top SQLs - Top SQLs - Top SQLs - Top SQLs - Unstable Performance Analysis - SELECT - INSERT - UPDATE - MERGE - PARALLEL execution plans

http://savvinov.com/2012/05/29/where-awr-cant-help-identifying-top-sql-in-absenc e-of-cursor-sharing/ 7) References and Metalink Notes -------------------------------------------------------------------------------Things needed prior and during the activity Below are the documents we need before the activity: 1) Most recent RDA of the database 3) Hardware, Storage, and network architecture that includes the Database, Appli cation Server, BI environment 4) Hardware, Storage (raw and usable), and network make and model (plus specs) 5) Workload period of the following (day and time of the month): - work hours - peak and off peak - ETL period - reports period

- (OLTP) transaction processing - backup (RMAN, filesystem copy, tape, SAN mirroring) Here are the things that we need during the tuning activity: 1) It is critical to have AWR/Statspack data, ideally it should represent the fo llowing workload periods: - work hours - peak and off peak - ETL period - reports period - (OLTP) transaction processing - backup (RMAN, filesystem copy, tape, SAN mirroring) The snap period (interval) should be at least 15mins. And the data retention sho uld be at least 30 days to have enough data samples during workload characteriza tion. AWR needs a diagnostic and tuning pack license. Statspack is a free tool. Any of them should be installed. 2) SAR data of the database server Below are some of the tools that will be used during the activity: OSWatcher (Oracle OS Watcher) - Reports CPU, RAM and Network stress, and is a ne w alternative for monitoring Oracle servers Perfsheet (Performance Visualization) For Session Monitoring, uses excel sheet Ashmon (Active Session Monitoring) For monitoring Database Session Lab 128 (trial software) Tool for Oracle Tuning, Monitoring and trace SQL/Store d procedures transactions SQLTXPLAIN (Oracle Extended Explain Plan Statistics) Provides details about all schema objects in which the SQL statement depends on. Orasrp (Oracle Session Resource Planner) Builds complete detailed session profil e Snapper (Oracle Session Snapper) - Reports Oracle session level performance coun ter and wait information in real time Oracle LTOM (Oracle Lite Onboard Monitor) Provides automatic session tracing AWR r2toolkit - A toolkit for workload characterization and forecasting gxplan - Visualization of explain plan }}} References: Total Performance Management http://www.allenhayden.com/cgi/getdoc.pl?file=perfm gmt.pdf http://www.evernote.com/shard/s48/sh/ba502722-fe8a-4088-935d-f32ce6639a41/38b906 fd8ca9b49374679e4b0992de13 <-- details snapper