|Oracle® Fusion Middleware Upgrade Guide for Oracle Business Intelligence
11g Release 1 (11.1.1)
Part Number E16452-01
This chapter describes post-upgrade tasks and considerations for an Oracle Business Intelligence upgrade.
This section describes post-upgrade tasks and considerations for Oracle Business Intelligence Enterprise Edition (Oracle BI EE).
Oracle Business Intelligence Agents (iBots in 10g) with a schedule in 10g, will not have the same schedule in 11g until the schema has been imported, or the Agent is re-scheduled by selecting a schedule and saving it in 11g.
After the Scheduler schema has been upgraded, you must use Enterprise Manager to verify that the Scheduler is configured to use the upgraded schema. Without this verification, when you edit an Agent, its schedule becomes disabled.
Manually copy the following files, paths, style sheets, and skins from the Oracle BI EE 10g installation to the Oracle BI EE 11g installation. You can also use Oracle Enterprise Manager to refer the 11g installation to the 10g files.
Note:These steps apply only if you have made modifications to these files in 10g (which are all optional).
Scheduler script path
Scheduler Default script path
OBIPS User pref currencies config file
OBIPS PDF font map file
Javahost user config file (Move the specific configuration you require, not the entire file.)
Javahost scheduler user jar file path
Language specific custom messages
Note:In order to follow the Oracle standard internationalization naming convention, some of the directories that contain language-dependent message files have been modified. following table lists the message file directory names that have been changed between Oracle BI EE 10g and 11g.
|10g Name||11g Name|
|l_zh-tw||l_zh-TW (not applicable for Windows installations)|
|l_pt-br||l_pt-BR (not applicable to Windows installations)|
After running Upgrade Assistant to upgrade an Oracle BI EE RPD, be sure that Connection Pools in the 11g environment are still pointing to the correct data source. In the case of xml data sources, be aware that the path to the source xml is held against each table definition in the physical layer, rather than at the connection pool level.
You cannot upgrade an entire Oracle BI EE cluster. If you require a clustered 11g deployment, perform a simple installation and upgrade to that single instance before scaling out.
For information about scaling out an Oracle BI EE deployment, see "Extending and Scaling Your Deployment" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
After upgrading your Oracle BI EE RPDs and catalog, consider the following:
Your 11g system will use the upgraded RPDs and catalog.
Existing catalogs of the same name are renamed.
RPDs are given a unique version number as they are added to the system so that any existing RPDs are not overwritten.
Users migrated from the RPD into WebLogic LDAP derive their application role memberships directly from the Policy Store, which can be managed within Oracle Enterprise Manager. However, users that exist in an external user population, and are authenticated using an Authentication Init Block, derive their application role memberships from the ROLES (or GROUP) session variable that is set in response to a database query within an Authorization Init Block. To ensure consistent behavior for any given user, ensure that each user exists in only one place. Therefore, any users migrated from the RPD into WebLogic LDAP should be removed from your external user population.
This section describes post-upgrade tasks and considerations for Oracle Business Intelligence Publisher (Oracle BI Publisher).
Before restarting the Managed Server - If the 10g security model is Oracle BI Server, after the upgrade to 11g, the security model is set to Oracle BI Server. Therefore, you must manually change the Oracle BI Server name (or IP Address) in
xmlp-server-config.xml file located in the
Restart the Managed Server that runs the Oracle BI Publisher instance. Once the server is running, you can log in with a 10g user ID and password.
The repository is a file system, therefore the integrated environment does not work. In this case, log in to the following URL:
If you cannot log in with a 10g user ID and password, you can log in with the superuser ID and password.