Trying to start the 184.108.40.206 Grid Control with opmnctl command fails with the following errors.
[oraoem@erputdb2 bin]$ ./opmnctl status
opmnctl: ORACLE_INSTANCE is not set.
opmnctl status requires that ORACLE_INSTANCE be correctly set in your
In the 220.127.116.11 Grid Control release, "opmnctl" is not a valid command for starting the OMS as the 11g OMS is deployed in Weblogic server unlike 10g version which is deployed on an OC4J.
opmnctl utility should be used to start the OMS only in the 10g versions of Grid Control nad not in the 11g Grid Control version.
Grid Control 18.104.22.168 uses "emctl" command to start Grid Control:
./emctl start oms
This will start the Grid Control 22.214.171.124 OMS as well as starting the necessary Weblogic processes needed by the OMS.
11g Grid Control: Using 'opmnctl startall | status | stopall' in OMS_HOME Fails with "opmnctl: ORACLE_INSTANCE is not set" [ID 1160335.1]