Pages

Thursday, 19 April 2018

ORA-04024: self-deadlock detected while trying to mutex pin cursor 0x1FDB2F8C8

We got below error while staring the database on 12.1.0.2 oracle cluster.

oracle@oracle-sangam1_testdb1:/backup_prod/testdb_upgrade_backup>srvctl   start database -d testdb
PRCR-1079 : Failed to start resource ora.testdb.db
CRS-5017: The resource action "ora.testdb.db start" encountered the following error:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-04024: self-deadlock detected while trying to mutex pin cursor 0x1FDB2F8C8
Process ID: 125154
Session ID: 98 Serial number: 57029
. For details refer to "(:CLSN00107:)" in "/opt/oracle/product/base/diag/crs/pwdbl0927pp02/crs/trace/crsd_oraagent_oracle.trc".

CRS-2674: Start of 'ora.testdb.db' on 'pwdbl0927pp02' failed
CRS-2632: There are no more servers to try to place resource 'ora.testdb.db' on that would satisfy its placement policy
oracle@oracle-sangam1_testdb1:/backup_prod/testdb_upgrade_backup>srvctl status database -d testdb
Instance testdb1 is running on node oracle-sangam1
Instance testdb2 is not running on node pwdbl0927pp02
oracle@oracle-sangam1_testdb1:/backup_prod/testdb_upgrade_backup>

Solution:
Set below hidden parameter and restart instances.

alter system set “_fix_control”=’9550277:ON’;


alter system set  "_fix_control"='9550277:ON' scope=spfile;

System altered.

oracle@oracle-sangam1_testdb1:/backup_prod/testdb_upgrade_backup>srvctl status    database -d testdb
Instance testdb1 is running on node oracle-sangam1
Instance testdb2 is running on node oracle-sangam2
oracle@oracle-sangam1_testdb1:/backup_prod/testdb_upgrade_backup>


or

apply patch Patch 21372829 on 12.1.0.2 environment.

Note:Please consult Oracle support before setting hidden parameter

No comments:

Post a Comment