ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Originally Published: 2019-05-01
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.1.0
Platform: null
Platform (Other): null
O/S Version: null
Product Name: null
Product Description: null
Issue
04/08/2019 02:05:16.251 WARN (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 54, SQLState: 61000 04/08/2019 02:05:16.251 ERROR (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Cause
I had opened this separate case to investigate below errors as observed from aveksaServer.log:
04/08/2019 02:05:12.620 WARN (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 54, SQLState: 61000
04/08/2019 02:05:12.620 ERROR (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Error ORA-00054 is a commonly seen error by Oracle users and occurs when a user tries to execute a LOCK TABLE or SELECT FOR UPDATE command with the NOWAIT keyword when the resource is unavailable. DDL or DML operations are being run concurrently without proper commits.
In most cases, Error ORA-00054? occurs from a session. Any session that has referenced the table and any structural change attempt, such as adding a column, requires an “exclusive” lock.
Workaround
select a.sid, a.serial#
from v$session a, v$locked_object b, dba_objects c
where b.object_id = c.object_id
and a.sid = b.session_id
and OBJECT_NAME=’EMP’;
To kill the session and unlock the tables, write the following statement:
SQL>alter system kill session ‘sid, serial#’;
Related Articles
ACM-100162 || PV_USER_ALL_ACCESS view does not include custom attributes post 7.1.1 installation Number of Views The replication connection from local site [] to [] is abnormal since the last change was sent Number of Views RSA Identity Governance and Lifecycle7.0.2 installation with remote database fails with "Invalid Username/Password" in the… Number of Views RSA Identity Governance and Lifecycle error when using the IBM DB2 driver: "Unable to load database driver" Number of Views Unable to modify email address used to create accounts for RSA Community and my.rsa.com Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Act… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Request Access to the RSA Authentication Manager AMI for AWS via RSA Support
Don't see what you're looking for?
