OPMN Not Cleanly Stopping All Application Processes (ESSSVR) When Shutting Down Essbase, Locking Applications
Last updated on APRIL 18, 2018
Applies to:Hyperion Essbase - Version 220.127.116.11.000 and later
Information in this document applies to any platform.
Using OPMN to shutdown the Essbase Server, if a process is being run on a database, e.g a calculation, the ESSBASE process is stopped but the ESSSVR process is left running and never shuts down. When Essbase is started back up, the application fails to start.
The correct behavior would be the ESSBASE process will be shutdown and once the process that is running on the database completes, the ESSSVR process will then be shutdown.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms