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
Log Artifacts generation fails due to ORA-31061 error in ASR report generation in RSA Identity Governance & Lifecycle Number of Views RSA Governance & Lifecycle 8.0 Patch 08 Release Notes Number of Views A completed change request to remove Aveksa Application/Directory entitlements from a user does not remove the access from… Number of Views RSA Governance & Lifecycle 8.0 Patch 08 Release Notes Number of Views How to recover the AveksaAdmin account password in RSA Identity Governance & Lifecycle 7.0.2 P02 and above Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… Deploying RSA Authenticator 6.2.2 for Windows Using DISM
Don't see what you're looking for?
