Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Essbase-OBIEE-error "[nQSError: 22069] No dimension is available to project the pseudo measure."
Hi expterts,
Trying to import Essbase cube in rpd(obiee 12 c) and getting below error when select dimensions with measures.
Requirement is- Business dont want flattern measures. Any suggestion please.
Getting error:
error "[nQSError: 22069] No dimension is available to project the pseudo measure."
Answers
-
Which OBIEE 12c? There are many ....
You get that when using the wizard in the RPD to import the cube itself?
0 -
It has been a while since I had the dubious pleasure of Essbase through OBIEE, but I remember getting around this by having a dimension that was not filtered on, in my case this was lucky as we had the Essbase set up for multi-currency but in practice the client used only one, so we did not need to filter on that dimension to get the right numbers.
The 'hit' below seems to corroborate my memory; - (and yes I know, just add another dimension is not always a palatable solution)
According to this blog post for this error, when we select all dimensions in a cube, this error occurs. In that case we can add one extra dimension/attribute in the cube and delete that from presentation layer of OBIEE. It worked for us. We had 7 dimensions and 1 measure. We added an extra attribute in the cube.
http://www.wretch.cc/blog/tamataco/22068132
If anyone else has found a better solution to this I too would be interested!
0 -
12.2.2
0 -
Thanks for your response.
I am not able to open this blog. Are you?
On oracle support we found that we need to flattern measure hierarchy.But in my case, business dont want flatern hierarchy. So any other solution?
0 -
Sorry, you are right, I cannot open the blog either, but as I said the advice is basically add another dimension which only has one member in it, which as I say worked for me as I already had that one dimension, if you are looking at Essbase through Planning and Budgeting or similar then I know that 'add one dimension' translates as 'rebuild your entire application'.
Short of this you could also build an ASO equivalent with +1 dimension and export into that?
Then when you build the analysis you do not need to filter on that extra dimension and you do not get the error in question.
Personally I found Essbase through OBIEE so limited that building an export and piping it into database tables to emulate a classic star schema (again no small piece of work I know) actually gave me vastly faster report development times, report run times and more flexibility - and I was easily able to sell the solution to the business as a consequence.
0 -
Thanks,
Any help on how t create a dimesnion in OBIEE cube?
we cant extra dimesnion in Essbase.
0 -
You cannot create another dimension purely using modelling in OBIEE, sorry that is not an option.
You have three options; -
1. Remodel the database on the Essbase side
2. Create a new database that is identical to your current but with one new dimension with only one member, load data into it, use this for OBIEE reporting
3. Flatten your dimensions - see MOS note https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=268517618314221&id=1425294.1&displayIndex=2&_afrWindowMo… (you will need to log into MOS with a valid customer account) which confirms that flattening your dimensions is your only option, and as you have control over how you present that in the subject area I do not see that this is such an unpalatable alternative, unless the members in the dimension are highly volatile - however, please note that this bug is only supposed to be 11.1.1.5 OBIEE - and there is nothing against 12c for the same error, so if you are using the wizard in the rpd as @Gianni Ceresa asks, then I would log an SR and see if you can get them to recognise a new bug - if you do then kindly report the bug number here then others can also put their business need behind it and you have more chance of getting a fix
My unwritten Option 4 is to always leave an unfiltered dimension in your analysis but I realise that this is not likely to be workable for you without a single member dimension.
OBIEE truly being integrated into OBIEE with full multi-dimensional features would be top of my wish list, as I spend a lot of time in both EPM and OBIEE camps, and I currently find it hard to recommend OBIEE for reporting on Essbase sources.
0 -
I am working with Oracle on this issue , And will update this thread
0 -
I would be surprised if you get any traction with support, as they will allude to flattening the measures as an acceptable solution, but sincerely wish you success with this as I agree that the proposed solution is less than ideal, especially as Essbase cubes invariably have dynamic dimension members.
0 -
I hit this same issue today. A friend suggested a great workaround - just add a dummy attribute dimension to the cube. It has a minimal impact on the cube and it will allow you to display all the available true Essbase dimensions in your analysis.
Cheers,
Guillaume
0
