Month: February 2013

Oracle Knowledge Base article 1488475.1

I have a colleague that has become quite the OBIEE expert over the last few months.  She loves OBIEE sometimes more than others, especially given the amount of patches that have come out.

A couple of months ago I upgraded her OBIEE implementation at a client to, but I noticed today that a new round of OBIEE patches were available.  So, how do you find out what patches are available?  Log into Oracle Support ( and search the Knowledge Base for article 1488475.1.  This article lists the patches available for various releases of OBIEE 11g.

OBIEE consists of the following:

  • Patch 16094198
  • Patch 16094192
  • Patch 16080520
  • Patch 16094205
  • Patch 16094211
  • Patch 16067995
  • Patch 16097082

This patch set was released on February 5, 2013

This is a cumulative bundle patch to go on top of current releases  (excluding FA

Patch 16094198 (1 of 7) Oracle Business Intelligence Installer. (generic)

Patch 16094192 (2 of 7) Oracle Real Time Decisions. (generic)

Patch 16080520 (3 of 7) Oracle Business Intelligence Publisher. (generic)

Patch 16094205 (4 of 7) Oracle Business Intelligence ADF Components. (generic)

Patch 16094211 (5 of 7) Enterprise Performance Management Components Installed from BI Installer (port-specific)

Patch 16067995 (6 of 7) Oracle Business Intelligence. (port-specific)

Patch 16097082 (7 of 7) Oracle Business Intelligence Platform Client Installers and MapViewer  (generic)


The Readme files for the above patches describe the bugs fixed in each patch, and any known bugs with the patch.

This patch is cumulative, and therefore contains all of the fixes included in the earlier,,, and patch sets.

However, lists of fixes from included patch sets need to be looked up in the respective patches’ readme files, and are not included in the above patches’ readme files.

The instructions to apply the above patches are identical, and are contained in the readme file for patch 16094198.

Please bear in mind, that the readme states to apply patch 13952743 for JDeveloper, too.

Oracle Hyperion Smart View Release

On February 18, 2013, a new patch for Smart View was released:  This release holds some pretty interesting new features that foreshadow the release of OBIEE

New Features:

  • Support for OBIEE through Smart View (if you are on OBIEE
  • New VBA functions to interact with OBIEE
  • Shared Connections can be stored in an XML file (used to provide access to OBIEE through Shared Connections).  Could be pushed with a software install to new users for example.
  • New document contents pane.  Think of this as a table of contents for Smart View information located in your Office document.
  • HsGetValue functions can be copied and pasted between files or Office applications (Why are you using HsGetValue? Hyperion Enterprise is dead, people.).
  • Support for Shared Connections in functions.  This is a nice feature for people building reports using Smart View.
  • New reporting object called an Office Table.  These are for Word only and look like a part of the Word document, but are refreshed using a Smart View connection.  Allows users to format the table using Word formats, but members and data come from Smart View.  That could be interesting for management or tax reporting that is done using Word.
  • POV will now support 5000 members.

Basically download the patch #16238382 and install using the SmartView.exe, or by auto deploy, or from Workspace, or now from OBIEE apparently.

One little gotcha that I found was that the Windows 64-bit version of 16238382 does not include both the 32 and 64 bit installers as previous Smart View patches have.  Keep that in mind if you are used to just grabbing one of the Smart View patches like me.

Here’s a link to Oracle’s Documentation Library for the release of Smart View:

Oracle Hyperion Smart View for Office Documentation Release


UPDATE – March 7, 2013:

Oracle has been contacting anyone that has downloaded this patch to inform them that the patch now includes the version.xml file that was originally missing in the patch.  The version.xml is needed to do automatic updates to Smart View through Workspace.  Setting up automatic updating is something that I normally don’t do because many users don’t have administrator rights on their computers.