Re: ORA-04020: deadlock detected while trying to lock object FIT_DBA.OFFICE

From: Luis Nobre <lcnobre_at_americel.com.br>
Date: 13 Nov 2001 05:51:58 -0800
Message-ID: <72646b0e.0111130551.7f8f1ae5@posting.google.com>

Hi.
Got the following from metalink :

---

This article is being delivered in Draft form and may contain errors. Please use the MetaLink "Feedback" button to advise Oracle of any issues related to this article.

---

Problem Description

---

After upgrading a database, and this database has many concrurrent users, who
are using much stored procedures, package, etc. The following problem can be
encountered: tracefiles with ORA-4020.

04020, 00000, "deadlock detected while trying to lock object %s%s%s%s%s"
// *Cause: While trying to lock a library object, a deadlock is detected.
// *Action: Retry the operation later.

In the database are invalid objects present, check by: select count(*) from dba_objects where status='INVALID';                                                        

Solution Description

---

This problem can be solved by compiling all invalid objects in the database.
In Oracle 8 and higher there is a special script provided to do this:
$ORACLE_HOME/rdbms/admin/utlrp.sql

Explanation

---

After an install, upgrade or patch an object may become invalid. This can be
caused by running $OH/rdbms/admin/catalog.sql and
$OH/rdbms/admin/catproc.sql

Oracle will try to compile an invalid object if it is needed, to do this Oracle
must lock the invalid object. The problem is caused by the fact that several users
of the database try to use the same (invalid) objects. When an object is locked
for compilation, and another user tries to use this object, the ORA-4020 can be
encountered.

References

---

[NOTE:1050538.6] and [NOTE:2097198.6] ORA-04045 & ORA-04020 WHEN UPGRADING FROM 16.0 TO 16.1
Additional Search Words

---

upgrade invalid catalog catproc

I HOPE THIS HELPS!
BEST REGARDS.
LCNOBRE. Received on Tue Nov 13 2001 - 07:51:58 CST