After bouncing the R12 application the concurrent managers are not getting up.
The error message in ICM log:
ORACLE error 60 in insert_fcp
Cause: insert_fcp failed due to ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "APPS.FND_CP_FNDSM", line 134
ORA-06512: at line 1.
Even after bouncing the application multiple times the issue persists.
I have also executed the setup clean, cmclean and autoconfig but it did not work for me.
Then I tried "Concurrent Managers Will Not Start ORACLE error 60 in insert_fcp (Doc ID 1256084.1)" , but again no luck.
Finally,After searching it on google, I got the solution.
The root cause was APPS user password was in Grace period.
SQL> select ACCOUNT_STATUS,EXPIRY_DATE,PROFILE from dba_users where username='APPS';
ACCOUNT_STATUS EXPIRY_DA PROFILE
-------------------------------- --------- ------------------------------
EXPIRED(GRACE) DEFAULT
After changing the APPS password the issue got resolved.
The error message in ICM log:
ORACLE error 60 in insert_fcp
Cause: insert_fcp failed due to ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "APPS.FND_CP_FNDSM", line 134
ORA-06512: at line 1.
Even after bouncing the application multiple times the issue persists.
I have also executed the setup clean, cmclean and autoconfig but it did not work for me.
Then I tried "Concurrent Managers Will Not Start ORACLE error 60 in insert_fcp (Doc ID 1256084.1)" , but again no luck.
Finally,After searching it on google, I got the solution.
The root cause was APPS user password was in Grace period.
SQL> select ACCOUNT_STATUS,EXPIRY_DATE,PROFILE from dba_users where username='APPS';
ACCOUNT_STATUS EXPIRY_DA PROFILE
-------------------------------- --------- ------------------------------
EXPIRED(GRACE) DEFAULT
After changing the APPS password the issue got resolved.
A deadlock occurs when 2 sessions block each other by attempting to update a row, which is already updated by another session but has not been yet committed or rolled back. There can be more than 2 sessions involved, but the main idea is the same.
ReplyDeletehttp://dbpilot.net/2018/01/15/ora-00060-deadlock-detected-while-waiting-for-resource/
...