Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
HFM Patch 206 or 205

Hi
So I have applied the patch 206 hoping it would fix the issue Stopped consolidation enters scheduled stop status but never actually stops. This is actually defect fixed on 205 version but not on 206 per Read Me. But I have thought 206 would include all the fixes from 205 as well as any new fixes, i mean the Hyperion patches are cumulative. Am I wrong? Because it is still the issue even after applying patch 206. Cannot stop consolidations. It says Scheduled stop and parent members keep consolidating even though I stopped it.
Mikkis
Answers
-
For clarity, not all patches are cumulative. Some patches are for specific items (e.g Patch Set Exception). You would need to read the readme to understand if the patch is for a specific item or cumulative.
There are Details about patches in general on the Oracle site for example the below:
Available Patch Sets and Patch Set Updates for Oracle Hyperion Enterprise Performance Management Products (Doc ID 1400559.1)
https://docs.oracle.com/cd/E25290_01/doc.60/e25224/patchesupdates.htm
-
Hi Mikkis,
HFM 206 patch is a cumulative patch that includes all the previous patch fixes. I suspect that the issue you are facing may be a regression in 206.
If you are able to reproduce the issue, please submit an SR with support to investigate further.
Thanks,
Chandra
-
If a subcube (scenario/year/entity combination) is already started, HFM must wait for it to finish before we can stop. This is to prevent future integrity issue.
-
How long are you waiting for the consolidations to finish? I know we used to have the issue, but we're able to stop our consolidations on 206. I believe Suresh is correct and it may just be that if you try to stop a consolidation, it needs to finish the current entity it's working on(it can't immediately stop mid calculate) so if you're in the middle of 8 entities due to multithreading and you are working with high levels, there could be a long delay while it finishes.
It shouldn't take longer to stop than a normal consolidation though. That was happening during the original bug regarding the issue. So if I had a 30 minute consolidation, trying to stop it would just freeze it and even an hour later it still wouldn't stop.
-
Hi Joe,
Our consolidations take around 90 min. When I stop when the consolidation is at base level, it stops immediately, but when I try to stop at parent level, like the levels 3-5 (level 1 being highest parent), it won't stop immediately. It just keep running until the time it normally takes to consolidate that period if we don't kill it. It never froze on us.
Mikkis