Tag Archives: repository

OBIEE 11g Upgrade Assistant (UA) Fails When Upgrading A 10g RPD File To OBIEE 11g

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

 

  1. Retry the RPD file upgrade.

 

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: 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.