Planning Web App Unresponsive After Applying Planning PSE And Essbase .025 Patchsets
(Doc ID 2472274.1)
Last updated on SEPTEMBER 25, 2019
Applies to:Hyperion Planning - Version 188.8.131.52.008 and later
Information in this document applies to any platform.
Encountering issues where Planning Refreshes caused the Planning service to stop without log info. As recommended, installed Planning PSE 28549776, and applied required Essbase component patches from version 184.108.40.206.023 to 220.127.116.11.025.
The following Essbase patches were applied:
- 27797123 - Essbase RTC .025
- 28396955 - Essbase Client .025
- 27797131 - Essbase Server .025
- 27797138 - Provider Services .025
After patch application and post-implementation steps, all services start, ahd the 8300 Listener port is open and the Planning process is loaded into memory. WebLogic shows the Planning service as running, but Planning is unresponsive.
The following message in the Planning1.log file that indicates the service changed to Standby mode:
#### <> <> <>
#### <[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <>
Also tried redeploying to WebLogic with no change in result.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document