Utilities to Import Oracle Express v6 eif files to flat files or DB tables

Question

We are seeking advise on how to import data from Express V6 to Hyperion Essbase. We have eif files and would like to import the data to DB tables of flat files for Import to Essbase. Is Oracle OLAP 10g required for this?
Thanks,
Tim Kline
at&t - IT
(407)-858-8454

Answer 1

It's probably dimension order. When you use a for statement, you are specifying the order in which you want things to be processed. I copied your statement as the order. What you really need to do is a describe on one or more of your variables:
describe f.minsThe system will respond with something like (I've made this up):
DEFINE F.MINS VARIABLE INTEGER <time product geography...>The describe command lists the dimensions from fastest varying to slowest. Unfortunately, for historical reasons, the FOR command takes its arguments from slowest to fastest. So (ignoring the rest of the dimensions I didn't list) you would
use a FOR statement like this for optimum looping:
FOR ...GEOGRAPHY PRODUCT TIMEYou don't really need to list time (it only has one value), but it doesn't hurt anything. What is going on here is we store values in the AW as an (approximately) linear array, ignoring some complications, and if you specify the "right" order, we will pull all the values on one page before going to the next page. If you don't specify the "right" order, you will be pulling each value from a different page, and doing a ton of I/O. With a command like REPORT, which does its own looping, it tends to loop in the optimal order internally.
Rearrange your dimensions on the FOR statement in order to optimize your looping.
If you use the script you already have, you will need to make one additional change to it. You either need to delete the existing program:
DELETE EXPORT_ITbefore you re-define it or make it active:
CONSIDER EXPORT_IT before you can re-populate the text. I frequently do:
DEFINE PROGRAM EXPORT_IT
CONSIDER EXPORT_ITwhen I am using a script to create a program. You will see an error on the DEFINE after the first time, but you can ignore it. You might want to DESCRIBE the program to make sure you have the text you expect.
Jim