opmnctl startall requires that ORACLE_INSTANCE be correctly set in your environment.

Problem: error occurs when using command opmnctl in oracle 11g grid for starting OMS.

oracle@>opmnctl startall
opmnctl: ORACLE_INSTANCE is not set.

opmnctl startall requires that ORACLE_INSTANCE be correctly set in your
environment.

Make sure you are using ORACLE_INSTANCE/bin/opmnctl, or set ORACLE_INSTANCE
in your environment.

SOLUTION:
–See metalink  [ID 1160335.1]

Cause:

to deploy 10g version we use OC4J but in in 11.1.0.1 grid control release, OMS is deployed in Weblogic server,and so opmnctl is not a valid command to start and stop the OMS.

So, opmnctl utility is used to start OMS only in 10g versions of grid control.
 
Solution:
So use  "emctl" command in 11g to start Grid Control:

 #emctl start oms

This  starts the Grid Control 11.1.0.1 OMS as well as starting the necessary Weblogic processes needed by the OMS.

You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “opmnctl startall requires that ORACLE_INSTANCE be correctly set in your environment.”

  1. Smithe266 says:

    Hi, Neat post. There is a problem with your web site in internet explorer, would check this IE still is the market leader and a large portion of people will miss your magnificent writing because of this problem. fdaedfgdafdaeade

Leave a Reply