ODI Data or Metadata Load Takes Extremely Long Time When Using The Sunopsis Memory Engine As Staging Area
(Doc ID 1167437.1)
Last updated on OCTOBER 11, 2019
Applies to:Hyperion Financial Management - Version 188.8.131.52.00 and later
Hyperion Essbase - Version 184.108.40.206.00 and later
Hyperion Planning - Version 220.127.116.11.00 and later
Information in this document applies to any platform.
A Hyperion Planning metadata load via ODI that uses the Sunopsis Memory Engine as the staging area takes a very long time to complete. It does complete if left long enough but takes far longer than would normally be expected given the amount of rows to be loaded.
In an actual example seen by support a metadata load took longer than a full day to load just over 11,000 rows of metadata into a Planning application.
- The same symptoms could also be seen with Hyperion Planning data loads when using the Sunopsis Memory Engine as the staging area.
- The same symptoms may also be seen when loading data or metadata to Hyperion Financial Management or Essbase applications if using the Sunopsis Memory Engine as the staging area.
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
|Option #1 - Increase the memory allocated to the ODI JVM.|
|Option #2 - Use a schema in a physical RDBMS for the staging area rather than the Sunopsis Memory Engine.|