The following table identifies the high-level tasks that you perform to upgrade EPM System products. You must perform tasks in this order and you must complete the entire checklist.
The process described in this chapter assumes that you upgrade one product at a time and indicates where a sequence is required.
Note: | If you are upgrading from an environment with multiple releases, see Upgrading from an Environment with Multiple Releases. |
Table 29. Upgrading Checklist
| Task | Reference | Check When Completed |
|---|---|---|
Go through the tasks in the following section once for all EPM System products at one time. | ||
| Preparing to Upgrade | ||
1. Review release compatibility, system requirements, and other prerequisites for this release. If your database environment needs to be upgraded, perform the database upgrade before you proceed. See the database documentation for details. |
| |
2. Prepare the new environment for the new Release 11.1.2.1 installation. Note: Create a new database to store Shared Services data. (However, if you are upgrading from Release 11.1.1.3 and you used one database repository for all products, you do not need to create a new database for Shared Services. The Shared Services tables will be dropped during configuration.) Tip: In preparation for a new installation, you can use a worksheet to note the machines on which earlier release products are installed, and the machines on which you plan to install the new release products. You can refer to this information in subsequent procedures. |
| |
3. Perform upgrade-specific prerequisite tasks. | Upgrade Installation Prerequisites | |
4. Download and prepare the installation files. | Downloading and Preparing Files for Installation | |
5. Prepare data for upgrading. | Preparing Data for Upgrading | |
6. Stop EPM System services if you are upgrading on the same machine. | Stopping EPM System Services | |
7. Uninstall the earlier release of EPM System products. Oracle recommends that you uninstall if you are upgrading to the same machine. | Uninstalling the Earlier Release of EPM System Products | |
Iterate through the following checklist items for each product, one product at a time, in the following order:
Tip: Oracle recommends that after completing each step, you return to this checklist so that you perform the upgrade steps in the correct order. | ||
| Installing and Configuring | ||
8. Install EPM System products (choosing the New installation option) in a new installation location. |
| |
9. Configure Release 11.1.2.1 products. Note that you must configure Foundation Services first. Foundation Services must be installed and configured for other products to configure successfully. Caution! If you have already configured the Web server and you configure any additional products, you must run EPM System Configurator again and select the Foundation Services Configure Web Server task. Then, restart the Web server and EPM Workspace. |
| |
10. Start EPM System services. | Starting and Stopping EPM System Products | |
| Validating the Installation | ||
11 Using EPM System Diagnostics, validate the installation. | Validating the Installation and Verifying Deployment | |
| Performing Post-Configuration Tasks | ||
12. Complete product-specific postconfiguration tasks. | Performing Postconfiguration Tasks | |
13. If products have been rehosted on a new server, make updates, such as updating data source connections. | Updating References to a Rehosted Environment | |
14. Upgrade applications for the following products from the earlier release to the current release:
Note that Planning applications are upgraded using the Upgrade Wizard, which also includes steps for rehosting. Other applications are upgraded during configuration. | Upgrading Applications from the Earlier Release to the Current Release | |
15. Perform product-specific upgrade tasks for products that you upgraded. | Performing Additional Product-Specific Upgrade Tasks | |
16. If your previous deployment did not use Shared Services security, transfer users and groups to Shared Services. This step is required for earlier releases of the following products if you have not yet implemented Shared Services security.
If you used Shared Services security in the earlier release, you can skip this procedure. | Transferring Users and Groups | |