Execute to Parse % in statspack

[pascal01]

Hi, I've been generating several statspack reports of our OLTP database(9.2.0.4) and noticed that the "Execute to Parse %" is constantly between 25-50%. The %Library Hit% is always near 100%. We are not suffering performance problems. We have CURSOR_SHARING=SIMILAR.
Do I need to be concerned with the Execute to Parse issue since the Libary cache is always around 100%?
Thanks for your inputs.

[dbasan]

when everything is working fine why do you worry, relax

What's is your value on session cached cursors?

[pascal01]

Hi. session_cached_cursors=50

Is this why the percentage is too low? Should I increase it to 200?

[dbasan]

That would reduce the parse count. Run statspack again to see the difference.

Are there waits, I/O - run TKprof and post.

[tamilselvan]

Hi, I've been generating several statspack reports of our OLTP database(9.2.0.4) and noticed that the "Execute to Parse %" is constantly between 25-50%. The %Library Hit% is always near 100%. We are not suffering performance problems. We have CURSOR_SHARING=SIMILAR.
Do I need to be concerned with the Execute to Parse issue since the Libary cache is always around 100%?
Thanks for your inputs.

CURSOR_SHARING=SIMILAR requires additional soft parse. It's NOT advisable to use SIMILAR / FORCE in a production environment.

[marist89]

Hi. session_cached_cursors=50

Is this why the percentage is too low? Should I increase it to 200?

Maybe yes, maybe no. How much time is being spent doing this?