-> 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.
-> Library cache pin: This event manages library cache concurrency. Pinning an object causes the heaps to be loaded into memory. If a client wants to modify or examine the object, the client must acquire a pin after the lock.
-> Library cache pin: This event manages library cache concurrency. Pinning an object causes the heaps to be loaded into memory. If a client wants to modify or examine the object, the client must acquire a pin after the lock.
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/21993926/viewspace-663617/ ，如需转载，请注明出处，否则将追究法律责任。
下一篇：
进军OCM
请登录后发表评论
登录
全部评论
最新文章
- PARALLEL_EXECUTION_MESSAGE_SIZE
- some suggestions for rac performance
- ORA-01931: cannot grant UNLIMITED TABLESPACE to a role on 10g
- RMAN-06094 Datafile does not exist
- MRP0: Background Media Recovery terminated with error 1274
- set up a standby quickly by duplicate.
- how to mount diskgroup automatically
- alias doesn't work on solaris
- ORA-00600 [Kfgfinalize_2] While Mounting Diskgroups In Rac [ID 418063.1]
- rac installation on Solaris10 x86-64
