Note:Chapter 1, "Planning to Upgrade from Oracle BI 10g to BI 11g" provides additional considerations and possible post-upgrade tasks, in addition to the tasks provided in this chapter.
Depending upon the Oracle Business Intelligence 11g features you are using, you should review the appropriate sections of Chapter 1 before you perform the tasks in this chapter.
The following sections describe post-upgrade tasks and considerations for Oracle Business Intelligence Enterprise Edition (Oracle BI EE):
In previous releases (prior to 11g), you could create iBots (now known as agents in Oracle Business Intelligence 11g). For more information about the upgrade of 10g iBots to 11g agents, see Section 22.214.171.124, "Upgrading iBots."
If you used iBots with a schedule in 10g, then the resulting upgraded agents do not have the same schedule in 11g until the schema has been imported or until you reschedule the agent by selecting a schedule and saving it in 11g.
To fix this problem, after you upgrade the Scheduler schema, use Oracle Enterprise Manager Fusion Middleware Control to verify that the Scheduler is configured to use the upgraded schema.
For more information, see "Using Fusion Middleware Control to Configure a Database for the Oracle BI Scheduler" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
After you upgrade to Oracle Business Intelligence 11g, check whether you have made any of the customizations that are described in the following sections:
For the reasons listed in Section 126.96.36.199, "Upgrading Custom Styles and Skins," you must recreate any customized style sheets or skins that you modified in the Oracle Business Intelligence 10g environment.
If you made modifications in 10g to the following files, paths, and other customized files, and you want to use those modifications in the new 11g environment, then you must copy your customizations from the Oracle BI EE 10g installation to the Oracle BI EE 11g installation:
Scheduler script path.
Scheduler Default script path.
Configuration file for user preferred currencies in Presentation Services.
Presentation Services PDF font map file.
JavaHost user configuration file. (Move the specific configuration that you require, not the entire file.)
JavaHost scheduler user jar file path.
Language specific custom messages. For more information, see Section 188.8.131.52, "More About Localized (Language-Specific) Custom Messages."
For information about the changes in directories and locations from Oracle Business Intelligence 10g to 11g, see Section 4.3, "Changes to Oracle Business Intelligence Directory Structure".
If you have localized custom messages to support multiple languages, then note the following:
In order to follow the Oracle standard internationalization naming convention, some of the directories that contain language-dependent message files have been modified. The following table lists the message file directory names that have been changed between Oracle BI EE 10g and 11g.
Footnote 1 This name change involves only the case of the last two letters. As a result, this change does not affect Windows systems, which are not case-sensitive.
Before restarting Presentation Services (coreapplication_obips1), manually copy those localized files from the following 10g directory:
to the following 11g directory:
After running Upgrade Assistant to upgrade a repository for Oracle BI EE, ensure that Connection Pools in the 11g environment still point 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.
For additional information about data sources, see the following:
The information about Stage 2, "Reconfigure Data Source connections" in Table 1-1, "Example Upgrade Test Plan"
You cannot upgrade an entire Oracle BI EE cluster. If you require a clustered 11g deployment, then 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 Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Users migrated from the repository into the embedded WebLogic LDAP server derive their application role memberships directly from the Policy Store, which can be managed within Fusion Middleware Control.
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 that were migrated from the repository into WebLogic LDAP should be removed from the external user population.
For more information, see Section 1.6, "Understanding Oracle Business Intelligence Security Upgrade".
When upgrading a repository, users or groups with names that contain the following invalid characters are not upgraded:
To solve this issue you must create the users or groups after upgrade is complete, with new names that do not contain the invalid characters.
Important:When you create new users or groups, the new user or group names must not contain invalid characters.
You must copy all sample files manually from the 10g folder to the 11g folder when upgrading the catalog.
For information on the changes to the directory structure from Oracle Business Intelligence 10g to 11g, see Section 4.3, "Changes to Oracle Business Intelligence Directory Structure".
After upgrading the system, verify whether you must perform the optional task of scanning and updating objects in the catalog. For information on this optional task, see "Updating Catalog Objects" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
If you are upgrading from Oracle BI EE 10g, and any of your Oracle BI EE users were assigned to the "Presentation Services Administrators" group, then post-upgrade to 11g, Oracle recommends that you reassign these users an appropriate existing Application Role, or that you create a new Application Role in 11g for these users.
The following sections describe post-upgrade tasks and considerations for BI Publisher:
If the 10g security model was set to BI Server, then after the upgrade to 11g, you must verify that the BI Server name (or IP Address) in the
xmlp-server-config.xml file is correct.
For more information, see the following:
The information about Stage 5 in Table 1-1, "Example Upgrade Test Plan"
Restart the Managed Server that runs the BI Publisher instance. When the server is running, you can log in with a 10g user ID and password.
After the upgrade is completed, verify the name of the server referenced in the following configuration files:
For more information, see the following:
After the upgrade process, you must verify the location of the upgraded BI Publisher file-based repository.
In addition, if you are using BI Publisher with Oracle Business Intelligence Enterprise Edition, then you can upload repository to the Oracle BI Presentation Catalog.
For more information, see "Configuring the Catalog" in the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.
If you upgraded the repository from an E-Business Suite Data Template directory, then the upgraded data model will not have any data source references in the 11g environment. Perform the following tasks to update the data source references for Oracle Business Intelligence 11g:
Create a JDBC/JNDI connection to the EBS database.
For more information, see "Setting Up Data Sources" in the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.
Edit the Data Model to reflect this data source for the data model.
For more information, see the Oracle Fusion Middleware Data Modeling Guide for Oracle Business Intelligence Publisher.
Save the Data Model.
If the Data model refers to any SQL package function, then verify that the package name is correctly mapped in data model.
If you were using external web services or HTTP data sources in Oracle Business Intelligence 10g that required an HTTP proxy, then ensure that you enable the proxy for your new Oracle Business Intelligence 11g environment.
As described in Section 184.108.40.206, "Enhanced Catalog Object Security", the process you use to grant access to data sources in Oracle Business Intelligence 11g has changed from Oracle Business Intelligence 10g.
As a result, after you upgrade, you must ensure that--for all roles that must access a data source--the role is granted access to the data source. This requires assigning roles to data sources in the BI Publisher Administration page.
For more information, see "Granting Data Access" in the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.
When you first logged into Oracle Business Intelligence, folders were automatically created to hold content that you might eventually create. Starting from Release10, these folders are not automatically created when a new user logs in. Instead, the folders are created when they are actually needed. Examples of these folders are the
_portal folder to hold personal dashboards and the
_delivers folder to hold alerts.
And for structure changes, for a new user (first login user), objects previously stored in the
subscriptions folders are moved to the
internals folder. The
deliveries folder is merged with its parent folder
These changes have no effect on the folders for existing users. You can optionally remove empty folders within each user's home directory or relocate existing folders to their new locations during upgrade or during catalog validation. To do so, specify the following elements within the
<catalog></catalog> nodes in the
During upgrade, do the following to remove all empty folders:
During upgrade, do the following to relocate existing folders to their new locations:
During upgrade, do the following to ensure that the two preceding settings take effect:
During catalog validation, do the following to remove all empty folders: