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

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

2. Ensure that there is at least three times as much free space as the total size of the Essbase cube in your temp directory when upgrading from Release 11.1.2.x to Release 11.2.15. For example, if the data size of the Essbase cube is, for example, 10 GB, then there must be 3 * 10 (30 GB) of space available in your temp directory.

   This space will be cleaned up after the upgrade process and is only used for temporary purposes.

3. For EPM products using Java API (JAPI) - Ensure that you take a backup of the file EPM_ORACLE_HOME\common\EssbaseJavaAPI\11.1.2.0\bin\essbase.properties and copy it to EPM_ORACLE_HOME\common\EssbaseJavaAPI-21C\11.1.2.0\bin\essbase.properties after the upgrade to Release EPM 11.2.15.

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