John post a great blog about extracting data from Essbase using calculate script. Here, I want to give another example with report script.
1. create a report script in Essbase and test it.
2. Copy the .rep file from Essbase server to ODI server if they are installed on separate machine.
3. If you haven't create source/target schema yet, please refer John's previous blogs for detail. I changed the data type from blank to char for all Essbase output columns manually.
4. Set the properties of LKM Hyperion Essbase DATA to SQL
EXTRACTION_QUERY_TYPE := ReportScript (default)
EXTRACTION_QUERY_FILE :=E:\report.rep(ODI server's path)
5.Save the interface then execute it.
Sunday, September 13, 2009
Monday, August 31, 2009
ODI-Extract Essbase metadata to oracle
John has released a wonderful post for this, however some guys met some issues when follow
that post, just like me. After changing some setting, it works now(version: 10.1.3.5).
1. Change the path of logFileName\errFileName
2. Make ODI do not generate quotes
2.1 go to topology
2.2 edit the Hyperion Essbase technology (phisical architecture)
2.3 at tab Language, column "Object Delimiter", delete the quotes and let it with no value.
3. Change the default value to "Char" at models->essbase model-> source application ->columns
4. Verify the LKM and IKM
LKM: LKM Hyperion Essbase METADATA to SQL
IKM: IKM SQL to SQL Append
that post, just like me. After changing some setting, it works now(version: 10.1.3.5).
1. Change the path of logFileName\errFileName
2. Make ODI do not generate quotes
2.1 go to topology
2.2 edit the Hyperion Essbase technology (phisical architecture)
2.3 at tab Language, column "Object Delimiter", delete the quotes and let it with no value.
3. Change the default value to "Char" at models->essbase model-> source application ->columns
4. Verify the LKM and IKM
LKM: LKM Hyperion Essbase METADATA to SQL
IKM: IKM SQL to SQL Append
Subscribe to:
Posts (Atom)