Upgrading OBIEE 10g Repository To 11g Using The Upgrade Assistant ( UA ) Fails To Start The BI Server

Applies to:

Business Intelligence Server Enterprise Edition – Version: [1905] and later   [Release: 11g and later ]
Information in this document applies to any platform.


The 10g repository fails to upgrade when running the Upgrade Assistant Utility because the BI Server will not restart.


The OBIEE 10g Repository was configured for a cluster aware cache

10g NQSConfig.INI file (partial)

// A comma separated list of <directory maxSize> pair(s)
// e.g. DATA_STORAGE_PATHS = “d:\OracleBIData\nQSCache” 500 MB;
DATA_STORAGE_PATHS = “E:\OracleBIData\cache” 500 MB;
MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size


// Cluster-aware cache

GLOBAL_CACHE_STORAGE_PATH = “\\01AL10015011002\Global_BI_Cache” 1000 MB;

However, OBIEE 11g was not configured for a cluster aware cache prior to the upgrade assistant running

11g NQSConfig.INI file (partial)


nqserver.log message
[2011-01-06T20:20:18.000+00:00] [OracleBIServerComponent] [WARNING:1] [] [] [ecid: ] [tid: 814] Warning: Clustering and cache are enabled for this OBIS node, but cluster aware cache is disabled. This can lead to inconsistencies.



  1.   Workaround: This is a temporary workaround to allow the repository (rpd) to be upgraded.Disable the repository cache in FMw Enterprise Manager Control prior to running the upgrade assistant.
  2. Solution: The upgrade assistant does not update or configure the OBIEE 11g NQSConfig.INI file. It must be updated manually before proceeding with the upgrade.  Correct, the root cause which is to configure and enable the cluster aware cache in 11g to match the configuration in 10g prior to running the upgrade assistant.


Note:   If your issue does not match this exactly then check the following:

  • The upgrade assistant log is located at [middleware_home/[oracle_home]/upgrade/logs
  • If any components fail to start after the upgrade assistant completes, refer to the specific component logs (i.e. nqserver.log, saw0.log)
  • It may also be helpful to check the webcatupgrade.log and the upgradelog.xml to find items that failed.


Obiee 11g: After upgrade from 10g, 11g report generated UNION ALL in SQL

Applies to:

Business Intelligence Server Enterprise Edition – Version: [1905] and later   [Release: 11g and later ]
Information in this document applies to any platform.


1) Customer upgraded RPD and web catalog to
2) Its noticed that in the same reports take a lot longer to execute:
Eg: 1 min 30 sec in 11G vs. only 30 sec in 10G.
3) RPD doesn’t have any metadata inconsistencies, connection pool settings are good.
4) The memory usage spikes up when reports are run, and BI Server is taking too long compiling these reports.
5) Customer notices that the XML copied from 10g to 11g creates a more complicated logical query in 11g compared to 10g.
6) When customer copies the logical query from 10g and runs in 11g it gives the same performance as 10g.


Basically this is caused by many column with the empty string formula: ”, causing it to have 2nd UNION leaf to calculate the subtotal in


These columns with a column formula ” where used as separators in the report.

Replaced all column separators with “duplicate measure” columns with a column length of 0.
This ensures the subtotals are NOT trying to use the separators as dimensions and create extra queries with UNION ALL.

OBIEE CPU Patches — Where To Find OBIEE 10g and 11g Critical Patch Updates (CPU) Patches And/Or Security Alerts

Applies to:

Business Intelligence Server Enterprise Edition – Version: [1900] to [1308] – Release: 10g to 11g
Business Intelligence Server Enterprise Edition – Version: [1900] to [1308]   [Release: 10g to 11g]
Information in this document applies to any platform.


How can you determine if there are any Oracle Critical Patch Updates (CPU) and/or Security Alerts for Oracle Business Intelligence Enterprise Edition (OBIEE) 10g and 11g?


Critical Patch Updates and Security Alerts

Critical Patch Updates (CPU) and Security Alerts notifications are posted on the Oracle Technology Network (OTN) website.  This website maintains a listing of all Oracle products including OBIEE and typically gets updated quarterly, or as needed.  It is possible to receive notification of new CPU and security alerts by email.

Critical Patch Updates (CPU) Patches are cumulative for many Oracle products. This means that, for these products, a CPU includes new security fixes as well as all previously released CPU fixes for this particular
platform and version combination. The main benefit of cumulative CPUs is that it allows customers to
quickly and easily “catch up ” to current security release level by only applying the most recent CPU.

For example,you have the patch for Oct 2011, you do not need to first apply the patch for Jul 2011. Applying the most current CPU patch will include all current fixes.
However, each CPU advisory describes only the security fixes added since the previous Critical Patch Update advisory. Thus, prior Critical Patch Update advisories should be reviewed for information regarding earlier published security fixes.

Full details on released CPU patches and how to enable alerts can be found here.

Locating OBIEE CPU Patch
To determine if a recent CPU Patch affects OBIEE, you will need to go to CPU Patch link  http://www.oracle.com/technetwork/topics/security/alerts-086861.html

Look for section ” Critical Patch Updates” . There will be many links available for CPU patches released during different months. One needs to review these links according to what CPU patches one is looking for.

For example, you can click CPU Patch link(i.e. “Critical Patch Update – October 2011″ )
http://www.oracle.com/technetwork/topics/security/cpuoct2011-330135.html and it will bring up a new page.
In the new page, look for section ” Affected Products and Components” and under this section look for
OBIEE (i.e. “Oracle Business Intelligence Enterprise Edition, versions,,″). If you see references to OBIEE, click the Patch Availability ” Fusion Middleware” link and review the patch release notes for applicable patches.

For example, when using the steps just described, you will see section titled “3.2.2 Oracle Business Intelligence Enterprise Edition” and will find the latest CPU patches.

Here you will notice that CPU patches were released for OBIEE for Oct 2011 <<12830486, 12830471>>, July: Patch 11833743 for OBIEE 10g and so on.