STATSPACK report main parameter indicator
Full text link: http://www.eygle.com/more/statspack_list.htm
first part
Database summage information
DB Name DB ID Instance Instal Release Cluster Host ---------- --------------------------- - - ----------- ------------ Glob 188430914 Glob 1 9.2.0.4.0 NO B02
the second part
Database Sampling Time, this section records the time of the database, and the number of sample points, this part of this information is very important for Report.
Any statistics need to be measured by time latitude, leave time, any data lost meaning.
We often see someone in the forum to post TOP 5 wait for the event to seek analysis, our answer is:
Unable to analyze, if there is no time dimension!
Snap ID Snap Time Sessions Curs / Sess Comment ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ - - ------------------- Begin Snap: 508 10-NOV-03 15:27:29 76 39.4 End Snap: 511 10-NOV-03 15:57:42 66 35.4 ELAPSED: 30.22 (MINS)
the third part
Main performance indicator description:
Execute to Parse% Performing an Analysis ratio
Instance Efficiency Percentages (Target 100%) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ Buffer NOWAIT%: 100.00 Redo NOWAIT%: 100.00 Buffer Hit%: 99.81 In-Memory Sort%: 100.00 Library Hit%: 98.75 Soft Parse%: 97.05 Execute to Parse%: 44.21 Latch Hit%: 94.79 Parse CPU To Parse ELAPSD%: 11.74% Non-Parse CPU: 96.08
Performing an analysis ratio calculation formula is as follows:
100 * (1 - parses / executions) = Execute to Parse
So if the system Parses> Executions, this ratio may occur less than 0.
This parameter calculates from the following sections:
Instance Activity Stats for DB: ORA9 Instance: Ora91 Snaps: 30 -32 Statistic Total Per Second Per Trans ----------------------------- ---- -------------------------------- Exchange Deadlocks 481 0.2 0.0 execute count 4,873,158 1,968.2 94.4 ............... parse count (failures) 542 0.2 0.0 parse count (hard) 80,281 32.4 1.6 parse count (total) 2,718,643 1,098.0 52.6 parse time cpu 44,009 17.8 0.9 parse time elapsed 374,902 151.4 7.3 ... ....................
Through the formula and the above two values:
100 * (1 - parses / executions) = Execute to Parse 100 * (1 - 2, 718, 643/4, 873, 158) = 0.4421184777797067118462 * 100 = 44.21 This value <0 usually explains the problem of Shared pool settings or efficiency
Causes repeated resolution, Reparse may be more serious, or it is related to Snapshot
If the value is negative or extremely low, there is usually a problem with database performance.
Parse CPU to Parse Elapsd%
Parse Time CPU and PARSE TIME ELAPSED
100 * (PARSE TIME CPU / PARSE TIME ELAPSED) = Parse CPU to Parse ELAPSD% 100 * (44,009/374,902) = 11.7388010733471680599196590% = 11.74%
Rollback Per Transaction Average Roll Rolling Roll
% Blocks Changed Per Read: 1.14 Rollback Per Transaction%: 38.22 Rows Per Sort: 11.83 If the roll rate is too high, you may indicate that your database has experienced too much invalid operation. Bringing Undo Block This parameter calculation formula is as follows: Round (User Rollbacks / (USER COMMITS USER ROLLBACKS), 4) * 100% .................. User Commits 31,910 12.9 0.6 User Rollbacks 19,740 8.0 0.4 ......... .... For this example: ROUND (19740 / (31910 19740), 4) = .3822
The content of this part has not been written yet, continues to carry ...
:)
Friday, June 25, 2004
If You Have Any Question, please mail to eye@itpub.net.
