Upgrading the Essbase Studio Catalog and Data

To move Essbase Studio from an 11.1.1.x release to the current release, you perform an upgrade. To move from an 11.1.2.x release to the current release, you apply the maintenance release.

The upgrade or maintenance release procedure for Essbase Studio is part of the configuration process for EPM System. See the Oracle Enterprise Performance Management System Installation and Configuration Guide for more information. Complete the tasks applicable to your environment in the order noted in the guide.

After configuration, perform these tasks in Essbase Studio:

  1. Whether you perform an upgrade or apply the maintenance release, you must run the reinit command. See the Oracle Enterprise Performance Management System Installation and Configuration Guide for information on running the reinit command.

  2. If Essbase Server has moved, perform the rehosting procedure so that Essbase connections point to the new server location, as described in Updating References to a Rehosted Essbase Server.

  3. If Essbase Studio Server has moved, for deployed applications that reference the old server location, update the cube linkage, as described in Updating Cube Linkage.

  4. For text file data sources:

    • Specify either the location from an earlier release, or the replicated location for the Essbase Studio data files by modifying the default EPM_ORACLE_INSTANCE/BPMS/bpms1/datafiles location provided in the EPM System Configurator. See the Oracle Enterprise Performance Management System Installation and Configuration Guide for more information.

    • Edit the connection properties for any text file connections to point to the new location of the text files, as described in Editing Data Source Connection Properties.

    • After configuration, if you move your text files to another location, edit the server.datafile.dir property in the server.properties file and edit the connection properties for any text file connections to point to the new location of the text files. See server.datafile.dir and Editing Data Source Connection Properties respectively.

  5. If Performance Management Architect Dimension Server has moved, edit the connection properties for any Performance Management Architect Dimension Server connections that point to the old server location, as described in Editing Data Source Connection Properties.