Managing Content Upgrade Issues

Oracle Hyperion Planning Modules, Account Reconciliation, Financial Consolidation and Close, and Tax Reporting business processes may perform content upgrade after the monthly update process is complete. This section explains on how to manage content upgrade issues.

Applies to

Planning Modules, Account Reconciliation, Financial Consolidation and Close, and Tax Reporting.

Content upgrade, which propagates the changes introduced during the daily maintenance of an environment, coincides with the monthly update of the environment. If a content upgrade is required, Oracle creates, schedules, and executes a content upgrade job.

If a content upgrade fails, the environment becomes inaccessible to everyone other than using REST APIs and EPM Automate.

Best Practice

Run a database refresh prior to scheduled monthly updates.

Monthly updates are scheduled, typically, on the first Friday for Test environments and on the third Friday for production environments. Ensuring that a clean database refresh is completed prior to monthly updates reduces content upgrade issues.

Resolving Database Refresh Failures

Oracle refreshes the database as a part of the content upgrade. Separate cube refresh jobs may be executed during database refresh. Application customizations, for example, incomplete changes to the outline and metadata, may cause the cube refresh job to fail. If the content upgrade fails because of an inability to complete a database refresh, review the failed Cube Refresh job to identify why the refresh failed. After fixing the underlying reason for the cube refresh failure, rerun the failed job to complete the database refresh.

To resolve database refresh failures during content upgrade:

1. Sign in to the environment as a Service Administrator.
2. From the Application card on the Home page, select Jobs.

   The Job Console is displayed.

3. In Recent Activity, click the failed Refresh Database job, for example, the RefreshDataBase_PostProcess_Rates of Financial Consolidation and Close.

   The Job Details screen displays information on the cube for which the refresh failed and indicates the reason for the failure.

4. Correct the issue that caused the cube refresh to fail. If the failure is caused by an incomplete customization, remove or complete it.
5. In the Job Console, click Actions in the row of the failed job and select Run.

Resolving Conflicts with Other Scheduled Activities

Generally, the content upgrade job is executed 12 hours after the daily maintenance is completed. The start time, however, can be customized. See Setting Content Upgrade Start Time in Oracle Enterprise Performance Management Cloud Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

Do not schedule other activities, such as activities initiated using REST APIs, EPM Automate, and Groovy scripts, during the period when content upgrade is scheduled on the first and third Fridays of the month.

How to Get Help

If the information in the preceding sections fails to resolve you issue, contact Oracle for help.

1. Create a Provide Feedback submission, which includes screenshots of the actions, and errors, if any displayed during the upgrade process.

   Optionally, authorize Oracle to access the maintenance snapshot of the environment by consenting to application snapshot submission. See Creating a Provide Feedback Submission.

2. Create a technical service request that identifies the Provide Feedback reference number. See Submitting a Technical Service Request. Attach additional screenshots, if needed, to the service request. In the service request, specify:
   • Did this issue start after the latest monthly update?
   • Whether this is a critical outage.