Replicating Data

When you upgrade to EPM System Release 11.1.2.1, you use the data from the earlier release in one of two ways:

You can replicate the data to a new machine, making it accessible from the new installation environment. For example, use this option if you want to maintain the earlier release environment.
During product configuration with EPM System Configurator, you specify the new, replicated location for data when you configure the product data directory locations.
Note:
Oracle recommends that you replicate data.
You can leave the data on the existing machine, making the drive shareable. If you choose to leave data on the existing machine, you can skip the procedures in this section. During product configuration with EPM System Configurator, you specify the existing data location. You can choose this option only if you no longer need to maintain the earlier release environment.
Note:
For Essbase, you can choose this option only if the data is on a supported type of shared drive, such as a SAN drive.

To replicate product data files:

On the shared drive or machine hosting the data for the new release, create directories to store the replicated product data.

Tip:

This location is the data storage location for Release 11.1.2.1, so store data in a meaningful, permanent location. You might choose to specify a location for each product, for example: EPMData/productName. Do not store data in the directory that is to be used as EPM_ORACLE_INSTANCE, which in a default installation is Oracle/Middleware/user_projects/epmsystem1. (EPM_ORACLE_INSTANCE must be an empty directory.)

Replicate data as noted in the following table for each EPM System component.
During configuration during an upgrade, EPM System Configurator prompts you for the data location.

Table 32. Data to Replicate for Upgrading

Product	Data to Replicate
Essbase	Essbase provides a tool to help with replicating data. See Preparing Essbase Data for Upgrading. In addition, note the following: If you are installing this release of Essbase on a new machine, gather additional data from the machine hosting the earlier release installation: Make a list of the ODBC DSNs defined on the machine so that you can redefine them on the new machine. Perform this step for Essbase and Integration Services. Make a list of JAVA options (ESS_JVM_OPTIONn) that are set on the machine so that you can redefine them on the new machine (either as environment variables (Windows) or through hyperionenv.doc (UNIX)).
Administration Services/Business Rules	HBRClient.properties; the default location is HYPERION_HOME/products/Essbase/eas. For Release 9.3.3, the location is HYPERION_HOME/AnalyticAdministrationServices. You must copy the file to EPM_ORACLE_HOME/products/essbase/eas on the target machine. Tip: If you have already installed the new release, copy the HBRClient.properties from the source machine over the existing file on the target machine.
Essbase Studio	For upgrades from Release 11.1.1.3, text files that are used as data sources. In Release 11.1.1.3, these files were stored by default in HYPERION_HOME/products/Essbase/EssbaseStudio/Server/datafiles. Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator, you enter this location on the Configure Essbase Studio Data File Location configuration page.
Reporting and Analysis	Data files. By default these files were stored in the following location: 9.2.1 and 9.3.3: BIPLUS_HOME/data/RM1_servername 11.1.1.3: HYPERION_HOME/products/Foundation/workspace/data/RM1_servername Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator, you enter this location on the Reporting and Analysis Framework Services configuration page, for Repository Directory.
Performance Scorecard	Attachment and note files. By default these files were stored in the /attachments and /notes directories in following location: Release 9.2.1: HYPERION_HOME/hps/9.2/AppServer/InstalledApps/WEB_SERVERVERSION/webappsconf Release 9.3.3 and 11.1.1.3: HYPERION_HOME/deployments/WEB_SERVER/webappsconf Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator, you enter this location on the Performance Scorecard configuration page, for Specify directory to store Performance Scorecard files.
Strategic Finance	Data files. By default these files were stored in the following location: For Release 9.2.1 and Release 9.3.3: /HSFData For Release 11.1.1.3: HYPERION_HOME/products/hsf/HSFData Note: Make note of the location to which you replicate the data files. During configuration with EPM System Configurator, you enter this location on the Strategic Finance configuration page.
FDM	Data files. For each application, copy the entire data directory structure. To see the location of the source application data: From Workbench client, select Add Application, select the application, click Modify and then note the data location. Repeat for each application. The FDM data directory on the new machine should be a UNC share and should be available to the DCOM user used to configure FDM. This directory structure must be replicated to the new environment if it is not accessible from the new environment. Note: Make note of the location to which you replicate the FDM data directory. During FDM configuration, for each application, you specify the new data directory.