Identifying and Correcting Issues

Use the procedures in this section to identify and correct issues that may cause unacceptable Planning forms performance.

  1. Review the best practices to replace zero blocks and remove #missing blocks in BSO cubes to reduce database size. See Optimize BSO Cubes.
  2. Review the Activity Report, which contains information on the impact of business rules on performance. Specifically, review the Business Rules Attached to a Form Taking Longer than 3 Seconds section of the report to determine if an attached business rule is causing poor performance. Use the instruction in Troubleshooting Business Rules and Member Formula Errors and Performance to optimize business rules attached to the form.

    Ensure that the network proxy timeout setting is sufficient to meet the business rule execution time requirements. If a business rule attached to a form takes longer than three minutes to execute and the network proxy timeout is set to three minutes or less, your proxy may repeatedly execute the rule. You can avoid this issue by setting the network proxy timeout to more than 3 minutes.

  3. If performance does not improve after completing the preceding steps, review the application design, the number of cells on the form, and dynamic content in the form in order to improve the performance.
    1. Ensure that the member data storage property of all Level 0 members that do not use a member formula is set to Never Shared.
    2. Ensure that level 0 members tagged as Dynamic Calc has a formula. See Level0 Members Tagged as Dynamic Calc but without a Formula.
    3. Always design a symmetric (versus asymmetric) form. Oracle Essbase queries may be symmetric or asymmetric. Symmetric queries are those where members queried on rows or columns are of cross-dimensional layout. Asymmetric queries are those where the cross-dimensional layout of the members being queried changes in either the rows or the columns.

      On encountering an asymmetric query, the Essbase hybrid query engine, which processes only symmetric grids, automatically breaks it into multiple symmetric grids. These symmetric grids are processed one at a time and then returned in the original asymmetric form, which makes the process less efficient.

  4. If you get the Unable to load the data entry form as the number of data entry cells exceeded the threshold error, see Resolving the Unable to load the data entry form as the number of data entry cells exceeded the threshold Error for options to resolve the error.
  5. If performance still does not improve, seek help from Oracle.
    • Create a Provide Feedback submission, and include screenshots of the form as you run it in your environment.

      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:
      • Is this a Forms 1.0 form or a Forms 2.0 form?
      • Name and path of the form, all POVs, and all user and substitution variables being used.
      • Expected performance parameters and actual results.
      • Did this issue start after the latest monthly update?
      • If the performance of the form was acceptable previously, but is not now, include the date, time, and time zone when performance was acceptable.
      • Snapshot of the environment, if available, from the last time when the performance of the form was acceptable.
      • Form changes that you made since the last time when the performance was acceptable.
      • Whether this is a critical outage.