All apps dba Blog is the blog contributed by Doyensys Employees, With the view to share the knowledge out of their experience.
Doyensys Is a Fast Growing Oracle Technology Based Solutions Company Located in the US And Offshore Delivery Centers in India. With rich experience In Oracle E-Business, Oracle Database, Oracle Application Express (APEX), Oracle J Developer, Oracle OBIEE and E-Business Suite
Cache contention is a serious issue. In most cases it would be good to analyze
what is holding the library cache lock and killing it will resolve the issue.
Library cache events can even bring the database to a hang state. It’s a good
idea to identify and kill appropriately as early as possible. But do not kill
any mandatory processes or sessions as it may lead to an outage. Contact Oracle
support for critical issues.
Library cache resource types
waited for over the life of the instance
p.addr=s.paddr and s.sid in (51,146,407,397,389,377,345,302,239,214)
This script points to the
session that is holding a library cache lock for any object. A typical session will wait on a library
cache lock when when it is trying to modify the object definition. The object may be a package/procedure or just
a table or index definition