Oracle® Business Intelligence Applications Fusion Edition Upgrade Guide Version 7.9.5 Part Number E12084-01 |
|
|
View PDF |
This chapter provides an overview of the Oracle BI Applications upgrade process. It includes the following topics:
The Oracle Business Intelligence Applications Fusion Edition Upgrade Guide provides instructions for upgrading to the current release of Oracle BI Applications from the previous releases listed below:
Siebel Analytics 7.5.3
For instructions, see Section 3, "Upgrading Siebel Analytics 7.5.x".
Siebel Business Analytics 7.7, 7.7.x and 7.8.x
For instructions, see Section 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x".
Note:
Upgrade paths to the current release of Oracle BI Applications from Siebel Business Analytics Applications 6.x, 7.x, and Oracle Business Intelligence 7.9.x (7.9.0, 7.9.1, 7.9.7.9.2, 7.9.3, and 7.9.4) with Siebel Relationship Management Warehouse or Oracle Business Analytics Warehouse on NCR Teradata database are currently NOT available.Siebel Business Analytics for Life Sciences 7.8.0, 7.8.1 and 7.8.2
For instructions, see Section 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x".
Oracle Business Intelligence Applications 7.9.0, 7.9.1, 7.9.2, 7.9.3, and 7.9.4
For instructions, see one of the following, depending on your source system adapter:
You should consider the following points before you begin your upgrade:
Review the System Requirements and Supported Platforms for Oracle Business Intelligence Applications Fusion Edition to make sure your database platform versions are supported.
The upgrade process is not only a technical process. You will also need to analyze the impact of the schema changes on your current custom implementation. The extent of your customizations will have an impact on the length of time required for the upgrade.
In addition, at different stages of the upgrade you will also need to analyze your organization's business requirements. For example, at the stage in which you are upgrading the Oracle Business Intelligence repository, you will need to know which repository objects are not in use so that they can be trimmed from the repository. To determine this information, you will need to know what reports are in use.
It is highly recommended that you use side-by-side environments when performing each stage of the upgrade process. Enabling side-by-side-instances of the entire Oracle Business Intelligence Applications environment is a critical success factor for upgrade.
For the other stages of the upgrade, you can upgrade your environments in place. However, for comparison and benchmarking purposes, it is recommended that you upgrade using side-by-side environments.
You should determine what customizations were made to your existing DAC repository before you begin the upgrade process. Depending on the release from which you are upgrading, moving the customizations in your existing DAC repository into the new DAC repository may be a manual process.
For each stage of the upgrade process, you need to allocate a reasonable amount of time to validate the results of that stage and address any problems. In addition, final user acceptance testing must confirm that the entire upgrade process was successful.
When you move from a development environment to test or production environments, you must perform the following stages of the upgrade process for each environment:
Upgrade the platform
Upgrade the applications
Migrate the data
You can migrate the DAC, Informatica, and Oracle BI repositories into the production environment after you merge and test them.
For a description of the major stages of the upgrade process, see Section 2.4, "Major Stages of Oracle BI Applications Upgrade".
This section provides best practice steps you need to perform before you begin the upgrade process.
Review this guide, Oracle Business Intelligence Applications Fusion Edition Upgrade Guide, in its entirety.
Rename and copy into a different location your current repositories, Presentation Catalog (formerly known as the Web Catalog), and DAC installation folder from your existing environment. The file names and locations listed below represent the standard names and locations of files that shipped with previous versions of Siebel Business Analytics Applications and Oracle BI Applications.
When you backup the DAC repository, you export the DAC metadata, in XML format (using the DAC's Export tool), into a different database, which can be used later as a reference. For instructions, see the Oracle Business Intelligence Data Warehouse Administration Console Guide.
Type | Name | Location |
---|---|---|
DAC metadata repository | *.xml | OracleBI\DAC\export |
Oracle BI repository (formerly called Analytics repository) | OracleBIAnalyticsApps.rpd | OracleBI\Repository |
Informatica repository | Oracle_BI_DW_Base.rep | OracleBI\dwrep\Informatica\Repository |
Presentation Catalog (formerly called Web Catalog) | <file_name>.webcat | OracleBIData\web\catalog |
DAC installation folder | DAC | OracleBI\DAC |
Gather information that describes the current implementation, including the following:
Version of the transactional database to which you upgraded.
Version of the Oracle BI Infrastructure (platform) or Siebel Business Analytics platform from which you are upgrading.
To determine the platform version from which you are upgrading, launch the Administration Tool, and click Help, and then click Administration Tool in the toolbar. A message box provides the platform version.
Version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading.
To determine the version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading, launch the Data Warehouse Administration Console (DAC), and click Help, and then click About DAC.
Note:
If the DAC is not a component of your Analytics installation, you are running Siebel Analytics 7.5.x.Figure 2-1 shows the upgrade flow for the major stages of the Siebel Business Analytics and Oracle BI Applications upgrade process. Depending on the prior release from which you are upgrading, you may find minor changes in the process shown in Figure 2-1.
Table 2-1 provides the documentation you should refer to for each stage of the upgrade.
In general, you must complete stages one through five sequentially, in the following order: 1) upgrade the Siebel Business Analytics platform or Oracle BI Infrastructure to the current release of Oracle BI Infrastructure; 2) upgrade the Siebel Business Analytics Applications or Oracle BI Applications to the current release of Oracle BI Applications; 3) upgrade the metadata in the DAC and Informatica repositories; 4) upgrade the data warehouse schema; 5)(For Siebel source systems) upgrade the Siebel transactional database schema.
You can perform stages six through eight simultaneously; that is, you can migrate data into the upgraded data warehouse (stage six), upgrade the Siebel Analytics or Oracle BI repository (stage seven), and upgrade the Web (Presentation) catalog (stage eight) at the same time. However, you cannot test the results of your Web (Presentation) catalog upgrade until you have finished migrating your data.
Note:
Depending on the prior release from which you are upgrading, you may find minor changes in the process described in this section.Table 2-1 Major Stages of the Oracle BI Applications Upgrade and Related Documentation
Stage | Related Documentation |
---|---|
Note: The Oracle Business Intelligence Infrastructure is code-independent from the Oracle BI Applications. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Caution:
It is highly recommended that you consider obtaining support from Professional Services to assist with the end-to-end upgrade process.Note:
Upgrading Oracle's Siebel Customer Relationship Management applications is out of the scope of this document. Upgrading your current version of Siebel CRM applications is optional.