Last updated on AUGUST 08, 2016
Applies to:Hyperion FDM Essbase Adaptor - Version 126.96.36.199.00 and later
Information in this document applies to any platform.
When processing in batch parallel mode, it is possible that the data file name that is used to copy to the Essbase server can be a duplicate of an existing file that is currently being loaded. The logic of the file naming convention is on line 544.
For example if you have three locations:
One of the locations may fail during a parallel batch run during the load.
The app log contains Essbase Error error "Object [EG58] already exists and is not locked".
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