Oracle Process Manager and Notification (OPMN) enables management of system components in Fusion Middleware and installed with following Fusion Middleware components
Fusion Middleware System Components (there are two type of components in Fusion Middleware – System Component and Java Component) are started using OPMNCTL from $ORACLE_INSTANCE/bin directory and logs are recorded in $ORACLE_INSTANCE/diagnstics/logs/OPMN/<opmn> directory.
If you face below error during OPMN start then check OPMN logs to troubleshoot
RCV: No such file or directory
Communication error with the OPMN server local port.
Check the OPMN log files
/oracle/fusionapps/mididm/Oracle_IDM1/opmn/bin/opmn: unexpected exit: code 512
opmnctl startall: opmn failed to start.
In my case error reported in OPMN logs at $ORACLE_INSTANCE/diagnstics/logs/OPMN/opmn/opmn.log
[2011-10-27T23:29:46][opmn][ERROR:1][OPMN][code:ons-listener]127.0.0.1,6700: BIND (Address already in use)
[2011-10-27T23:35:59][opmn][NOTIFICATION:1][OPMN][code:ons-internal]ONS server initiated
[2011-10-27T23:35:59][opmn][NOTIFICATION:1][OPMN][code:pm-internal]PM state directory exists: /oracle/fusionapps/mididm/asinst_1/config/OPMN/opmn/states
This means OPMN Local Port 6700 is already in use by some other process.
1. Identify which process is using port 6700 (on Linux as root user run “lsof | grep 6700“) and terminate process using port 6700
If above solution is not acceptable then
2. Change OPMN local port in $ORACLE_INSTANCE/config/OPMN/<opmn>/opmn.xml and change value defined against local
<port local=”6700″ remote=”6701″/>
Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.