OBIEE: Start/Stop Individual Components (Manually)

First, navigate to the ORACLE_INSTANCE/bin directory. For me on Linux, that is /obiee/Middleware/instances/instance. List out the directory contents and you should see the opmnctl
[oracle@oracle-web-tier bin]$ total 56K drwx------ 3 oracle dba 4.0K drwx------ 14 oracle dba 4.0K drwxr-x--- 2 oracle dba 4.0K -rwx------ 1 oracle dba 44K ls -lah Aug 16 00:53 . Sep 8 17:09 .. Aug 16 00:53 essbase_ha Aug 16 00:53 opmnctl

Let's see what is running:

[oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 1525 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 1443 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 1487 | Alive coreapplication_obips1 | OracleBIPresentat~ | 1469 | Alive coreapplication_obis1 | OracleBIServerCom~ | 30698 | Alive

All of the components are running. Good. Let's shut down everything.
[oracle@oracle-web-tier bin]$ ./opmnctl shutdown [oracle@oracle-web-tier bin]$ ./opmnctl status opmnctl status: opmn is not running.

And bring everything back up.

[oracle@oracle-web-tier bin]$ ./opmnctl startall opmnctl startall: starting opmn and all managed processes... [oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 3124 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 3123 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 3121 | Alive coreapplication_obips1 | OracleBIPresentat~ | 3120 | Alive coreapplication_obis1 | OracleBIServerCom~ | 3122 | Alive

Now, let's stop the BI Server, coreapplication_obis1 or OrcleBIServerCom~. There are 2 ways to bring this down. Well, one command, stopproc, but 2 different ways. Notice the column headers up above, you have ias-component and process-type. Using ias-component:
[oracle@oracle-web-tier bin]$ ./opmnctl stopproc iascomponent=coreapplication_obis1 opmnctl stopproc: stopping opmn managed processes... [oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 3124 | Alive

coreapplication_obisch1 coreapplication_obijh1 coreapplication_obips1 coreapplication_obis1

| | | |

OracleBIScheduler~ OracleBIJavaHostC~ OracleBIPresentat~ OracleBIServerCom~

| | | |

3123 3121 3120 N/A

| | | |

Alive Alive Alive Down

Start it back up.

[oracle@oracle-web-tier bin]$ ./opmnctl startproc iascomponent=coreapplication_obis1 opmnctl startproc: starting opmn managed processes... [oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 3124 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 3123 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 3121 | Alive coreapplication_obips1 | OracleBIPresentat~ | 3120 | Alive coreapplication_obis1 | OracleBIServerCom~ | 3525 | Alive

process-type shutdown:
[oracle@oracle-web-tier bin]$ ./opmnctl stopproc processtype=OracleBIServerComponent opmnctl stopproc: stopping opmn managed processes... [oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 3124 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 3123 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 3121 | Alive coreapplication_obips1 | OracleBIPresentat~ | 3120 | Alive coreapplication_obis1 | OracleBIServerCom~ | N/A | Down

Note that I didn't use OracleBIServerCom~. It expects the full name of the component, in this case, OracleBIServerComponent. If you use the shortened name, you'll get this:
[oracle@oracle-web-tier bin]$ ./opmnctl stopproc processtype=OracleBIServerCom~ opmnctl stopproc: stopping opmn managed processes... ============================================================================= === opmn id=oracle-web-tier:9501 No processes or applications match the specified configuration.

Finally, bring the BI Server back up.

[oracle@oracle-web-tier bin]$ ./opmnctl startproc processtype=OracleBIServerComponent opmnctl startproc: starting opmn managed processes... [oracle@oracle-web-tier bin]$ ./opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------coreapplication_obiccs1 | OracleBIClusterCo~ | 3124 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 3123 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 3121 | Alive

coreapplication_obips1 coreapplication_obis1

| OracleBIPresentat~ | | OracleBIServerCom~ |

3120 | Alive 3803 | Alive

Fairly simple. For a full list of opmnctl commands, simply run ./opmnctl help and you'll get the following output:
[oracle@oracle-web-tier bin]$ ./opmnctl help usage: opmnctl [verbose] [<scope>] <command> [<options>] verbose: print detailed execution message if available Permitted <scope>/<command>/<options> combinations are: scope ------command --------start startall stopall shutdown options --------Start opmn Start opmn & all managed processes Stop opmn & all managed processes Shutdown opmn & all managed Start opmn managed processes Restart opmn managed processes Stop opmn managed processes Trigger opmn to reread opmn.xml Get managed process status Get DMS metrics for managed

processes [<scope>] startproc [<attr>=<val> ..] [<scope>] restartproc [<attr>=<val> ..] [<scope>] stopproc [<attr>=<val> ..] [<scope>] reload [<scope>] status [<options>] [<scope>] metric [<attr>=<val> ..] processes [<scope>] dmsdump [<dmsargs>] [<scope>] debug [<attr>=<val> ..] information [<scope>] set [<attr>=<val> ..] [<scope>] query [<attr>=<val>] launch [<attr>=<val> ..] phantom [<attr>=<val> ..] ping [<max-retry>] validate [<filename>] help usage [<command>] createinstance createcomponent deleteinstance deletecomponent registerinstance redeploy application unregisterinstance updateinstanceregistration updatecomponentregistration

- Get DMS metrics for opmn - Display opmn server debug Set opmn log parameters Query opmn log parameters Launch a configured target process Register phantom processes Ping local opmn Validate the given opmn xml file Print brief usage description Print detailed usage description Create an Oracle Instance Create a specified component Delete an instance and components Delete a specified component Register with admin server Redeploy the admin server

- Unregister with admin server - Update instance registration - Update component registration