Note the following installation prerequisites.

• Ensure that you have the anti-virus software disabled for the entire duration of the installation process. Anti-virus software can be re-enabled once the installation is complete.

• Review the system requirements in the (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

• Linux Operating System Requirements:

  • Oracle Linux 8 (UL0+) and Red Hat Linux 8 (UL0+)
  • Oracle Linux 7 (UL0+) and Red Hat Linux 7 (UL0+)
• Before applying the update to move to EPM 11.2.15 and before configuring Essbase Server, see Applying an Update Prerequisite Tasks (Essbase 21c Only).

• You must install and configure all EPM WebLogic instances on the same operating system.

• EPM System Installer installs Oracle WebLogic Server for you. If you have an existing WebLogic Server installation and want to use it instead of the WebLogic Server installed by EPM System Installer, it must be the version supported by Oracle Enterprise Performance Management System.

  Note:

  Ensure that you note the Middleware home location for the WebLogic Server installation. During installation, you must install EPM System products to this same Middleware home. If EPM System Installer detects an existing WebLogic Server installation in the installation location, it does not install WebLogic Server.

• Ensure that there is 4 GB of temp space available. You can specify an alternate /tmp directory if needed.

• If you are configuring a Essbase Failover environment in Windows, ensure that the common shared Essbase application directory is mounted on the same drive (for example, Z:) on the nodes and use it as the application directory in the EPM configuration tool.

  Note:

  UNC Shared directory path is not supported as Essbase application directory in Windows.

• When updating an existing Essbase environment (Version 11.1.2.4) where EAS Lite is configured independently, the machine where EAS Lite was previously available will no longer be availalable on the same machine after updating to Release 11.2.15. It will be removed from the machine, along with the registry entries related to it. As an alternative, it will be set up on the same system as Essbase Server.

• Install the 64 bit version of Visual C++ Redistributable Packages for Visual Studio 2019 on the Windows machine where Oracle Hyperion Financial Reporting is installed. (Latest Microsoft Visual C++ Redistributable Version).

  On Linux:

  Make sure libstdc++.so.6 is installed on the machine whereFinancial Reporting is installed.

• On Linux systems, ensure that ulimit is 8096 for the ODI patch to apply. You can query for the current ulimit setting with the following command: ulimit -n
• Ensure that the noexec option is not enabled on the /tmp directory and remove it if it is enabled. Additionally, confirm that the /tmp directory has sufficient space and the necessary permissions.

• See Preparing Your Environment for installation prerequisites.

• For Oracle Hyperion Tax Provision, you must also install all Oracle Hyperion Financial Management components, although they do not need to be installed on the same machine as Tax Provision.

• If you are installing on the same machine on which Oracle Business Intelligence Enterprise Edition or Oracle Business Intelligence Publisher are installed, install into two different Middleware homes. Future patch sets for EPM System and Oracle BI EE will be released at different times, which would create constraints for the upgrades of a merged Fusion Middleware Home.

  For information about Fusion Middleware, see https://www.oracle.com/middleware/technologies/bi-foundation/hyperion-supported-platforms.html.

• If you are installing and configuring Oracle Hyperion Financial Data Quality Management, Enterprise Edition, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator is in same database as FDMEE and the Oracle Data Integrator agent application is deployed in same JVM as FDMEE.

• FDMEE is required for Account Reconciliation Manager in Oracle Hyperion Financial Close Management. Configure Financial Close Management and Account Reconciliation Manager before configuring FDMEE.

• If you have an existing Oracle SOA Suite installation you plan to use with Financial Close Management, note the Middleware home location for the SOA Suite installation.

  During installation, you must install EPM System products to this same Middleware home.