So you might ask your Oracle Sales, what’s new in this Oracle BI EE version. Majority of the time, they will tell you a few features.
Here’s the site, Cumulative Feature Overview.
The objective of the tool is to help IT plan ahead to its upgrades and whether it is worth it. Obviously, I if you read my post on “OBIEE 188.8.131.52 Features that makes you upgrade today!”, you will find it absolutely worthwhile to upgrade!
Here’s how to use it:
I don’t usually send out information on Smart View patches but in OBIEE, there is one particularly resolved issue that needs to be highlighted and worthwhile to make your upgrade today. It is highlighted in blue below.
Oracle BI EE
19475349 — In reports created in the Smart View View Designer, if the associated data contained the hexadecimal value of 0x13, an invalid character error occurred, resulting in this message: “’!!’, hexadecimal value 0x13, is an invalid character.”
20295285 — Oracle BI EE content is not viewable in Smart View when called from an Oracle BI EE catalog shortcut link.
20698288, 20803386 — When retrieving data from a table in Oracle BI EE, the first column gets merged every 500th record.
20833815 — When more than three tables from Oracle BI EE are inserted into a worksheet, the cell positions of some tables are not maintained.
20912635 — Column order is not maintained in Smart View 184.108.40.206.200 after the BI Answers table is modified and a new column is inserted between two existing columns.
So I previously said that the last release which was 220.127.116.11.150120 was supposed to be the last patch for OBIEE. However, on the day of Pluto Fly By, Oracle released 18.104.22.168.150714. Oracle only states that this patch only fixes a major bug for Oracle Business Intelligence Third Party with bug number 20247002. I searched for this bug and could not find relevant information.
If you are stable on 22.214.171.124.150714, then I would probably not patch to this version. For more information on Oracle Support page, you can go here.
OBIEE Patch 126.96.36.199.150120 ODBC driver returned an error
After patching to 188.8.131.52.150120 it so happens that where Total Rows are used, there may be possibilities that you get “ODBC driver returned an error…..Cannot function ship the following expression…”.
Yes, 184.108.40.206.141014 also has the same problem described previously in this post here. Actually, a interim fix has been issued for a few weeks now but I wanted to do deep dive tests before I tell everyone that this works. It works!!!
Download the Patch 19599154 here. Alternatively, search in Oracle Support for Patch Number 19599154 Windows x64 yourself to get this patch. You have options of fixing 141014 or 150120.
For more details of the original bug issue, please view below.
OBIEE BUNDLE PATCH 220.127.116.11.150120
The Patch is platform specific and is available for:
IBM AIX on POWER Systems (64-bit)
MS Windows (32-bit)
MS Windows (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This patch set is available for Oracle Business Intelligence Enterprise Edition 18.104.22.168.0, 22.214.171.124.1, 126.96.36.199.131017, 188.8.131.52.140114, 184.108.40.206.140225, 220.127.116.11.140415, 18.104.22.168.140527, 22.214.171.124.140715 and 126.96.36.199.141014.
This is provided as single Bundle Patch 20124371 and is comprised of the following:
Patch 16913445 – 1 of 8 Oracle BI Installer (BIINST)
Patch 18841070 – 2 of 8 Oracle BI Publisher (BIP)
Patch 18657616 – 3 of 8 EPM Components Installed from BI Installer 188.8.131.52.0 (BIFNDNEPM)
Patch 18841084 – 4 of 8 Oracle BI Server (BIS)
Patch 18841078 – 5 of 6 Oracle BI Presentation Services (BIPS)
Patch 17300045 – 6 of 8 Oracle Real-Time Decisions (RTD)
Patch 16997936 – 7 of 8 Oracle BI ADF Components (BIADFCOMPS)
Patch 18841089 – 8 of 8 Oracle BI Platform Client Installers and MapViewer
NOTE: Also required to be downloaded:
OBIEE Patch 184.108.40.206.141014 ODBC driver returned an error
After patching to 220.127.116.11.141014 it so happens that where Total Rows are used, there may be possibilities that you get “ODBC driver returned an error…..Cannot function ship the following expression…”.
The way to fix it is to edit the fact columns and change the “Aggregate Rule (Total Rows)” to “Sum” instead of Default. The strange thing is that the first fact column can be left as default from my current observations. Hope this helps everyone who encounter this error.
Update 25-November-2014: For row totals, when percentage is present, changing to SUM will cause percentage to add up which is wrong. Temporarily may need to change report based aggregation methodology to none so that incorrect figures are not displayed. I am still working on how to fix this issue.