Hyperion Migration Considerations to 11.2.15 release

 Migration Considerations

Currently, Oracle Hyperion Enterprise Performance Management System does not support application and artifact migration from Release 11.2.12, 11.2.13, and 11.2.14. You must use Apply Update in these environments to make their snapshots compatible with Release 11.2.15.  

You cannot directly migrate artifacts and snapshots taken from existing Release 11.2.12, 11.2.13, and 11.2.14 deployments of Oracle Hyperion Enterprise Performance Management System to a newly deployed Release 11.2.15 deployment.

Oracle plans to offer support for direct application and artifact migration for new deployments from Release 11.2.12, 11.2.13, and 11.2.14 to Release 11.2.15 by the end of CY 2023.  

At that time, customers can migrate applications to new deployments on Linux release 8 and Windows Server 2022.

Hyperion 11.2.15 is out ! Migration path from 11.2.x

 Oracle released 11.2.15 today Nov 1.  Here is the migration path from the readme doc:

Oracle EPM Cloud licensing information Oct 2023

 https://www.oracle.com/mx/a/ocom/docs/corporate/pricing/oracle-fusion-cloud-global-price-list.pdf

Oracle Hyperion HFM 11.2.x Importing applications

Importing Applications

You can import an application across databases or across EPM systems using homogeneous databases, however both EPM systems must use either Oracle Database or SQL Server. Source applications can originate from prior releases as far back as 11.1.2.4, however to upgrade older applications, you must run the Financial Management Upgrade Application task in EPM System Configurator from one Financial Management server. To import an application, you must have the Application Administrator role and be provisioned in Shared Services for the Financial Management Application Creator role.

You can import an application to the same environment and rename it, or you can register the new application in a different project and cluster.

You can import data for all years and scenarios, or select specific years and scenarios.

By default, the process duplicates the application profile information, metadata, and security information. You can also select to import the task and data audit information from the source application to the destination application.

Prerequisites for Importing Applications

These steps are required before you import applications:

• You must create a data communication link between the source and destination databases.

• If you are using Oracle databases, you must create a Database Link.

• If you are using SQL Server databases, you must create a Linked Server.

• You must make sure that the HFM database has the rights to create a Database Link or Linked Server.

• You must grant a one-time explicit DB privilege for database users configured in the Database Link or Linked Server rather than provisioning the users through roles.

To import an application:

1. Log on to the destination EPM system.
2. Select Navigate, then Administer, and then Consolidation Administration.
3. Select Administration, and then Import Applications.
4. Select Database Link if you are importing between Oracle databases, or select Linked Server if you are importing between SQL Server databases.

   When you select Database Link or Linked Server, the source applications are listed.

5. From the application list, select the source application.
6. Specify the Destination Application Name and Destination Application Description.

   The source application is imported with this name and description.

7. For Cluster, select the cluster the application should be registered on.
8. For User Management Project, select the project the application should be registered on.
9. Optional: Select the Import Audit Tables option to import the Data Audit and Task Audit tables from the source to the destination application.
10. Optional: Select the Import Data Tables option to import the data tables from the source to the destination application.

    If you select Import Data Tables, you may also specify the Scenario and Year filters.

11. Optional: Select the Purge Source Data option to purge the source data tables after copying to the target application.
12. Click Import.

When you start the import process, the system displays a warning that the operation is data intensive and asks if you want to continue.

It then displays the Admin Tasks page, where you can monitor the progress of the Import Application task.

After the system successfully imports the source application, it registers the newly created application to the cluster and project that you specified, and you can open the new application.

Oracle Hyperion Supported Paths to Release 11.2 release

You can move to Oracle Enterprise Performance Management System Release 11.2.x from Release 11.1.2.4.xxx, including Release 11.1.2.4.700 and Release 11.1.2.4.900.

Upgrade From	Upgrade To
Release 11.1.2.4.xxx, including Release 11.1.2.4.700 and Release 11.1.2.4.900	Release 11.2.x
For Oracle Hyperion Financial Close Management, you can upgrade only from Release 11.1.2.4_253+.	Release 11.2.x
For Oracle Hyperion Financial Data Quality Management, Enterprise Edition, you can upgrade only from Release 11.1.2.4.220. Note that PSU .220 is included in Release 11.1.2.4.700 and Release 11.1.2.4.900.	Release 11.2.x

Hyperion Essbase 21c is planned for 11.2.15

 Please be advised that:

• Current plans call for Oracle Hyperion Enterprise Performance Management (EPM) System release 11.2.14 to be the last release to embed and certify Essbase 11.1.2.4.
• Current plans call for Essbase 21c to be embedded with EPM System release 11.2.15. It will be the only Essbase release certified with the EPM System.

I am also involved in recent projects that migrate EPM 11.1.2.4 to EPM 11.2 and at that time latest version was 11.2.12 and since 11.2 requires out-of-place migration and I wanted to migrate to the latest possible version on the new servers, I had to check what was the supported path to get there. Every patch mentions this in the release notes.

For 11.2.12 I had to install 11.2.8, install all the patches and then apply patch 11.2.12 (11.2.13 is the latest version now). You can always update 11.2.8-14 to 11.2.15 in the future. In practice what this hints is that moving forward, to install 11.2.16 or later, when they become available, you will need at least version 11.2.15.

When the installer of the full installation runs, you will just need to choose apply update instead of new installation. In my case it's inhibited since I didn't have any prior version installed.

Hyperion on-premise support extended till 2034 !!

 May 12, 2023 update FYI

https://www.oracle.com/us/assets/lifetime-support-applications-069216.pdf