Resolving Issues with Smart Push

If you encounter performance issues or errors while performing smart push, try to optimize them. Smart push errors may include a resource not being available to complete the job and an inability to allocate needed resources for smart push.

For best practices to replace zero blocks and remove #missing blocks in BSO cubes to reduce database size, see Optimize BSO Cubes.

Applies to

Oracle Hyperion Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Enterprise Profitability and Cost Management, Tax Reporting, Sales Planning, and Strategic Workforce Planning.

Handling Smart Push Errors

Typical Smart push errors related to lack of resources include the following:

• Smart Push Error – There are not enough resources available for cube xxx to complete this job. The job will complete when the resources are available.
• Push Data failed – Unable to allocate resources for cube xxx for 45 seconds. Reduce the number of simultaneous operations on this cube or try again later.

To fix resource allocation-related errors:

1. Review the Activity Report to identify resource intensive activities and slow performing Oracle Essbase operations. Typically, the impact such operations have on system resources could deprive smart push of needed resources. Be sure to review the following tables in the Activity Report. See About the Activity Report in Oracle Enterprise Performance Management Cloud Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.
   • Top 10 Worst Performing Calc Scripts

     Optimizing these calculation scripts may free up system resources that can be allocated to smart push.

   • Top 10 Worst performing Business Rules over 30 seconds

     Execution of business rules require system resources. Redesigning these business rules may free up resources that can be allocated to smart push. See Troubleshooting Business Rules and Member Formula Errors and Performance.

   • Top 10 Worst Performing Essbase Queries over 15 Seconds

     This table identifies up to 10 long running Essbase queries that take more than 15 seconds to run. Evaluate these queries to make them more efficient.

   • Business Rules Attached to a Form Taking Longer than 3 Seconds

     Evaluate these rules to see if they can be streamlined to take less execution time.

2. Review recent application changes, especially changes to data maps definition.

   Review data map and other application changes and evaluate how they impact the use of system resources. Redo data map definitions that contribute significantly to resource use.

   Review the Application Design Changes table in the Activity report to identify recent changes to the application.

3. Avoid smart pushes to the ASO cube when exclusive operations such as merge slices and clear data are in progress.

   ASO cube exclusive operation behavior affects smart push. Because other operations have to wait for the completion of exclusive operations, smart push waits if exclusive operations on the Essbase cube are in progress. Smart push, which is an end-user operation, has a limited wait period. If the exclusive operation finishes within the wait period, smart push is initiated; otherwise smart push fails.

Optimizing Smart Push

To optimize smart push:

• Drop aggregate views
• Enable query tracking
• Run a few smart pushes to ensure that everything works as designed
• Create aggregate views based on query tracking
• Set up a nightly job to drop and re-create aggregate views

If these optimization steps do not improve performance, seek help from Oracle.

Resolving Smart Push Performance Issues

If you encounter performance issues while performing smart push, evaluate whether the data calculations are causing the performance issues.

Dynamic calculation members may impact the performance of smart push operations. To ensure optimal performance of smart push, exclude dynamic calc members from the smart push definition. If you must transfer dynamic calc members, move only the required members and exclude the members that are not required.

Getting Help

1. Create a Provide Feedback submission that captures your actions.

   Optionally, allow 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. The service request must contain the following additional information:
   • Detailed steps to reproduce the issue.
   • Did this issue start after the latest monthly update?
   • If the process was performing better previously, the date, time, and time zone when smart push was performing as expected.
   • Snapshot of the environment, if available, from the last time when smart push was performing as expected.
   • Application changes that you made since the last time smart push was performing as expected.
   • Whether this is a critical outage.