Solved

# TOAD Server Statistics explanation required.

Posted on 2006-05-03
Medium Priority
976 Views
Can somebody please explain the following Server Statistics in TOAD version 8?

Parse to Execute ratio: 80.3098

Redo space wait ratio: 147.6276

Both are giving critical warnings.

Thanks,
Mike.
0
Question by:MikeHunt

LVL 4

Accepted Solution

csachdeva earned 200 total points
ID: 16595911
That means the PARSES are greater than or equal to the EXECUTES.  The formula used it:

,'         Execute to Parse %:'                  dscr
, round(100*(1-:prse/:exe),2)                    pctval

As prse = exe, the execute/parse % goes to ZERO.  As prse starts to exceed executes, the % goes NEGATIVE.

This happens when an application parses a query but never executes it.  Some applications (generic apps typically) parse a "select * from T" to describe a table, never execute the cursor -- their parses exceed their executes.

The soft parse ratio is good cause they parse "select * from t" hundreds of times -- and each parse is in fact a soft parse.  They just parse way too much.

A soft parse happens during the PARSE.  You never need execute the query to increase the soft parse count.  So the two are not really related in any way.  You can have a low execute to parse with a high soft parse ratio, you can have a
high execute to parse with ah low soft parse ratio as well.  They are two indicators that you look at independent of each other.

it would be valid to say "One of the very possible causes is lack of bind variables, since if you do not use binds we KNOW for a fact you are parsing as often as possible and the more you parse, then lower that execute to parse ratio
is."

Redo Space wait Ratio: When a change is made to an Oracle data block, an entry must be made to the redo log buffer. If there is insufficient space for the redo log entry, a redo space wait will occur. The redo space wait records the proportion of time a redo buffer had to wait because of insufficient space. If this ratio is high--certainly if higher than 1 percent--the LOG_BUFFER parameter should be increased.

Regards,
Chetan Sachdeva
0

LVL 1

Author Comment

ID: 16596033
Thanks Chetan, that's about as good an explanation as I could have wished for.

Cheers,
Mike.
0

## Featured Post

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever had to make fundamental changes to a table in Oracle, but haven't been able to get any downtime?  I'm talking things like: * Dropping columns * Shrinking allocated space * Removing chained blocks and restoring the PCTFREE * Re-or…
When it comes to protecting Oracle Database servers and systems, there are a ton of myths out there. Here are the most common.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This video shows syntax for various backup options while discussing how the different basic backup types work.  It explains how to take full backups, incremental level 0 backups, incremental level 1 backups in both differential and cumulative mode a…
###### Suggested Courses
Course of the Month16 days, 1 hour left to enroll