SQL Load from Oracle into 64 bit Essbase 9.3.1 - issue

Question

I have a sql load that works fine in 32 bit Essbase 7.1.5
Now I have setup the same sql load in a new 64 bit Essbase 9.3.1 environment. SQL runs. However when it retrieves it is not retrieving some fields "correctly". For example I have some extract functions in the SQL to extract the month or year from a date field. These are returning "0" now for the month or year. (the function syntax is correct as it works in the 7.1.5 environment. Plus for all my fields that are returning numeric dollar values, they are returning a value of "0" instead of the correct value (which it returns in the 7.1.5 environment).
The sql works correctly if run in SQLPlus. So Essbase is having the issue.
Any ideas?
Edited by: Sean V on Jun 5, 2009 7:48 AM

Answer 1

Hi Sean,
If you can do it yourself or someone else who can do it for you,
create a view in your db schema you are connected to and use a tool like Oracles SQLDeveloper (it's for free) or something similar to check your query result by select from your view.
This way you can hide your internal logic behind this view and no one has to worry about it.
From my POV this approach has no drawback but only advantage for you.
If it works as expected put the view into your rules file (I do assume you are using rules files)
Example (you need the CREATE VIEW privilege for you account(schema)):
CREATE v_dataload as
SELECT DIM_COL1 as year , DIM_COL2 as month, DIM_COL3 as market , DATA_COL1 as profit, DATA_COL2 as costs .... etc.,
In you rules file you then just put in the SELECT box: year,month, profit, costs ...
and in the table box: v_dataload
If you name you columns like the Dimension (Gen1) you have the comfort that essbase automatically maps the columns tho the appropriate dimension. (But remember a colum in Oracle can have only up to 30 Characters)
Back to you question:
If you get a correct result from you view when using SQLDeveloper but not in you rules file I would say it's very likely a ODBC driver problem.
If so, please check if you have installed the correct driver for your system. MERANT driver is the best choice as fare as I know.
In normal cases you never should have to cast anything into a VARCHAR, since exactly this is the job of the ODBC driver.
However, if everything fails and a cast (like Glen said) is the only way you can make it work put this cast into your view too.
CREATE v_dataload as
SELECT TO_CHAR(DIM_COL1) as year , TO_CHAR(DIM_COL2) as month, TO_CHAR(DIM_COL3) as market ,TO_CHAR( DATA_COL1) as profit, TO_CHAR(DATA_COL2) as costs .... etc.,
Regards
Andre
Edited by: andreml on Dec 16, 2009 12:52 PM