OBIEE (aka BP6) is out and until MOS hosts a proper tracking note, here is the list of all patches making up this patch set with direct links.

Patch 15844023    Patch (1 of 7) Oracle Business Intelligence Installer
Patch 15844066    Patch (2 of 7) Oracle Real Time Decisions
Patch 14800665    Patch (3 of 7) Oracle Business Intelligence Publisher
Patch 15843961    Patch (4 of 7) Oracle Business Intelligence ADF Components
Patch 15844096    Patch (5 of 7) Enterprise Performance Management Components Installed from BI Installer
Patch 14791926    Patch (6 of 7) Oracle Business Intelligence
Patch 15839347    Patch (7 of 7) Oracle Business Intelligence Platform Client Installers and MapViewer

As always: don’t forget JDEV patch 13952743



While I was off, Oracle released OBIEE which is another bugfixing patch set which doesn’t bring in new functionality but irons out quite a few quirks.

Here you can find the main MOS article detailling the patches making up this patch set as all bugs fixed in it.

By the way…make sure you don’t forget JDEV patch 13952743.



Patch is here and can be downloaded from MOS.

Once more it’s a 7-pack patch and here are the patch numbers and direct links:

Patch 14285344: Patch (3 of 7) Oracle Business Intelligence Publisher
Patch 14415773: Patch (5 of 7) Enterprise Performance Management Components Installed from BI Installer
Patch 14405222: Patch (6 of 7) Oracle Business Intelligence
Patch 14409674: Patch (7 of 7) Oracle Business Intelligence Platform Client Installers and MapViewer

Documentation’s here: https://updates.oracle.com/Orion/Services/download?type=readme&aru=15499675



In one of my recent posts I was talking about the different patch levels for and and their impact on functionality and the MDX produced. Interestingly enough not all of the problems appear with every cube outline imported into OBIEE. Oracle initially had troubles reproducing some of the errors (using the normal OOB Essbase sample cubes).

To recap: the changes to the connectivity DLLs first introduced in patch 7349048 (for enabled OBIEE / Essbase security integration, but had some side effects. Performance dropped up to 3000% in some cases, standard report level totals or pivot totals stopped working etc. This is mostly due wrongly produced MDX. Especially for the grand totals the situation is quite clear:

set [Currency2] as ‘Filter([Currency].Generations(2).members, (([Currency].CurrentMember.MEMBER_ALIAS = “US Dollar” OR [Currency].CurrentMember.MEMBER_Name = “US Dollar”)))’
set [Time Period2] as ‘Filter([Time Period].Generations(2).members, (([Time Period].CurrentMember.MEMBER_ALIAS = “2009” OR [Time Period].CurrentMember.MEMBER_Name = “2009”)))’
set [Time Period3] as ‘Filter(Generate({[Time Period2]}, Descendants([Time Period].currentmember, [Time Period].Generations(3),SELF), ALL), (([Time Period].CurrentMember.MEMBER_ALIAS = “Quarter 1” OR [Time Period].CurrentMember.MEMBER_Name = “Quarter 1”)))’
member [Currency].[CurrencyCustomGroup]as ‘Sum([Currency2])’, SOLVE_ORDER= AGGREGATION_SOLVEORDER
member [Time Period].[Time PeriodCustomGroup]as ‘Sum([Time Period3])’, SOLVE_ORDER= AGGREGATION_SOLVEORDER
{ [Account].[Sales]
} on columns
from [Sample.Sample]
where ([Currency].[CurrencyCustomGroup],[Time Period].[Time PeriodCustomGroup])

The MDX simply contains no “on rows” specification. These changes remained in all subsequent patches and are also part of Hence, this release suffers from the same problems.

On, there exists patch 8444119 which basically was constructed after 8444119 itself does not solve any of the issues mentioned above. It does however include a small, non-documented switch which resolves all these issues. NOTE: this is NOT documented and will only work on! Oracle told me they’re working on a similar fix for and on updating the patch information, but no sign of either yet.

In a environment, install patch 8444119, then create a new environment variable: “OBIS_Essbase_CustomGroup_Generation”. Set the value to “0” (without the quotes). This will correct the issues and correct the MDX fired against Essbase. Also, performance will be stabilized and go back to the level of an unpatched

Oracle unfortunately didn’t specify in detail what this OBIS_Essbase_CustomGroup_Generation “performance knob” (as they call it) does behind the scene and what the other two available settings “1” and “2” entail. Hopefully they update patch 8444119 soon since its documentation still says nothing about the existance of this environment variable.

Document 845594.1 has been created an published on Metalink. This is the only document existing which points to or mentions OBIS_Essbase_CustomGroup_Generation. So if you’re out there, going against Essbase cubes and running with 8444119 (or any MDX-influencing other patch below) or a full blown then check it out.

WARNING: While document 845594.1 outlines the issue and the solution, the version it refers to is WRONG!

Applies to:
Business Intelligence Suite Enterprise Edition – Version: [1900] – Release: 10g”

Patch 8444119 and the use of environment variable “OBIS_Essbase_CustomGroup_Generation” do only apply for patch You can not use this solution with



Hi guys,

Just quickly to let you all know. I’m not cutting you out of the loop by not writing on the details, but if I’d have to document all tests I run and all issues I find, I will still be here next month.

Bottom line:
– watch out for with 734908
– watch out for with 844119
– watch out for

With those three versions be VERY careful that you test each and every report you have running against Essbase.

I will update you as soon as I can with a finalized overview. Probably only once Oracle has come back…


I still haven’t blogged about the BI Forum in Brighton, the things I saw there, the things I wanted to test afterwards OR the things I need to blog in detail to explain my ad-hoc speech…

…all because of bloody! God that release is a pain when you’re using Essbase. I know it’s bad form to blog about what you’re about to blog about, but I will definitely fire off a huge rant with detailed descriptions soon.



Greetings, programs!

Back on April 3rd, when I initially wanted to get patch #8293083, I hit a wall.

Product Oracle BI Suite EE
Last Updated 18-MAR-2009

The patch had been made obsolete over night. So I raised an SR with Oracle. First response on the 14th:

“Bug 8293083 is a duplicate of Bug 8332167.

Bug 8332167 is fixed in
Also in patch for Linux ARU 11105211
No patch for Windows.”

Sweet. So because it was a duplicate of a Linux patch the Windows patch was made obsolete? My mind boggles trying to understand that logic, but anyways I insisted on getting the patch and voilà! The patch exists again for Windows since the 17th.

Sounds good? No, not really.

8293083 is actually QF420 and in order to install it, you need to replace your whole OracleBIserverbin folder. In itself, not an issue, but there’s also patch 8290868 (QF410), which is a patch for 7482937 which resolves a rather serious issue for MDX generation for and/or filters.

The issue being that 8290868 – like 8293083 – replaces the whole bin folder. And Oracle still can’t confirm that 8293083 is an incremental patch and includes all of 8290868.

So right now there’s a choice.
a) Use 8293083, but not be sure that 8290868 and 7482937 function correctly


b) Use 8290868and 7482937 and wait for a final statement from Oracle.

I’ve gone for b) since it’s extremely difficult to track down each and every weird behaviour in the MDX generation for all filters, EVALUATE statements, unions etc etc.

Of course I will keep you guys updated with my latest findings and Oracles statements.

End of line.


Still experiencing quite some connectivity issues with the Essbase integration. I’ve finally split the service requests, so that the Essbase team doesn’t need to go through me every time.

Patches currently to be tested (alone and in conjunction):