Diagnosing Form Retrieval Performance
Service Administrators can use the Retrieval Performance Diagnostic Agent to investigate forms that open slowly. You can describe the issue in natural language and provide the form name. The assistant validates the form, runs data retrieval diagnostics in the background, and analyzes the diagnostic logs to identify supported metadata and form-design issues.
You can also diagnose Ad Hoc Grids created in Oracle Smart View for Office and saved in the application. The assistant considers a saved Ad Hoc Grid as a form for this analysis.
The assistant provides findings and recommended actions. It doesn’t change form layouts, form configuration, or metadata. Review the recommendations and make the changes appropriate for your application.
Before you begin
You must be a Service Administrator to run retrieval diagnostics. Use a valid form name or the name of an Ad Hoc Grid saved in the application.
Data Retrieval Diagnosis must be enabled. Before enabling the setting, ensure that no active jobs are running. Enabling it may require an Oracle Essbase restart. You can enable the setting when prompted by the agent. To enable it manually, click Application, then click Consolidation Settings. From Setting Type, select Diagnostics, then enable Data Retrieval Diagnosis.
Note:
- The setting can slow normal data retrieval, so disable it after the diagnosis is complete.
- When you enable diagnostic settings, a recommendation for Data Retrieval Diagnosis Configuration is added on the Recommendations page with Open status. After you disable the diagnostic setting, the recommendation automatically changes to Resolved status.
Running retrieval diagnostics
- On the Home page, click Consolidation Assistant.
- Enter a request that includes the form name. For example, enter "My Revenue_Input form is loading slow" or "Diagnose slow performance of Expense Detail".
- If the assistant asks for the form name, enter the exact name of the form or the saved Ad Hoc Grid. If the name is invalid, provide a valid name to continue.
- If Data Retrieval Diagnosis is disabled, the assistant displays an option to enable it. Review the impact described by the assistant. Confirm that you want to enable the setting only after ensuring there are no active jobs. If you cancel, the assistant provides instructions to enable the setting manually and stops the diagnosis.
- If a diagnostic job already exists for the same user, application, and form,
then the assistant provides two options:
- Review existing result to reuse the prior result
- Reprocess to submit a new job. Reprocess after changing the form or metadata to evaluate the updated configuration.
- For a new job, review the progress updates while the diagnostic job runs in the background. When processing is completed, the findings and recommended actions are displayed. If there are actionable findings, you can also download the details in HTML format for reference.
Reviewing results and completing diagnosis
Results identify the issue category, the affected artifact, the observation, and the recommended action. For metadata findings, the artifact identifies the dimension and member. For form-design findings, it identifies the form.
| Category | Finding | Recommended action |
|---|---|---|
| Solve order | A Dynamic Calc member has an unsuitable solve order. | Set an appropriate solve order for the member and its aggregating ancestors. |
| Member formula | A level 0 Dynamic Calc member has no valid member formula. | Add a valid member formula. Where dynamic calculation is not required and the member can be changed, consider Never Share data storage. |
| Data storage | An Entity member uses unsupported Dynamic Calc data storage. | Use an appropriate supported storage option, such as Never Share, Store, or Shared, according to the member’s role. |
| Form design | An asymmetric form layout increases retrieval complexity. | Where practical, redesign the form with a more symmetric layout. |
Downloading the summary
When actionable findings are identified, download the HTML summary to refer to the findings while making changes. It contains the findings shown in the conversation. The file name includes the form name and diagnostic job ID.
If no supported inconsistencies are identified, the agent reports that result and does not generate an HTML summary. If retrieval remains slow, contact Oracle Support. A result with no findings does not establish that all possible causes of slow retrieval have been ruled out.Applying recommendations
Review and apply the recommended form or metadata changes manually. Retrieval findings are recommendations; the agent does not automatically resolve them. If a recommendation affects a predefined member that cannot be changed, follow the applicable metadata guidance in Troubleshooting Financial Consolidation and Close Retrieval Performance.
After making changes, request diagnosis for the form again and select Reprocess to obtain fresh results. Review existing result returns the prior analysis and does not assess your changes.
Disabling diagnosis
When diagnosis is complete, click Application, then click Consolidation Settings. From Setting Type, select Diagnostics, then disable Data Retrieval Diagnosis. The agent reminds you to disable the setting but does not turn it off automatically.