Change in DataExport option

I was helping out a colleague of mine so I was investigating why a script that would export data in 11.1.2.2 was not exporting anything in 11.1.2.4. Started by only using

Essbase would respond with:
Received Command [Calculate] from user [admin@Native Directory] using [EXP.csc]
DataExport detects Dynamic Calc member [KittenMbr] in the range. Exporting Dynamic Calc data may slow down performance.
This DataExport operation will export data from existing blocks only. Any FIX on sparse dynamic calc members will be ignored. Use DATAEXPORTNONEXISTINGBLOCKS ON option to export data from all potential blocks.
Data Export Completed. Total blocks: [15]. Elapsed time: [0.023].
Total Number of Non-Missing cells exported: [60].

Now this is a cube with many Sparse members on DynamicCalc – I got no influence on this part -, which was mitigated in the old version by using:
DataExportDynamicCalc ON;
DATAEXPORTNONEXISTINGBLOCKS OFF;

Same result. Hmm interesting.

After 2 minutes on Metalink, we were able to find Document 2123909.1, where Oracle development explains changed the behaviour. Short story: you are supposed to use them as:
DataExportDynamicCalc ON;
DATAEXPORTNONEXISTINGBLOCKS ON;

After using it as above, I get the response from Essbase:
Received Command [Calculate] from user [admin@Native Directory] using [ESC.csc]
DataExport Warning: This DataExport operation will export a total of [3958416] blocks. Exporting dynamic calc members from all blocks has significant performance overhead. Use DATAEXPORTNONEXISTINGBLOCKS OFF option to export data from existing blocks only.
Data Export Completed. Total blocks: [45]. Elapsed time: [508.234].
Total Number of Non-Missing cells exported: [180].

Do I got to add be careful with this? if nothing else is an indication, just look at how much more time it took for export of still such a small amount of data.

Leave a Reply

Your email address will not be published. Required fields are marked *