This content has been marked as final. Show 8 replies
If you have OBIEE version 184.108.40.206 or higher, then you can use its native OLAP support instead of relying on the metadata generated by the AWM plugin. The native support bypasses the security filter workaround you had to do, so it should resolve your issue.1 person found this helpful
Does that involve creating the cube in OBIEE instead of AWM then?
Okay, I found this, which appears to explain it rather clearly. Thanks for point me in the right direction, I'll update this thread once I confirm if this method works with BI Administrator users.
Edited by: islan on Jan 22, 2013 8:43 AM
You appear to have found a good document to start from.
Using OLAP with OBIEE is a two step process.
(1) You define (and build) the cubes in AWM.
(2) You tell OBIEE about these cubes.
Prior to OBIEE 220.127.116.11, the only way to do (2) was to use the AWM plugin and map OBIEE to the generated cube views. But starting from 18.104.22.168 you can, instead, "import" the cubes using a dialog in the OBIEE admin tool. OBIEE will generate different SQL depending on which approach you take.
From that blog, it looks like the Admin Tool direct Data Source method requires it to be done locally on the BI server. Is this pretty much true?
I am attempting to setup the connection in Administrator Tool using the standard <machine name>:port:sid, with port being the default for JavaHost 9810, but I am now getting the following error: "nQSError: 77031] Error occurs while calling remote service AWImportService11G. Details: Error getting AW database version -- IO Error: Got minus one from read call".
Anybody know what this is about?
The link in your first posting points to the old-way of creating OBIEE metadata for OLAP objects.
Starting with OBIEE 22.214.171.124, it is much simpler as Oracle-OLAP is one of the data sources in BI-Admin Tool.
So do not use the old way.
Start with this doc:
For your other issue, you need this troubleshooting doc:
Note that even though it says OBIEE 126.96.36.199, the above two docs are applicable to 188.8.131.52 and future releases.
For security, you should define it in OBIEE instead of doing in OLAP.
Thanks, I was able to import directly from Admin Tool following the instructions in the Oracle Business Intelligence 11g Developer's Guide (pg. 315). This does get around the requirement for a security filter.