Wait Event: Row cache objects latch
Possible Causes:
Actions:
Ref:
Configuring the library cache to an acceptable size usually ensures that the data dictionary cache is also properly sized. So tuning Library Cache will tune Row Cache indirectly
WAITEVENT: "latch: row cache objects" Reference Note (Doc ID 1550722.1)
gavinsoorma.com
Possible Causes:
- This latch comes into play when user processes are attempting to access the cached data dictionary values.
Actions:
- It is not common to have contention in this latch and the only way to reduce contention for this latch is by increasing the size of the shared pool (SHARED_POOL_SIZE).
- Use Locally Managed tablespaces for your application objects especiallyindexes
- Review and amend your database logical design , a good example is to merge or decrease the number of indexes on tables with heavy inserts
Ref:
Configuring the library cache to an acceptable size usually ensures that the data dictionary cache is also properly sized. So tuning Library Cache will tune Row Cache indirectly
WAITEVENT: "latch: row cache objects" Reference Note (Doc ID 1550722.1)
gavinsoorma.com
1 comment:
Hi,
I guess we can use DBMS_SHARED_POOL to pin the objects in the shared pool so that this wait event can be reduced. But it has to be enhanced from the application design and how often the object is being used.
Thanks
Post a Comment