Month: September 2013

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.

OBIEE patching

Just last week I installed OBIEE and patched it to version which was released back in July, I believe.  I went to my trusty Oracle Support document (Doc ID 1488475.1), and found that someone from Oracle had gutted the article of virtually all helpful information on the various OBIEE patches available for versions and  Thankfully, I was able to find Doc ID 1566124.1, which states the patches that make up OBIEE

The six OBIEE-specific patches are combined into one download as patch number 16556157.  Also required during the patching is patch number 16569379.  These patches are available on the My Oracle Support site ( and are installed as previously covered on this blog.  Be sure to read the readme file in the Patch 16453010 folder for any questions.

Patch 16556157 – OBIEE BUNDLE PATCH (Patch) is comprised of the following patches, which are not available separately:

  • Patch 16453010 – Patch (1 of 6) Oracle Business Intelligence Installer (BIINST)
  • Patch 16849017 – Patch (2 of 6) Oracle Business Intelligence Publisher (BIP)
  • Patch 16916026 – Patch (3 of 6) Enterprise Performance Management Components Installed from BI Installer (BIFNDNEPM))
  • Patch 16850553 – Patch (4 of 6) Oracle Business Intelligence Server (BIS)
  • Patch 16842070 – Patch (5 of 6) Oracle Business Intelligence Presentation Services (BIPS)
  • Patch 16869578 – Patch (6 of 6) Oracle Business Intelligence Platform Client Installers and MapViewer

Also you must download:

Patch 16569379 – Dynamic Monitoring Service patch

Oracle states the following caveats as well:

  • Be aware that a small number of the bug fixes that became available in the through Suite Bundle Patches are not available in the Suite Bundle Patch. Carefully review the list of bugs that are fixed in this Suite Bundle Patch before applying it to your system.
  • Oracle Exalytics customers must not install this Oracle Business Intelligence Suite Bundle Patch unless it is certified for the specific Oracle Exalytics Patch or Patchset Update that they are applying. For more information see Oracle Fusion Middleware Installation and Administration Guide for Oracle Exalytics In-Memory Machine and the Oracle Exalytics certification information.
  • For Oracle Fusion Applications customers, this Oracle Business Intelligence Suite Bundle Patch will be applied as part of a Fusion Applications installation or upgrade. Oracle Fusion Applications customers must not apply this Suite Bundle Patch independently.
  • The Oracle Business Intelligence Suite Bundle Patch is cumulative and might include patches that you might have already applied to the Oracle BI system. Therefore, when you install the Suite Bundle Patch, you might see warning messages that indicate that earlier patches are being rolled back. These warnings simply indicate that oPatch is working correctly, and do not require any action.
  • If you have horizontally scaled out the Oracle BI system on to multiple machines, then you must apply the Oracle Business Intelligence Suite Bundle Patch and the Dynamic Monitoring Service patch to all machines in the cluster.
  • When the installation of the Suite Bundle Patch is complete and the Oracle BI system is running again, end users might experience unexpected behavior due to pre-existing browser sessions that cache javascript from the earlier Oracle BI release. To avoid unnecessary support requests, ask all end users to clear their browser cache.

Exalytics First Impressions

For all of the much deserved hype surrounding the famed Oracle Exalytics platform (it’s 40 cpus of processing power, 1 Terrabyte of RAM, available flash disk drives, optimized in-memory data retrievals, etc.); the Exalytics server is just another 64-bit Linux server to the software installer. I must admit, I was a little disappointed. I was so geeked out to work on an Exalytics server and then I found out that the install is pretty much exactly what I had done on a 64-bit Linux server just a couple of months ago. The beauty of Exalytics, is that the installation of EPM is exactly the same as a 64-bit Linux server install.

Perhaps a little back story is in order. The client that I am working with for this project ordered two Exalytics servers: one for production and one that was to be split between development and test. The client purchased the EPM/BI Foundation Suite, but doesn’t have any plans to implement OBIEE for this phase of the project. The Exalytics servers were purchased to support the EPM suite, not OBIEE and Times Ten as most Exalytics servers are targeted. In fact, Times Ten was specifically not purchased by the client and was not to be installed.

Oracle has an excellent team that handles the business end of these Exalytics servers. They have a great process worked out to make sure that the clients receive exactly what they order on tight timeframes. The amount of time passed from the signed order was delivered to Oracle to delivery of the servers was no more than eight days. That is just a testament to the organization of Oracle’s team behind these servers.

So, the order for this build was to install as many EPM components on the Exalytics server as possible, and utilize Windows servers for the non-compatible components. The EPM system in this case includes Essbase, Planning, HFM, FDM, EAL, DRM, ODI, FR, Web Analysis, Calc Manager, and EPMA. Of course, not all of these products are compatible with Linux and/or Exalytics (HFM, FDM, and the EPMA Dimension Server to name a few).

The installation went smoothly for the most part. Splitting one box for use with two different environments required different Middleware Homes and port numbers which were fun to try and sort out. Splitting one server for two environments appears to be easier beginning with as the EPM System Registry now stores the port numbers for more products than in

Oracle has a special documentation library just for Exalytics here:  This is where you can find great information as to what products are supported on the Exalytics hardware.