Tag Archives: upgrade

Few 11g questions I found in the support log

A few useful things I found about 11G.

1.

Goal

In OBIEE 11g there is no link on the homepage for “Oracle Answers” like there was in the 10g version. Where is it or how to get it to appear?

Solution

BIEE 11g has been re-engineered in 11g, especially with the inclusion of WebLogic in the mid tier. A new look and feel is displayed from the 10g version. Now when connecting in 11g BIEE, you basically see Answers.

On the main 11g page, some of the latest Dashboards and Reports that have been created are displayed, plus there are still links to create a new report or open another dashboard.

So it is more a look and feel (cosmetic) change than anything else as the same functionality exists in both versions.

2.

Symptoms
In OBIEE Presentation Server log, you may see the following warning messages:

11g xml data incompatibility: object [some object type] at [the object path] requires upgrade. Admin needs to rerun upgrade, or remove the object, or fix the object’s xml manually. If problem persists, please contact technical support
Cause
========
Reason
========

Customers did not run catalog upgrade from the previous 11g version to the current version. Therefore, we have to upgrade it at run time in memory without saving it (if the catalog is upgraded through upgrade process, it will be upgraded and saved permanently in the catalog.) We give this warning message to warn customers that it is recommended to perform the catalog upgrade otherwise the application will need to perform the upgrade in memory.

Solution
The resolution for the issue has been documented. It is suggested to use the following:

Please refer to section: 3.8.10.2 Updating Oracle Business Intelligence Catalogs in
Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.5.0). Here is the link to the documentation.

Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.5.0)

The following bug has been logged to address the issue

Bug 12911878 – ERROR “11G XML DATA INCOMPATIBILITY” WHEN MOVING FROM 11.1.1.3 TO 11.1.1.5

Applies to:
Business Intelligence Server Enterprise Edition – Version: 10.1.3.4.1 [1900] to 11.1.1.5.0 [1308] – Release: 10g to 11g

3.

Symptoms
You are upgrading OBIEE 10g to OBIEE 11g using the Upgrade Assistant.  You have upgraded the repository successfully, but when you upgrade the web catalog, you get the following error:

[2011-03-09T13:38:25.565-05:00] [BIEE] [ERROR] [] [upgrade.BIEE] [tid: 13] [ecid: 0000IuRtnAxFw000jzwkno1DTwWL000004,0] javax.management.RuntimeMBeanException: Cannot refresh – Currently locked[[
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:897)

Cause
There is a lock on the web catalog in Enterprise Manager.

Solution
1. Search through Enterprise Manager and release any locks.
2. Stop and re-start Weblogic and the managed servers.
3. Start Upgrade Assistant and try upgrading the web catalog again.

OBIEE 10g and 11g: Comparing Repository And Catalog Security Models And Changes With Upgrade

Applies to:

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

Purpose

This document highlights the security features in Oracle Business Intelligence Enterprise Edition (OBIEE) and compares and contrasts features found in OBIEE 10g and 11g.

Questions and Answers

What documentation describes the security model for the Repository (RPD) and Catalog in OBIEE 10g?

OBIEE 10g security and repository access control are described in the Oracle Business Intelligence Server Administration Guide.

Web Catalog security and access control is described in the Oracle Business Intelligence Presentation Services Administration Guide.

What documentation describes the security model for the RPD and catalog  in OBIEE 11g?

OBIEE 11g security is described primarily in two places:

How are security settings enabled / controlled in OBIEE 10g and 11g?

In OBIEE 10g, security is controlled at the following points: permissions on the OBIEE Presentation catalog, via the repository (users and passwords) and optionally via an external LDAP, or external tables.

In OBIEE 11g, the security policy is split across the OBIEE presentation catalog, repository and default 11g identity store (embedded WLS LDAP), or external LDAP (i.e. OID or other if used).


What are the primary differences between the OBIEE 10g and 11g security models and what happens during upgrade?

Security Task/Object OBIEE 10g OBIEE 11g What happens during 10g upgrade to 11g?
Define Users and Groups in RPD file using OBIEE Admin Tool Default N/A. By default, users are defined in embedded WLS LDAP via FMW EM Console, or alternatively, in external LDAP. By default, existing users and groups migrated to embedded WLS LDAP. Existing groups are automatically mapped to an Application role.
Defining security policies Policies in the catalog and repository can be defined to reference groups within a directory Policies are defined in terms of application roles, which map to users and groups in a directory. 10g catalog groups are automatically migrated in the upgraded catalog and assigned the same privileges, access, and membership.
“Administrator” user Unique user with full administrative privileges No single user named for full administrative privileges. Administration can be performed by any user who is member of BIAdministrators group. “Administrator” user automatically added as member of “BIAdministrators” group in embedded WLS LDAP and granted Administrator role. The user specified during OBIEE 11g installation (i.e. “weblogic”, “biadmin”) is also a member of the BIAdministrators group.
Repository encryption Available on sensitive elements only – i.e. user passwords, connection pool passwords, etc. Entire RPD encrypted via a password. Prompted to set a repository password while running the upgrade assistant. Do not lose this password as there is no feature to recover a lost password.
External Authentication and OBIEE Initialization (Init) Blocks Init blocks are required for external LDAP or external table authentication. Init blocks not required for WLS embedded LDAP. Init blocks are required for external LDAP or external table authentication. Upgraded RPD will continue to point to 10g LDAP or external tables. Initblocks may need to be modified to ensure that deprecated, or reserved word, variable names are renamed.
NOTE: If you intend to use another LDAP server, such as Oracle Identity Management (OID), then you must upgrade to the embedded LDAP server first, then
migrate to the production LDAP server. Please see Upgrade Guide for further details.
Catalog Groups Defined in Presentation Server Administration link Available for backward compatibility. Use of Application Roles in FMW EM Console recommended. Existing groups will be migrated. Recommendation is to use application roles instead. Privileges on catalog objects may be granted to an application role via BI Presentation server Administration link.
SA System Subject Area Optional Available for backward compatibility and requires init blocks and external tables. Use of Embedded LDAP is recommended. Upgraded 10g RPD will point to external tables. Initblocks may need to be modified to ensure that deprecated, or reserved word, variable names are renamed.
“Everyone” Presentation Server Group Default Replaced with AuthenticatedUser role “Everyone” group migrated to AuthenticatedUser role.

Show Related Information Related

Errors and warnings after upgrade to 11G from OBIEE 10g

If you are going to upgrade to from 10g to 11g soon, you should consider the following issue :

Why Does The OBIEE 11g Consistency Check Show Errors And Warnings After An Upgrade That Did Not Occur In 10g?

The goal is to understand why an OBIEE repository (RPD) that completed an error and warning free consistency check in 10g, results in many warnings or errors when the RPD is upgraded to 11g and a consistency check is executed.

A wide range of errors and warnings have been seen.  A few examples have been copied below; however, many other errors or warnings could show after the upgrade.

For example:

Error: The content filter of a source for logical table: Fact response details references multiple dimensions. [nQSError:15001] Could not load navigation space for subject area Test_Area

Error 38126 Object Type: Logical Level
Logical Level “XyZ”.”123″ .. has name with leading or trailing spaces

Error 15004 Object Type: Business Model
Internal Error: Missing functional dependency association for colum 5: X_TABLE.ROW_ID
[nQSError: 15001] Could not load navigation space for subject area Test_Area.

Error 38079 Object Type: Physical Foreign Key
Foreign Key “ABC.123″….
FKey#2 A comparison is being carried out between non-compatible types

Warning: Fact table is not joined to logical dimension table. This will cause the problems when extracting project(s).

Warning: Missing Functional dependency association for column:

Oracle’s reply was:

In general with each release, the consistency checker is enhanced  to improve the consistency rules and to correct consistency checks that may not have been occurring in a previous release, but should have been.  Therefore, it is common and expected for each major release upgrade that you will see additional consistency check errors or warnings that you did not see in a previous release.

The majority of consistency check  errors and warnings that show in 11g but did not show in 10g are legitimate and represent a RPD design issue. The goal of these warnings and errors is to enforce RPD design rules and each one should be investigated and addressed as these could cause additional issues.

It is also advisable if you are in ‘online’ mode to check the nqserver.log from the BI Server to ensure you are correcting all the errors associated with a particular Subject Area and/or consistency check issue.

The default location will be here (assuming default instance name).

[middleware_home]/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

My advice is to make a good contingency plan, including roll-back possibility along with full regression testing (which can be tricky in OBIEE).

 

FOLDERS AND REQUESTS ARE NOT DISPLAYED AFTER UPGRADING TO 11.1.1.3.0.

You have an OBIEE 10.1.3.4.1. instance and a lot of folders and requests for the Administrator user.
You upgrade to 11.1.1.3.0, using the ua.bat tool. It finishes as complete and there are no errors in the the Upgrade Assistant (ua) log files:

 $OBIEE_HOME/upgrade/logs

For example
 C:\OBIEE_11g\Oracle_BI1\upgrade\logs

In OBIEE 11.1.1.3.0, when you log in as Administrator and go to the Catalog option, you are not able to see any folder or request.

Cause

The upgrade process, ua.bat, is not transferring the folders and request for the Administrator user.

This is due to the bug below


What were you trying to do?
---------------------------
Upgrade both repository and web catalog from 10.1.3.4.1 to 11.1.1.3.0.

What should have happened?
--------------------------
You should be able to see all folders and request you had in 10.1.3.4.1 after 
upgrading to 11.1.1.3.0.

What actually did happen?
-------------------------
For the Administrator account, after running the ua.bat for upgrading and 
finishing without error, when you log in with this account, it does not 
display  any folder or document for the Administrator user in 11.1.1.3.0, 
there are a lot of folders and request in 10.1.3.4.1.

What are the symptoms of the problem?
-------------------------------------
You have a web catalog in 10.1.3.4.1. When you log in as Administrator in 
this version you see a lot of folders and request for that user.

  You upgrade to 11.1.1.3.0 using the ua.bat utility. It finishes fine, 
completed without error. In the upgrade log file you can find some warnings 
that I am not sure they are related to this issue. You log in as 
Administrator in 11.1.3.0 and you cannot see any folder or request.

What changes have been made to the technical environment recently?
------------------------------------------------------------------
None.
-------------

Suggested workaround is the following:
In 10.1.3.4.1.
 ===============
 
 1) In Administration Tool, create a new user, 'new_account', under Manage-Security (if you are using other Security option, add the new user there).
 
 2) Using Catalog Manager, copy the content of the Administrator user into the new one.
 For instance:
 
 /-users-administrator
 into
 
  /-users-new_account
 
 3) Upgrade the Web Catalog using the ua.bat:
$ORACLE_HOME/bin/ua.bat
 
 
In 11.1.1.3.0.
 ==============
 
 4) Using Catalog Manager, copy the content of the 'new_account' user into the Administrator one.
 For instance:
 
 /-users-new_account
 
 into
 
 /-users-administrator
 
 5) Connect to OBIEE as Administrator and check you are able to see all folders and requests.

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.