Hi,
I experimented an ORA-00054 error (nothing very disturbing, it happens regularly). But this time, it's different! Last week, I tried to increase the length of a column in a table and I've got this error. So, I looked to the sessions that could locked the object (the table) and I didn't find one session. Strange, no?
I made a couple of searchs concerning this error message (Doc Id 33453.1, 1945579.1, etc), and I made the following query :
AGRT997 ON prod3> select owner, table_name, tablespace_name, table_lock
2 from dba_tables
3 where owner='AGRMDHP1'
4 and table_lock <> 'ENABLED'
5 order by 2;
OWNER TABLE_NAME TABLESPACE_NAME TABLE_LO
------------------------------ ------------------------------ ------------------------------ --------
AGRMDHP1 CLIENT AGRMDH DISABLED
1 ligne sélectionnée.
I ran this query for all my Oracle databases servers, and I found only one row and it's in my production environment. So, I found something on the Oracle support ((Doc Id 1301281.1, 1945579.1, etc) and I tried the following query to change the state of the table (bring back enable table lock):
SYS ON prod3> ALTER TABLE AGRMDHP1.CLIENT ENABLE TABLE LOCK;
ALTER TABLE AGRMDHP1.CLIENT ENABLE TABLE LOCK
*
ERREUR à la ligne 1 :
ORA-00054: ressource occupée et acquisition avec NOWAIT ou temporisation indiqué
I also read the Doc Id 1985913.1 but it didn't help me. I don't want stop my database service (rembember, I'm in production). Anyway, I found a post on the Internet that shows that if you stop and restart your database, that's not guaranty the lock will be release.
I'm runnning an Oracle Database Entreprise Edition 11.2.0.3 in RAC mode (3 nodes), under Windows Server 2008 R2.
Any idea ? Thank's in advance.
Yves