Sorry guys, its been long time.
Error occured in Maximo 7.6.1 and Oracle 12c. This error occured while doing db config after adding index in WORKORDER table.
Error: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Ran below query to find out the locked sessions:
select a.sid, a.serial#,b.object_id,b.oracle_username,b.os_user_name,c.object_name,c.owner from v$session a, v$locaked_bject b, dba_objets c where b.object_id = c.object_id and a.sid = b.session_id and object_name='<TABLE NAME>';
Once you get the output, note the sid and serial# values.
Run below query to kill the locaked session by login into sqlplus as user 'system'. If you know any user like 'sys' or 'maximo' having privileges to kill session, use them.
alter system kill session 'sid,session#'; -- Replace the sid and serial# values in the query.
Now verify DB config is stuck:
select * from maxvars where varname = 'CONFIGURING'; --Verify VARVALUE=0
If VARVALUE is 1, then change to 0.
update maxvars set varvalue = 0 where varname = 'CONFIGURING';
commit;
Sometimes it is required to restart the server. In my case, DB Configuration application was hung. so restarted the server. Once application is up, then recreated the index.
Thank you.
Error occured in Maximo 7.6.1 and Oracle 12c. This error occured while doing db config after adding index in WORKORDER table.
Error: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Ran below query to find out the locked sessions:
select a.sid, a.serial#,b.object_id,b.oracle_username,b.os_user_name,c.object_name,c.owner from v$session a, v$locaked_bject b, dba_objets c where b.object_id = c.object_id and a.sid = b.session_id and object_name='<TABLE NAME>';
Once you get the output, note the sid and serial# values.
Run below query to kill the locaked session by login into sqlplus as user 'system'. If you know any user like 'sys' or 'maximo' having privileges to kill session, use them.
alter system kill session 'sid,session#'; -- Replace the sid and serial# values in the query.
Now verify DB config is stuck:
select * from maxvars where varname = 'CONFIGURING'; --Verify VARVALUE=0
If VARVALUE is 1, then change to 0.
update maxvars set varvalue = 0 where varname = 'CONFIGURING';
commit;
Sometimes it is required to restart the server. In my case, DB Configuration application was hung. so restarted the server. Once application is up, then recreated the index.
Thank you.
