Application Tier: Forms

Forms performance issues may arise when dead connection persists on the server and consuming the server resources. Enable the forms dead client connection can eliminate the dead connection.

  • FORMS60_TIMEOUT=10 (recommended value and value specified in minutes)
  • Do $ ps –ef| grep f60webmx and terminates f60webmx processes for dead clients.
  • Enable Forms Abnormal Termination Handler by enabling theFORMS60_CATCHTERM
  • Deploy with socket mode for internal user.
  • Form – Cancel Query Should not be enabled unless you are on Forms patch set 14 (Forms version 6.0.8.23.x or higher).Cancel Query increases middle-tier CPU as well as DB CPU. To disable the cancel query, Set the Profile “FND: Enable Cancel Query” to No.
  • Tune the Cancel query features like
    • Export FORM60_LOV_INITIAL=32000
    • Export FORM60_LOV_MINIMUM=5000
    • Export FORM60_LOV_WEIGHT=0
    • These variables must be set in $APPL_TOP/.env or ‘formservlet.ini’ file.
  • Ensure users are optimally utilizing the professional Forms interfaces and for that avoid opening and closing forms across transactions
  • Avoid Blind queries
  • Trace Form.
    • Open the problematic, Go to Menu > Help > diagnostics > Trace with waits and binds

Application Tier – Reports

  • Ensure users provide selective parameters to the standard reports.
  • Review the report output:
    • Number of rows returned to the report.
    • Number of report pages.
  • SQL Trace can be generated at request submission time (SRS form – Debug Options) or by setting the “Enable Trace” flag in the concurrent program definition form.

Reports Tracing:

  • If the SQL trace for the report does not account for the elapsed time of the request, then generate a reports trace by appending tracing parameters to the concurrent program command line.
  • The following are the trace options:
    • TRACE_ALL: log all possible trace information in the trace file. (DEFAULT)
    • TRACE_APP: log traces information on all the report objects in the trace file.
    • TRACE_BRK: list breakpoints in the trace file.
    • TRACE_ERR: list error messages and warnings in the trace file.
    • TRACE_PLS : log traces information on all the PL/SQL objects in the trace file.
    • TRACE_PRF : log performance statistics in the trace file.
    • TRACE_SQL : log traces information on all the SQL in the trace file.
    • TRACE_TMS: enter a timestamp for each entry in the trace file.
  • Enabling Reports Trace (pre 11.5.10)
    • Sign-on to Apps with System Administrator responsibility
    • Navigate to Concurrent -> Program -> Define Query the concurrent program (report) which you want to trace. Locate the “Options” field and enter the following values : TRACEOPTS= TRACEFILE
    • Save the concurrent program
    • Run the report and a trace file will be generated.
    • Remember to clear the trace options after running the report.
  • Enabling Reports Trace (11.5.10)
    • Use the Debug Options page at request submission.
PrintFriendly

Viewers of this post also viewed...