RE: breakable parse lock

From: John Kanagaraj <john.kanagaraj_at_hds.com>
Date: Tue, 6 Jul 2004 14:13:45 -0700
Message-ID: <35CFD500D7BDCE43B9030BBA5979DC18015A37D3@ussccem13.corp.hds.com>

>Breakable parse locks are library cache locks (of enqueue types L[A-P])
>which are held briefly during the compilation time/parsing time of SQL
>or PL/SQL codes. They are released at the end of the
>compilation/parsing. They are known as breakable parse locks as they
>are not released, and only can be broken when the object is un-pinned.
>
>TM locks are held on tables during DDLs (like partition addition, Index
>Rebuilds, View creation on that table, PDML and Analyze) to protect
>(lock!) the definition of the table.
>
>In short breakable parse locks are library cache locks and TM locks
>protect the definition of the table during DDLs.

KG,

I remember something (probably from Steve's book?) that such 'breakable' locks are held as long as required to enable invalidation of PL/SQL objects in the shared pool (Functions/Stored proc/Packages) when the dependent object changes. Is this correct?

John Kanagaraj

---

Please see the official ORACLE-L FAQ: http://www.orafaq.com

---

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Tue Jul 06 2004 - 16:10:44 CDT