Before applying the update to move to Oracle Enterprise Performance Management System Release 11.2.15 and before configuring Essbase Server:

1. Disk Space Requirements

   Note:

   • Ensure your Middleware home (MIDDLEWARE_HOME) directory has free space equal to twice the size of the Essbase cube.
   • Ensure your TEMP directory has free space equal to three times the size of the Essbase cube. On Windows, TEMP directory is located in your <Local Drive:>, for example C:\.
     • For example, if your Essbase cube size is 10 GB, you’ll need 20 GB in your Middleware home (MIDDLEWARE_HOME) directory and 30 GB of free space in your TEMP directory. This space will be cleaned up after the upgrade process and is only used for temporary purposes.
     • The table below provides an example based on a 10 GB Essbase cube size.

   Table 11-2 Example assuming a 10 GB Essbase cube size

   Essbase Cube Size	Middleware Home Requirement	Temp Directory Requirement
   10 GB	2 x 10 GB (size of Essbase cub) = 20 GB	3 x 10 GB(size of Essbase cube) = 30 GB

2. If the files (for example, "Calc Scripts", "Rule Files") in your 11.2.x Essbase instance have names that contain non-English characters , they might not be converted to Essbase 21c as part of the upgrade to EPM 11.2.15. Ensure that you manually migrate those files.

3. For EPM products using Java API (JAPI), back up and restore the Essbase properties file:

   Table 11-3 Back up and Restore Essbase properties file

   Before Upgrade	After Upgrade
   Back up EPM_ORACLE_HOME\common\EssbaseJavaAPI\11.1.2.0\bin\essbase.properties	Copy it to: EPM_ORACLE_HOME\common\EssbaseJavaAPI-21C\11.1.2.0\bin\essbase.properties

4. 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.

5. 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.

6. WebLogic Administrator Password

   If the WebLogic Administrator Server password in EPM configuration does not include at least one number and contains special characters other than $ (dollar) # (pound) or _ (underscore), it must be updated to meet the following requirements before configuring the Essbase Server:

   • The password must begin with a letter.
   • It should be between 8 and 30 characters in length.
   • It must include at least one number.
   • Optionally, it can include any number of the special characters $ (dollar) # (pound) or _ (underscore).

     For more information on updating WebLogic Administrator Password, see Changing WebLogic Administrator Password.