Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- prog:sql_lock_library_cache [2010/10/25 22:50] – gpipperr
+++ prog:sql_lock_library_cache [2021/03/11 11:44] (aktuell) – [Quellen] gpipperr
@@ Zeile 1: / Zeile 1: @@
-====== library cache Lock ======
+====== Library cache Lock untersuchen ======
+**10/2010 zum erstenmal das Thema bearbeitet**
+Aus der Doku:
+<code>
+wait: library cache lock
+The library cache lock controls the concurrency between clients of the library cache by acquiring 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 (no other client can change the object).
+This lock is also obtained as part of the operation to locate an object in the library cache (a library cache child latch is obtained to scan a list of handles, then the lock is placed on the handle once the object has been found).
+</code>
+==== Demo Case ====
 Code in Session 1 anlegen, in Session 2 aufrufen und in Session 1 erneut anlegen => Ein Library Cache Lock entsteht
@@ Zeile 55: / Zeile 71: @@
 </code>
+----
+===== Quellen ====
+Support Nodes:
+  * Troubleshooting Library Cache: Lock, Pin and Load Lock (Doc ID 444560.1)
+  * 'library cache lock' Waits: Causes and Solutions (Doc ID 1952395.1)
+  * How to Find which Session is Holding a Particular Library Cache Lock (Doc ID 122793.1)
+Sehr gute Präsentation zu dem Thema:
+  * https://www.doag.org/formes/pubfiles/11343093/2019-NN-Lothar_Flatz-Trouble_im_Shared_Pool-Praesentation.pdf