STATSPACK REPORT - P2

Load Profile Section

1. This is used for comparing two reports to see if the Load characteristics from the two report periods are similar

Sample Load Profile Section Report

Definition

a) Redo Size :-- Amount of Redo generated . If increase in the value more DML happening (INSERT,UPDATE & DELETE) than before

b) Logical Reads :-- Reading from memory and diskc
c) Block changes :-- The number of blocks modified during sample interval . If it is more ,more DML statements are taking place (INSERT,UPDATE & DELETE)
d) Physical Reads :-- The number of call that caused physical I/O
e) Physical Writes :-- The number of physical writes issued
f) User calls :-- The number of queries generated
g) Parses :-- Total of both parse hard and soft
h) Hard Parse :-- This is condition when sql statements is parsed .If it is 100% .This is bad .A hard parse is usually accompained by latch contention on the shared pool and library cache latches.
I) soft parse :-- This is obtained by subtracting hard parses from parse
j) Executes :-- How many statements we are executing per second/transaction
k) Transaction :-- How many transactions per second we process

Buffer Nowait Ration :-- This is the percentage of time that the instance made a call to get a buffer . Buffer was made available immediately meaning it did not had to wait for buffer.

Buffer Hit Ratio :-- Also know as buffer-cache hit ratio . It shows % of time a particular block was found in buffer cache instead of performing a physical I/O

Library Hit Ratio :-- give the percentage of pin requests that result in pin hits.A pin hit occurs when the sql or pl/sql code to be executed is already in the library cache and is valid to execute .If “Library Hit ratio” is low . It could mean low shared pool

Execute to Parse.:-- If value is negative, it means that the number of parses is larger than the number of executions. Another cause for a negative execute to parse ratio is if the shared pool is too small and queries are aging out of the shared pool and need to be reparsed.

Parse CPU to Parse Elapsd % :-- Generally this is measure of how available CPU cycles were for SQL parsing. If this is low you may see “latch free” as one of your top wait events.

Redo Nowait Ratio :-- This indicates the amount of redo entries generated for which there was space available in the redo log.

In Memory Sort Ratio :-- This give percentage sorts that were performed in memory.

Soft Parse Ratio :-- This ratio gives the % of parses that were soft,as opposed to hard.

Latch Hit Ratio :-- This is the ratio of total number of latch misses to the number of latch gets for all latches.