OBIEE Blog

Applies to:

Business Intelligence Interactive Dashboard – Version: 11.1.1.5.0 [1308] and later   [Release: 11g and later ]
Information in this document applies to any platform.

Symptoms

Recently upgraded Oracle Business Intelligence Enterprise Edition (OBIEE) from 10g to 11g (OBIEE 11.1.1.5).
All upgrade steps were completed as described in the Upgrade Guide for Oracle Business Intelligence
11g; including upgrading the web catalog and repository (RPD).
The repository was checked and there were no errors.
When logging in to OBIEE Presentation server as a user with OBIEE Administrator role, the 11g dashboard is empty and expected content is not present.

Changes

Upgraded from 10g to 11g.

Cause

Insufficient permissions on ‘shared folders.’
The permissions on catalog folder ‘shared folders’ were available only for ‘Authenticated user’ and ‘Presentation Server Administrators’.

Solution

Login to OBIEE Presentation server as WLS or biadmin user and select Administration link ->
add relevant application role e.g. ‘BI Administrator role’ and grant at least read and traverse permissions to the ‘shared folders.’
Also ensure that you tick the check boxes to apply permissions to all items within the folder and sub folders.

Applies to:

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

Symptoms

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

Cause

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

10g NQSConfig.INI file (partial)
[ CACHE ]

ENABLE = YES;
// 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
MAX_CACHE_ENTRY_SIZE = 1 MB;
MAX_CACHE_ENTRIES = 1000;
POPULATE_AGGREGATE_ROLLUP_HITS = NO;
USE_ADVANCED_HIT_DETECTION = NO;

MAX_SUBEXPR_SEARCH_DEPTH = 7;

// Cluster-aware cache

GLOBAL_CACHE_STORAGE_PATH = “\\01AL10015011002\Global_BI_Cache” 1000 MB;
MAX_GLOBAL_CACHE_ENTRIES = 1000;
CACHE_POLL_SECONDS = 30;
CLUSTER_AWARE_CACHE_LOGGING = YES;

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

11g NQSConfig.INI file (partial)

GLOBAL_CACHE_STORAGE_PATH = “” 0 MB;
REPOSITORY_PUBLISHING_DIRECTORY = “\\nullserver”;

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.

Solution

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.

Applies to:

Business Intelligence Server Enterprise Edition – Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308] – Release: 11g to 11g
Business Intelligence Suite Enterprise Edition – Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308]   [Release: 11g to 11g]
Information in this document applies to any platform.

Symptoms

You have installed OBIEE 11g and upgraded the repository from 10g to 11g.  You log into OBIEE as Administrator and click on the Administration link and then the Manage BI Publisher link.  You get the error:
Server not initialized. Please make sure the repository is ready

Cause

You are missing the privileges Access to SOAP and Impersonate as System User from the  BIAdministrator and BISystem roles.

The BISystemUser communicates with the different components of the OBIEE and when BI Publisher is accessed from answers, it communicates with BI Publisher via SOAP.  The Access to SOAP privilege should be granted to the BISystem role.  Also the Impersonate as System User privilege should be granted to the BIAdministrator and BISystem roles.

Solution

1. Log in to OBIEE 11g with Administrator credentials (superuser in 10g rpd which was upgraded to 11g).

Note: The reason you need to log into OBIEE 11g with Administrator credentials, is because the error is seen only with an upgraded 10g repository.  Also the superuser in OBIEE 11g (the user created at the time of 11g install, the default name of which is weblogic) will not have access to the Administration link with the upgraded repository. See note 1262219.1 for how to add the missing Administration link in OBIEE 11g with the upgraded repository.

2. Click on Administration > Manage Privileges.

3. Assign BISystem or BIConsumer roles the Access to SOAP privilege.

4. Assign Impersonate as System User to BIAdministrator or BISystem role.

Applies to:

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

Symptoms
On OBIEE 11.1.1.3, When attempting to upgrade a 10g RPD file via the Upgrade assistant
(ua.sh ) , the upgrade fails and the following error can be seen in the log file:

[BIEE] [ERROR] [] [upgrade.BIEE] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] oracle.as.management.opmn.optic.OpticException: Error in starting opmn server[[
Operation aborted because of a system call failure or internal error
at oracle.as.management.opmn.optic.OpmnAdmin.executeCommand(OpmnAdmin.java:310)
at oracle.as.management.opmn.optic.OpmnAdmin.startOpmnServer(OpmnAdmin.java:87)
at oracle.ias.upgrade.config.oraclebi.OPMNUtil.startOpmn(OPMNUtil.java:46)

[Framework] [ERROR] [UPGAST-00138] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] upgrade exception occurred
[Framework] [ERROR] [] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] Cause: An unexpected upgrade exception has occurred. Action: See the secondary error message for additional details.
[Framework] [ERROR] [] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] Error in starting opmn server[[
Operation aborted because of a system call failure or internal error
]]

Cause

The system component services for BI components are not started.

The upgrade assistant is not able to communicate to OPMN.

Solution

1. Start OPMN services via the command:

   [middleware_home]/instances/instance1/bin> opmnctl startall

2. Confirm the status of opmn and the system components under the instance home with:

   [middleware_home]/instances/instance1/bin> opmnctl status

Note: You may  also start the System Components and check the status via Fusion Middleware Control

3. Retry the RPD file upgrade.

Applies to Business Intelligence Suite Enterprise Edition – Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308]   [Release: 11g to 11g]

Symptoms

After upgrading to Oracle Business Intelligence Enterprise Edition (OBIEE) 10g to OBIEE 11g, when viewing a dashboard or creating a new analysis in Answers, the following error occurs:

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 12504, message: ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
Or you might get the error:

[2010-11-16T06:02:38.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 004_ILDmfHpFw000jzwkno0002Xk0000qx] [tid: 4f353960] [nQSError: 17014] Could not connect to Oracle database. [[
[nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified
at OCI call OCIServerAttach.
[nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement.
[nQSError: 43113] Message returned from OBIS.
It looks like all the database connections have been broken.

Another symptom that may occur is that the BI Server does not start up and you get the following error in the nqserver.log:

[ecid: 00hxwa3cUNZ4aq_S9Q2FSx0001SO000000] [tid: 814] [36007] Loading repository E:\obiee11g\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\11rpd.rpd.
[2011-01-06T20:20:52.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00hxwa3cUNZ4aq_S9Q2FSx0001SO000000] [tid: 19b4] [nQSError: 17014] Could not connect to Oracle database. [[[nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specifiedat OCI call OCILogon.

Changes

Upgraded from OBIEE 10g to OBIEE 11g.

Cause

In OBIEE versions prior to 11g, it uses the database client home tnsnames.ora file to resolve the tnsname. But OBIEE 11g uses the tnsnames.ora file installed within its installation home. The path is
[middleware home]/[oracle home]/Oracle_BI1/network/admin
By default, there are no database tns alias descriptors configured.

Solution

There are three ways to solve this problem:

1. If you just need one TNS alias, then copy the database connection descriptor from database tnsnames.ora file to the tnsnames.ora file under the BIEE directory:

[middleware home]/[oracle home]/Oracle_BI1/network/admin

2. You  may also copy the entire tnsnames.ora file

3. Another alternative is to set the TNS_ADMIN environment varaible which would point to the directory where a tnsnames.ora file is located. This would need to be set as a System Environment variable in Windows or in the command shell if starting from a command-line. For Unix/Linux, it would need to configured in the user profile that owns the software or set explicitly in the shell if starting from the command-line.