Last updated on JULY 29, 2016
Applies to:Hyperion Essbase - Version 184.108.40.206.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 :
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?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms