Essbase & EAS Patches available

Last Thursday, Oracle issued a slew of patches for Essbase and its peripheral components (EAS, client, Run Time Client).  Typically Oracle has kept Essbase Studio and APS aligned with the same patch level, but .503 patches have not appeared for those products yet. These patches address bugs at the .500 patch level so I highly recommend applying this latest round of patches if you are on Essbase

Patch Numbers:

Essbase Defects Fixed:

Defect Number Defect Fixed
19485568, 19190554 Using linked partitions and making changes to the outline, followed by running outline sync, may cause the application to terminate abnormally.
19358183 The Essbase Server can terminate abnormally when running concurrent requests to calculate the database as well as run queries.
19339625 When updating a partition definition, validating and updating the outline at the same moment can abnormally terminate the application.
19288595 In some cases, UDAs are not updated when trying to synchronize the outline of a replicated partition.
19178010 When a query is too large, an aggregate storage database can terminate abnormally.  With, it returns an error:
ERROR – 1200613 – Internal error: Query is too large and cannot be executed. The product of member counts across all dimensions in the query exceeds 2^64.
19150857 Using Smart View with Essbase Release with SSOPTIMIZEDGRIDPROCESSING set to TRUE in essbase.cfg, data can be submitted by users to intersections that are secured as “read-only”.
19150857 The .db file can become corrupted under concurrent calculation requests.
19021424 Empty rows are inserted while performing a zoom-in on a member in Smart View Client.
18977312 On an aggregate storage database, an MDX formula can return inconsistent results.
18148156 A trigger can fail when ORACLEHARDWAREACCELERATION is set to TRUE in essbase.cfg.

EAS Defects Fixed:

Defect Number Defect Fixed
18684575 A data load rules file created in Administration Services console cannot be used by MAXL.

July 2014 Oracle Quarterly Critical Patch Availability

Today Oracle released a list of vulnerabilities to the EPM and related BI software along with a host of other products.  See the full announcement here: http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html

This one was interesting as my beloved Hyperion products were mentioned.  Seven vulnerabilities were identified with Hyperion products.  It was interesting that most of the patches for these vulnerabilities have been out for a little while, so hopefully you have already mitigated some of these.  Here is list of defects for Hyperion:

7-15-2014 5-25-14 PM

If you clicked the link from the announcement to My Oracle Support note number 1666884.1, the Patch Set Update and Critical Patch Update July 2014 Availability Document, will give you the patches to fix each vulnerability.

Patch Availability for Oracle Hyperion Analytic Provider Services

Product Home Patch Advisory Number Comments SPU Patch 17767293 CVE-2014-4246 PSU SPU Patch 18148649 CVE-2014-4246 PSU

Patch Availability for Oracle Hyperion BI+

Product Home Patch Advisory Number Comments SPU Patch 17529887 and SPU Patch 18383790 CVE-2014-0436 PSU (included in 17767293) and Client Installers PSE SPU Patch 18659116 and SPU Patch 18856417 CVE-2014-0436 I could not find these patches. The links do not show the patch.


Patch Availability for Oracle Hyperion Common Admin

Product Home Patch Advisory Number Comments CPU Patch 18672071 CVE-2014-4269, CVE-2014-4270 PSU for Shared Services CPU Patch 18659116 CVE-2014-4269, CVE-2014-4270 I could not find this patch either.


Patch Availability for Oracle Hyperion EAS

Product Home Patch Advisory Number Comments Admin Server Patch 17417347Admin Console Patch 17417344 Released January 2014 PSU, should also be included in PSU Admin Server Patch 17277761Admin Console Patch 17277764 Released January 2014 PSU Admin Server Patch 17545122Admin Console Patch 17545124 Released January 2014 PSU


Patch Availability for Oracle Hyperion Enterprise Performance Management Architect

Product Home Patch Advisory Number Comments SPU Patch 17529887 and SPU Patch 18383790 CVE-2014-4203, CVE-2014-4206 PSU and Client Installers PSE SPU Patch 18659116 and SPU Patch 18856417 CVE-2014-4203, CVE-2014-4206  I could not find this patch either.


Patch Availability for Oracle Hyperion Essbase

Product Home Patch Advisory Number Comments SPU Patch 18505489 CVE-2014-4271 PSU SPU Patch 18520684 CVE-2014-4271 Patch Set Update Exception (PSE): (18520684)


Patch Availability for Oracle Hyperion Strategic Finance

Product Home Patch Advisory Number Comments CPU Patch 14593946 Released April 2014 PSU CPU Patch 17636270 Released April 2014 PSU


In addition to the application patches, we also find that WebLogic Server is listed.  This is important because it is part of our installation of EPM 11.1.2.x and most of us take it for granted.

Patch Set Update Availability for Oracle WebLogic Server

Product Home Patch Advisory Number Comments
Oracle Java SE home JDK/JRE 6 Update 81:

See Note 1492980.1How to Maintain the Java SE Installed or Used with FMW 11g Products
Oracle JRockit 28.x home R28.3.3- Patch 18763693
WebLogic Server home PSU Patch 18040640 CVE-2014-2480, CVE-2014-2481, CVE-2014-4256, CVE-2014-4242, CVE-2014-4253, CVE-2014-4267, CVE-2014-4255, CVE-2014-4254, CVE-2014-2479, CVE-2014-4210, CVE-2014-4241, CVE-2014-4217, CVE-2014-4201, CVE-2014-4202 See Note 1306505.1Announcing Oracle WebLogic Server PSUs (Patch Set Updates)For CVE-2014-4256, see Note 1903763.1, Download Request for Security Configuration


Also note in the announcement that there is a patch for OBIEE’s Mobile App Designer.

Patch Availability for Oracle Business Intelligence App Mobile Designer

Product Home Patch Advisory Number Comments SPU Patch 18794832 CVE-2014-4249 Must delete existing MAD deployment and install this one.  Check the readme.


This appears to be a replacement for the entire MAD install.  Going forward, I will use the Oracle BI Mobile App Designer patch 18794832 instead of the older 17220994 patch.  This patch came out on 6/3, so they aren’t very good about announcing these patches.  I guess that’s why we should be reading these quarterly announcements to find out what has been fixed.


EAS is finally Java 1.7 Compatible!

Yesterday afternoon I received the latest Oracle Security Alert with the Critical Patch Update for January.  As I looked through the list, I saw that EAS – was listed.  After checking out the readme files on the patches, the one of the defects fixed was Java 1.7 compatibility.

This has been a thorn in Essbase Administrator’s sides for quite awhile since most JRE installations want to update automatically to the latest version by default.  Now you can update your JRE to 1.7 without fear of breaking your EAS console.

Here are the patches that you need:


  • Server: 17545122
  • Console: 17545124


  • Server: 17277761
  • Console: 17277764


  • Server: 17417347
  • Console: 17417344

Issue with restarting Essbase Administration Services

I wanted to send a quick note of thanks to Sundeep Reddy for his blog post about recreating a corrupted cwallet.sso file when EAS would not restart.  I had this exact thing happen today at a client and his instructions are spot on.

I did get an error that there was no JDK folder inside the …/Middleware/oracle_common directory, so I copied the …/Middleware/jdk160_29 directory and its contents to …/Middleware/oracle_common/jdk and then the orapki tool ran fine for me.

Hyperion Essbase: Issue with restarting Essbase Aministration Services EAS when EAS hung up.

Oracle HTTP Server timeouts

I’ve been to several clients that have large calculations, whether they are very complicated or maybe it’s just a large cube that has a less than optimal calculation (i.e. CALC ALL;).  One thing that was driving me crazy with Essbase Admininstration Services (EAS) was that when I was running one of these slow calculations, I would get an error after about 5 minutes that looked like an application crash.  When these faux crashes happen, the calculation clearly is still executing on the applicaiton based on the sessions information in EAS and the fact that the ESSSVR.exe for that application is still using CPU on the server.

Sure, you can run the calculations in the background to get by or execute them via MaxL, but sometimes you just want to run a process interactively.  I finally dug in and did some searching on timeouts in the EPM system. 

At one of my clients, we were trying to reload data to a cube that was just migrated to  There were 8 – 2 GB files that we were loading, so it was taking awhile.  Each time, the job would error out because of a timeout and cause the Essbase server to crash.  My client was getting irritated, and I couldn’t figure out what was going on.  I had similar issues at another client with a calculation, so I started wondering if there was a timeout somewhere. 

That’s when I realized that I have been using the OHS port for EAS all along (http://foundationServer:19000/easconsole/easconsole.jnlp).  This happened in the thick client and thin client consoles with the 19000 port, but does not happen with the 10080 port.

I did some searching and found that business rules can timeout if they run more than 5 minutes from Workspace, which is the same timeout value I had with my EAS data load.   

So, since I have OHS here, I decided to give it a shot.  I edited the mod_wl_ohs.conf file in NotePad and under EAS and EAS Console, I set the timeout value to 14400 (4 hours).  I then stopped and started OHS, and when I tested it – it worked like a charm.

 Here’s what I did:

 Oracle HTTP Server (OHS)

  1. Edit the following file:
  2. Add (or edit, if already present) the following parameters:
    WLIOTimeoutSecs 14400
    WLSocketTimeoutSecs 14400
    to the sections for EAS and EASConsole. Each section begins with an XML tag, for example:

<LocationMatch ^/eas/>


<LocationMatch ^/easconsole/>


Add the new “WLIOTimeoutSecs 14400” and “WLSocketTimeoutSecs 14400” properties as new lines within the tags, for example:

<LocationMatch ^/eas/>
     SetHandler weblogic-handler
     WeblogicCluster easserver01:10080
     WLIOTimeoutSecs 14400
     WLSocketTimeoutSecs 14400

<LocationMatch ^/easconsole/>
     SetHandler weblogic-handler
     WeblogicCluster easserver01:10080
     WLIOTimeoutSecs 14400
     WLSocketTimeoutSecs 14400

  1. Restart the Oracle HTTP Server after the modifications are complete.