Exporting Data in Replace Mode with the Essbase Adapter ESS11X-G4-H Does Not Clear the Last Entity Listed in the Export File

(Doc ID 1381538.1)

Last updated on AUGUST 01, 2016

Applies to:

Hyperion FDM Essbase Adaptor - Version and later
Information in this document applies to any platform.


When using FDM with Essbase Adapter ESS11X-G4-H and Selecting the Replace Method to load data to Essabse, the system does not perform the clear data on the last Entity contained in the export file, and the entity listed first is cleared twice.

The Essbase applicationname.log shows the clearing action twice for the first entity and the last entity is not referenced. For example, with the following file generated by FDM with the Essbase Basic/Demo application:


"Sales" "Boston" "Camera" "Actual" "Jan" "2011" 10
 "Sales" "New_York" "Camera" "Actual" "Jan" "2011" 14
 "Sales" "Phoenix" "Camera" "Actual" "Jan" "2011" 15

The demo.log in C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\essbase\essbase_0\app\Demo reports:

[Mon Nov 28 16:39:02 2011]Local/Demo/Basic/admin@Native Directory/1484/Info(1012555)
Clearing data from [Jan] partition with fixed members [Market(Boston);Scenario(Actual)]
 [Mon Nov 28 16:39:02 2011]Local/Demo/Basic/admin@Native  Directory/5752/Info(1012555)
 Clearing data from [Jan] partition with fixed members [Market(Boston); Scenario(Actual)]
 [Mon Nov 28 16:39:02 2011]Local/Demo/Basic/admin@Native  Directory/7056/Info(1012555)
 Clearing data from [Jan] partition with fixed members [Market(New_York); Scenario(Actual)]



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