SmartView Essbase Ad-Hoc and EPM 11.2
Author: Dave Shay | 2 min read | May 19, 2020
Are you getting a pop-up error in SmartView when trying a top-level SmartView ad-hoc retrieve from Essbase? In my case, I got a weird Java message complaining about “essggridoption.setAncestorTop().”
Our culprit here is a combination of the order by which Essbase 11.1.2.4 patches were automatically applied when EPM 11.2 was installed, and perhaps some funny business involving how files revert to read-only status in Windows Server 2019.
The EPM 11.2 installer automatically applies these Essbase 11.1.2.4 patches where appropriate:
Your problem here is this: The Essbase Java API files used by Analytic Provider Services (APS) don’t match what the Essbase server expects. There’s an Essbase API protocol mismatch here!
The patches automatically applied by the EPM 11.2 install tool are stored here:
\Oracle\Middleware\oracle_common\OPatch\Patches\patchFiles
Sure enough, there’s a subfolder here for 29749671.
Stop your EPM services on the APS host machine(s).
Attempt to copy \Oracle\Middleware\oracle_common\OPatch\Patches\patchFiles\29749671\files\common\EssbaseJavaAPI\11.1.2.0\lib\
to
Oracle\Middleware\EPMSystem11R1\common\EssbaseJavaAPI\11.1.2.0\lib\
choosing to overwrite the existing files.
One of three things will happen:
The copy happens OK and you may restart services.
It complains that a Java process is using one of the files you’re trying to overwrite. You’ll have to use your Windows Task Manager to hunt down and terminate those processes (or reboot). Then try again.
It complains the target file is read-only. If this is the case, right-click the target file, click Properties, and remove the Read-Only flag. Then try again.
#2 above happened to me. After I killed the offending process, replaced the files and restarted services, SmartView worked as expected!
