BIEE access to Essbase and Oracle

Question

I need to access Essbase through BIEE, and lookup the description from Oracle DB using the Essbase id retrieved at particular levels.
I experienced that even though I select two dimensions out of the five dimensions, all dimensions will be accessed with crossjoin as below:
With
set [MATERIALS5] as '[MATERIALS].Generations(5).members'
set [GEOGRAPHY5] as '[GEOGRAPHY].Generations(5).members'
set [YEARS2] as '[YEARS].Generations(2).members'
set [DATE5] as '[DATE].Generations(5).members'
set [Axis1Set] as 'crossjoin ({[MATERIALS5]},crossjoin ({[GEOGRAPHY5]},crossjoin ({[YEARS2]},{[DATE5]})))'
select
{[MEASURES].[AMOUNT]} on columns,
NON EMPTY {[Axis1Set]} properties ANCESTOR_NAMES, GEN_NUMBER on rows
from [CUBE01.JP]
Basically, I only retrieve month only and also the month properties at level 3 of "DATE" dimension. Why is 'DATE5' needed when I need MONTH only (which is 'DATE3')? Is the above an optimal path for the Essbase access?
My experience is that I see the memory grows up and up and then reaches around 2GB and then BIEE returns an error. Then I also need to restart BIEE so that I can rerun the query.
Can anyone give me any hints how to tune up the access and address this problem?
Thanks

Answer 1

Hi,
Are there any document that describes how to interpret the following generated statement?
>>>
With
set MATERIALS5 as 'MATERIALS.Generations(5).members'
set GEOGRAPHY5 as 'GEOGRAPHY.Generations(5).members'
set YEARS2 as 'YEARS.Generations(2).members'
set DATE5 as 'DATE.Generations(5).members'
set Axis1Set as 'crossjoin ({MATERIALS5},crossjoin ({GEOGRAPHY5},crossjoin ({YEARS2},{DATE5})))'
select
{MEASURES.AMOUNT} on columns,
NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
from http://CUBE01.JP
<<<
Thanks