Explore >> Select a destination
|
You are here 
|
jagjeet.wordpress.com | ||
| | | | |
antognini.ch
|
|
| | | | | ||
| | | | |
yorakb.wordpress.com
|
|
| | | | | check executions, parse_calls and version_count in v$sqlarea. If no issue identified : increase _kgl_hot_object_copies (default is number of cpu). If still not good, identify the most pinned cursors in shared pool : Then mark the cursor as hot : Ref : https://jagjeet.wordpress.com/2011/12/12/library-cache-mutex-x/ https://andreynikolaev.wordpress.com/2011/05/01/divide-and-conquer-the-true-mutex-contention/ | |
| | | | |
andreynikolaev.wordpress.com
|
|
| | | | | Oracle 11.2.0.2 contains enhancements 9282521 and 9239863 named Library cache: mutex X" for objects highly contended for. Part I and II. These enhancements introduce new interesting possibilities to tune some types of the mutex contention. Contention for heavily accessed objects can now be divided between multiple copies of object in the library cache. According to | |
| | | | |
dohdatabase.com
|
|
| | | Oracle Java Virtual Machine allows you to execute Java code directly in the database. This offers some amazing benefits. However, if it is not in use, you can speed up patching and upgrading by removing it. But how do you know whether it is in use? | ||
