CP Managers Will Not Start ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
(Doc ID 2113019.1)
Last updated on MARCH 04, 2016
Applies to:Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
The E-Business Suite (EBS) Internal Concurrent Manager (ICM) starts up, but all other Concurrent Processing (CP) managers will not start up (zero actual processes). The Apps listener is up and running, however. The ICM log file contains the following repeating message:
"ORACLE error 54 in insert_fcp
Cause: insert_fcp failed due to ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
ORA-06512: at "APPS.FND_CP_FNDSM", line 134
ORA-06512: at line 1.
The SQL statement being executed at the time of the error was: begin fnd_cp_fndsm.register_fndsm_fcp(:c,:n,:o,:l,:m,:t); end; and was executed from the file &ERRFILE.
Could not initialize the Service Manager FNDSM_<Node Name>_<SID>. Verify that <Node Name> has been registered for concurrent processing.
An error occured in client-side routine afpsmcsm for Service Manager FNDSM_<Node Name>_<SID>. The routine returned code 126.
Check for preceding errors and as well as the service manager log file for further details."
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /u02/app/<SID>/apps/apps_st/appl/po/12.0.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system adm : 29-FEB-2016 11:52:03"
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document