Also add the library cache load and pin events to that.
Anjo.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Friday, December 05, 2003 5:19 AM
1. latch free for the shared pool latch (a shared pool latch in 9i).
2. Indirectly, SQL*Net message
Which wait events are indications that your missing bind variables?
btw, if you want to implement bind variables through a c/c++ middle tier its best to
use 'prepared statements'. correct?
bind arrays can be issued as prepared statements right? This is when you need to do
alot of inserts
latch free waits on library cache shared pool latches.
But I'd check parse to execute ratio from v$librarycache instead. If most of
your statements close parse count and execution count, you might have a
problem.
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L
1. latch free for the shared pool latch (a shared pool latch in 9i).
2. Indirectly, SQL*Net message from client and CPU service time
consumption too, because not using bind variables probably means that an
application parses more often than it needs to.
Cary Millsap
Hotsos Enterprises, Ltd.
