Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 212 Oracle Analytics News
- 42 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
Integrating OBIEE 12C(12.2.1.4) with Essbase 11.2.1.4

We want to federate Oracle Essbase multidimensional sources(aggregated data from relational sources) with relational data sources(detailed facts).
Is there any bad known issues between these versions besides issue with bi admin tool?
OBIEE 12C and Essbase 11.1.2.4 integration issue
We are moving from OBIEE 10g + Essbase 11.2.1.4
Answers
-
That's an extremely wide and open question to say the least. There can be many issues but the most important ones / ones with the largest impact are in the cube design itself rather than the integration.
0 -
We know about many issues(obiee 10g+9.7,obiee 10g 10g+11.2.1.4) but I mean in General.
Are they compatible with each other?
Because we are choosing actual appropriate versions and we cant stop later))
0 -
Have a look at the certification matrix.
Essbase 11.1.2.* is certified for OBIEE 12.2.1.4.
0 -
I read it but
I faced the issue and the answer was
"As per Oracle SR, Solution is to use OBIEE 12.2.1.3 Admin Tool as OBIEE 12.2.1.4 Admin tool is not certified with imports from Essbase Version 11.1.2.4.X per Per BUG 27376664 and certification Doc ID 1109260.1"
And I want to understand does this integration have another huge bugs or not
0 -
That's an inacceptable answer from them since 12.2.1.3 will be out of error correction support innone month.
0 -
I hate what about to write but ....
Technically it isn't a totally blocking issue, the 12.2.1.4 Admin tool seem to not be certified for the import of an 11.1.2.4 cube (is there really such a thing like a certification for the import wizard of the Admintool? Never saw one, and the bug linked isn't accessible). This doesn't mean it doesn't work, just that the Admintool can't import the cube. If you get the cube into the RPD by another way (that's where 12.2.1.3 could be used) it must work as certified for OBIEE/DV etc.
What would be needed is to have access to that bug and the fix Oracle had to develop. That reply is July 2018, things had to change in the meantime!
0 -
.So we should have 2 installed version of BI EE 12C(12.2.1.2 and 12.2.1.4) on our development servers?
First only for importing cubes from essbase and second to develop with?
Is there any way to save and copy any files from 12.2.1.2 to anywhere 12.2.1.4 and don't user 2 servers?
Ive tried to copy all files
from
12.2.1.2 catalog c:\Oracle\Middleware\Oracle_Home\bi\bifoundation\server\bin\
to
12.2.1.4 catalog c:\Oracle\Middleware\Oracle_Home\bi\bifoundation\server\bin\admintoolessbase
and create new admintooless.cmd in c:\Oracle\Middleware\Oracle_Home\user_projects\domains\bi_domain\bitools\bin\
"SETLOCAL
set DOMAIN_HOME=c:\Oracle\Middleware\Oracle_Home\bi\bin\..\..\user_projects\domains\bi_domain
call "C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\server\bin\admintoolessbase\admintool.cmd" %*
ENDLOCAL"
but with no success
"Error: Unable to access jarfile C:\Oracle\Middleware\Oracle_Home\bi\bifoundation
\endpointmanager\jlib\bi-endpointmanager-impl.jar"
0 -
Have found patch.
Wow, impossible. Now I can import essbase metadata to bi repo)
0 -
Awesome, thanks for the update!
So the SR guys were wrong and @Gianni Ceresa the reply being from July '18 doesn't invalidate my statement since it is a product defect and suggesting to mixing Admin Tool versions is just beyond wrong.
0 -
I agree with you, but you know the kind of answers SRs are having lately ...
0