Re: hard vs soft parse

I think that there is a mis-print here, surely is should read:

>"A high soft parse rate is important because unnecessary HARD parses

Most applications will have to go through the parse/execute/fetch cycle to get data, OLTP systems rarely have a natural design that makes it straightforward to code for re-binds, which is how you explicitly avoid re-parsing.

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases

Publishers:  Addison Wesley Longman
Book bound date: 8th Dec 2000
See a first review at:
http://www.ixora.com.au/resources/index.htm#practical_8i
Order from Amazon via: http://www.jlcomp.demon.co.uk

arminseidel_at_my-deja.com wrote in message <8vdtnv$e45$1_at_nnrp1.deja.com>...


>Thanks! But how to avoid soft parsing?

>

>Oracle Magazine Sept/Oct publishes an article on Statspack:

>"A high soft parse rate is important because unnecessary soft parses

>limit application scalability. Ideally, a SQL statement should be soft-

>parsed once and per session and executed many times."

>

>Should the application keep a cursor on each SQL statement to avoid

>soft parsing?

>