OAE update trigger fails with ORA-04021: timeout occurred while waiting to lock object

Document ID : KB000088132
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
ErrorMsg: AwE-5001 Database Query Error (8/22/17 6:02 AM)
Details: create or replace trigger XXAPPWORX_STATUS_NOTIF_TRG
java.sql.SQLException: ORA-04021: timeout occurred while waiting to lock object

When updating the OAE Agent triggers in Applications Manager (AM) the update times out and the above error message is displayed.  

The complete error message will look similar to this:

06:02:17.20 ASM0: .AxConnectionPool: getNamedConnection (sync) done update-OAEPRD jdbc:oracle:thin:@//automic.test.com:1525/Automic:apps
06:02:17.20 ASM5: SQL Error: 4021
06:02:17.20 ASM0: .DBAccess: doSql() sID-null apps@both drop procedure aw_dbpipe_wait
ErrorMsg: AwE-5001 Database Query Error (8/22/17 6:02 AM)
Details: create or replace trigger XXAPPWORX_STATUS_NOTIF_TRG
before update on fnd_concurrent_requests for each row
when ( ( new.phase_code <> old.phase_code ) or
(new.status_code <> old.status_code ) or (new.hold_flag != old.hold_flag) )
begin
-- to trigger the pipe from appworx_oa_requests
update appworx_oa_requests set REQUEST_ID =REQUEST_ID
where request_id = :new.request_id;
end;

jdbc:oracle:thin:@//automic.test.com:1525/Automic:apps
java.sql.SQLException: ORA-04021: timeout occurred while waiting to lock object

 

Environment:
OS Version: N/A
Cause:
Cause type:
Configuration
Root Cause: This error is generated by Oracle and being captured in the Application Manager logs. The error message indicates the database objects are locked.
Resolution:
The ORA-04021 error is captured in the Applications Manager log files, however, it is being returned from Oracle.  It indicates the database objects are locked.  The other process using the locked object will have to finish processing and release the lock, or the process will need to be killed or the database server will need to be recycled in order to release the lock on the object.

Contact your Oracle Database Administrator or the Oracle Customer Support team and have them analyze the issue and take action.


Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A