latch:library cache lock等待事件
latch:library cache lock等待事件
This event controls the concurrency between clients of the library cache. It acquires a lock on the object handle so that either:
One client can prevent other clients from accessing the same object
The client can maintain a dependency for a long time (for example, no other client can change the object)
This lock is also obtained to locate an object in the library cache.
Oracle needs Library Cache Lock and Library Cache Pin for the compilation and parsing of packages, procedures, functions, and other objects. This is to ensure that no one is using the object during compilation/parsing since changes are being made to the definition of the object.
Problem
This wait can occur when DDL is being executed on an object or one of its dependant objects. This causes a database object invalidation. Typically these are the object maintenance operations such as: ALTER, GRANT, and REVOKE. After object invalidation, Oracle tries to recompile the object at the time of the next access attempt. This may be a problem in a case where other sessions have pinned the object in the library cache because they are actively accessing the object. This is more likely to occur with more active users and with more complex dependencies (e.g. many cross-dependent packages or package bodies). In some cases, waiting for object recompilation may take hours, blocking all the sessions trying to access it.
Typical Scenarios
A DML operation that is hanging because the table which is accessed is currently undergoing changes (ALTER TABLE). This may take quite a long time depending on the size of the table and the type of the modification (e.g. ALTER TABLE MODIFY col1 CHAR(200) on millions of records).
The compilation of package will hang on Library Cache Lock and Library Cache Pin if some users are executing any procedure or function defined in the same package.
Sessions trying to access objects that have recently been modified in some way may have to wait while objects are recompiled.
Solution
If a session is hanging on this wait, it is possible to find its blocker and kill it. Refer to MetaLink Note: 122793.1 for details on how to find the blocker.
For a long-term fix, look at any processes or applications that might cause object invalidations and limit or time their execution for minimal impact. Be very careful with altering, granting or revoking privileges on database objects that frequently used PL/SQL is dependent on.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31520497/viewspace-2156806/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- LIBRARY CACHE LOCK 等待事件事件
- enq:Library cache lock/pin等待事件ENQ事件
- 【TUNE_ORACLE】等待事件之“library cache lock”Oracle事件
- 尋找 library cache lock 等待事件的session事件Session
- 'library cache lock'等待事件的處理方法事件
- 俺也談談 library cache lock 等待事件事件
- oracle library cache相關的等待事件及latchOracle事件
- Cache Buffer Chain Latch等待事件AI事件
- 【等待事件】library cache pin事件
- 等待事件--library cache pin事件
- library cache pin 等待事件事件
- cache buffer lru chain latch等待事件AI事件
- 等待事件之Row Cache Lock事件
- 定位Library Cache pin,Library Cache lock等待的解決方法
- ORACLE等待事件latch: cache buffers chainsOracle事件AI
- 等待事件_cache_buffers_chains_latch事件AI
- 等待事件_cache_buffers_lru_chain_latch事件AI
- zt_library cache pin和lock等待分析
- 解決library cache pin等待事件事件
- buffer cache與相關的latch等待事件事件
- 共享池之六:shared pool latch/ library cache latch /lock pin 簡介
- library cache pin等待事件的模擬事件
- sql version count引發cursor:pin s wait x及library cache latch library cache lockSQLAI
- library cache lock和cursor: pin S wait on X等待AI
- 模擬cache buffers chains與library cache pin等待事件AI事件
- Library Cache Pin 及 Library Cache Lock分析
- library cache lock和library cache pin理解
- 一個關於latch: library cache事件的處理事件
- latch free等待事件事件
- 【TUNE_ORACLE】等待事件之“library cache pins”Oracle事件
- 由最長SQL想到的Latch Free( Library Cache Pin/Lock)整理~~草稿SQL
- 由row cache lock等待事件引起的效能問題事件
- 【效能調整】等待事件(八) library cache locks and pins事件
- 處理 latch_cache_buffers_chains等待事件一例AI事件
- Latch free等待事件(轉)事件
- latch等待事件彙總事件
- latch 相關等待事件事件
- Latch free等待事件三事件