HFM Is Not Accessible After Rebooting Database Server
(Doc ID 2252415.1)
Last updated on MARCH 15, 2019
Applies to:Hyperion Financial Management - Version 18.104.22.168.203 and later
Information in this document applies to any platform.
The customer has HFM, Planning & Essbase on single Exalytics server. MS SQL Database is on another Windows server.
Over the weekend as part of DB maintenance activity, they have performed below activities.
1. Stopped all Hyperion services
2. Rebooted database server
3. Restarted all Hyperion services (But HFM is not accessible after restarting services)
> Stopped all Hyperion services and stopped database
> Rebooted both Exalytics server and database server
> Started database and all Hyperion services
> Tested HFM which was accessible now
The customer wants to know whether this is a normal behaviour of the system or anything wrong from Hyperion side?
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