Components that are managed by OPMN should never be started or stopped manually. Use the opmnctl command line utility to start and stop system components.
Note: | If you attempt to use MaxL to shut down an Essbase instance that was started using OPMN, you are warned to use OPMN to shut down Essbase. In a Windows environment, before you launch Essbase, change the OPMN service (Oracle Process Manager (instanceName)) to start as a named user so that the shared network files are accessible. |
Use these commands to start, stop, and monitor Essbase from OPMN:
opmnctl status
Enables you to determine the status of system component processes.
opmnctl startproc ias-component=EssbaseInstanceName
Starts the system component named EssbaseInstanceName
opmnctl restartproc ias-component=EssbaseInstanceName
Restarts the system component named EssbaseInstanceName
opmnctl stopproc ias-component=EssbaseInstanceName
Stops the system component named EssbaseInstanceName
where EssbaseInstanceName is one of the following:
If you did not implement failover clustering, EssbaseInstanceName is the name of the Essbase instance that you entered when you configured Essbase Server.
If you implemented failover clustering, EssbaseInstanceName is the name of the Essbase cluster that you entered when you set up the Essbase cluster.
Note that the Essbase Server start and stop scripts redirect to OPMN. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
For more information on OPMN commands, see the Oracle Process Manager and Notification Server Administrator's Guide.
For troubleshooting and logging information, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.