prog:sql_lock_library_cache
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
| prog:sql_lock_library_cache [2021/03/10 11:39] – gpipperr | prog:sql_lock_library_cache [2021/03/11 11:44] (aktuell) – [Quellen] gpipperr | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| ====== Library cache Lock untersuchen ====== | ====== Library cache Lock untersuchen ====== | ||
| - | **10/2010** | + | **10/ |
| Aus der Doku: | Aus der Doku: | ||
| Zeile 13: | Zeile 14: | ||
| 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). | 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). | ||
| </ | </ | ||
| + | |||
| + | ==== Demo Case ==== | ||
| Code in Session 1 anlegen, in Session 2 aufrufen und in Session 1 erneut anlegen => Ein Library Cache Lock entsteht | Code in Session 1 anlegen, in Session 2 aufrufen und in Session 1 erneut anlegen => Ein Library Cache Lock entsteht | ||
| Zeile 67: | Zeile 70: | ||
| s.saddr = x.kgllkses; | s.saddr = x.kgllkses; | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| ===== Quellen ==== | ===== Quellen ==== | ||
| Zeile 76: | Zeile 81: | ||
| * How to Find which Session is Holding a Particular Library Cache Lock (Doc ID 122793.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:// | ||
prog/sql_lock_library_cache.txt · Zuletzt geändert: 2021/03/11 11:44 von gpipperr