Metadata Is Not Loaded To ASO Cube Properly Using Load Rule In ODI
(Doc ID 1313824.1)
Last updated on APRIL 19, 2018
Applies to:Hyperion Essbase - Version 126.96.36.199.00 and later
Information in this document applies to any platform.
When using IKM SQL to Hyperion Essbase (METADATA) to load metadata file which is in parent/child format with all the properties (e.g. data storage, UDA....) using load rule file from ODI, the data seems to have been loaded incorrectly.
For example, the metadata has been loaded to Essbase were all labeled as store, when you expect that the data should be label only since you have used a load rule file to replace the data storage in the data file.
You have verified that the load rule and metadata file both work find when loading in Essbase and you have already set KM options :
RESTRUCTURE_DATABASE to "KEEP_ALL_DATA" ,and
KM LOG_ENABLED to 'YES"
But, since all members were actually loaded, the .log and .err file are blank.
How can we investigate such data related issue and why the properties were not loaded correctly?
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