Thanks for the insight Steve
greetings
Pablo SK
- Steve Adams <steve.adams_at_ixora.com.au> escribió: >
Hi Pablo,
>
> It means that a session is waiting to use or change
> an object definition or to
> use an SQL statement that another session is
> loading, changing or parsing, or is
> waiting to change or parse. If this event
> accumulates a lot of time, then it may
> indicate that the shared pool is too small or is
> being flushed regularly.
> Otherwise it indicates that database object
> definitions are being changed
> regularly. There is a problem with the null-refresh
> optimization for snapshots
> introduced at 8i that can cause this.
>
> @ Regards,
> @ Steve Adams
> @ http://www.ixora.com.au/
> @ http://www.christianity.net.au/
>
>
> -----Original Message-----
> From: Pablo ksksksk [mailto:p_rodri99_at_yahoo.es]
> Sent: Friday, 19 January 2001 5:29
> To: Multiple recipients of list ORACLE-L
> Subject: library cache lock wait event
>
>
> Hi list,
>
> I've detected this wait event on one of my
> production
> databases.
>
>
> Event Name Timed waited
> library cache lock 615.00
>
>
> I'd like to know what's it about.
>
Do You Yahoo!?
Consiga gratis su dirección @yahoo.es en
http://correo.yahoo.es
Received on Fri Jan 19 2001 - 11:53:18 CST
