Resolving Other Performance Issues
Applies to
Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, Account Reconciliation, Profitability and Cost Management, Enterprise Profitability and Cost Management, Oracle Enterprise Data Management Cloud, Narrative Reporting, Sales Planning, and Strategic Workforce Planning.
Use this process to resolve performance issues, especially overall performance issues that cause all activities in the environment to be slower than expected.
Correcting Network Latency and User Load Issues
Begin by eliminating network latency as a reason for slow login performance. Slow performance of internal and external networks may lead to slow connections.
Review the Activity Report to identify areas for improvement. The information you must evaluate includes the following tables. See About the Activity Report in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.
- Top 10 Users with Poor Network Latency
This table, which identifies users who have the worst access performance, provides you a starting point to identify network latency issues.
- Number of Users
Use this table to identify whether the user load on the environment may be a contributing factor to slow performance. Generally, more concurrent user actions within an environment lead to slower performance.
- Top 30 Worst Performing User Interface Actions over 10 Seconds
Use this table to identify whether performance is impacted by slow performing user actions. Understanding the user operations that cause the environment to be busy helps you evaluate and streamline them.
- Business Rules Attached to a Form Taking Longer than 3 Seconds
Long running business rules may impact performance. Analyze the rules in this table to make them more efficient. See Resolving Form Functional and Performance Issues.
- Top 5 Worst Performing Calc Script Commands over 1 Min and Top 10 Worst Performing Business Rules. See Troubleshooting Business Rules and Member Formula Errors and Performance.
Identifying Browser Performance Issues
The Activity Report tracks the versions of the browsers that are used to access the environment and the number of users who use them. The use of Google Chrome, Microsoft Edge, or Firefox browsers are likely to provide better performance for accessing Oracle Enterprise Performance Management Cloud environments than other browsers. Also, encourage your users to use the latest published versions of these browsers. See Setting Up Browsers for EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.
Restarting the Environment (Optional) to Improve Performance
If all activities are slower than expected and you are certain that poor performance is not caused by user actions and network latency, restart the environment. This is a self-service operation that you can complete using the resetService EPM Automate command.
Before running this command, make sure that critical user initiated actions, including administrative and operational tasks being run using scripts, are not in progress. Restarting the environment terminates all ongoing processing in the environment.
Seeking Help
If the preceding information does not resolve your issues, contact Oracle Support for help.- Optional: Generate a Fiddler trace.
If overall performance is slower than expected, even after restarting the environment, generate a Fiddler trace of your session.
See Using Fiddler to Capture Diagnostic Information.
Watch this overview video for information on configuring Fiddler to capture HTTPS traffic.
If you are unable to generate a Fiddler trace file of your session, see Collecting Network Performance Trace Using a Browser for information on collecting network trace using a browser.
- Create a Provide Feedback submission. Optionally, allow Oracle to access the maintenance snapshot of the environment by consenting to application snapshot submission. See Creating a Provide Feedback Submission.
- 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:
- Details of the activities that take more time than expected.
- Fiddler trace file or network diagnostic HAR file.
- Did this issue start after the latest monthly update?
- If the activities were previously performing to expectation, the date, time, and time zone when performance was acceptable.
- A snapshot of the environment, if available, from the last time when performance was acceptable.
- Application changes that you made since the performance was acceptable.
- Whether this is a critical outage.
