ORA-00054: Resource Busy and Acquire with NOWAIT Specified ORA-06512 Approving Workflows
(Doc ID 750724.1)
Last updated on SEPTEMBER 04, 2018
Applies to:Oracle Workflow - Version 188.8.131.52 to 12.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Checked for relevance on 26FEB2012
Users are facing the following error when they are trying to approve POs, PRs, Expense report both through email notifications and Worklist.
"APPS.WF_NOTIFICATION", line 4888 ORA-06512: at line 1
This is happening with all modules and with all users.
User is attempting to respond to a notification (this updates the STATUS of the given notification id in WF_NOTIFICATIONS table) and they face an error that the resource is busy. This means that another session is holding a lock on the object that this user is attempting to modify.
The only other possible session that could hold locks for the same notification id is the mailer. Mailer goes through in cycles as follows.
- dequeues a given notification from WF_NOTIFICATION_OUT queue. This places a lock on that message in WF_NOTIFICATION_OUT queue
- builds a MIME message for that notification and sends it as e-mail.
- locks that given notification in WF_NOTIFICATIONS table. updates the STATUS and MAIL_STATUS.
- the GSC layer issues a commit
During this process, for a very short period mailer holds the lock on that notification.
Locking exception comes when user tries to DO SOME ACTION ITEM on a notification from worklist UI while that has been locked by any other process ( Mailer / Agent Listener etc.). If a notification is being locked for a while then it is fine, but if it has been locked for a long time and lock is not getting released then there is some issue with that process which acquired lock on that notification.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Workflow Information Center, Diagnostics, & Community|