Wednesday, April 20, 2011

Oracle Ebusiness Suite Health Check : FORMS

Apps Tier Performance Tuning: FORMS
 


      Note:  Keep Forms Patchset Current (125767.1)

  • Use Socket Mode (AutoConfig variable --> s_frmConnectMode=socket)
  1. It reduces client network traffic (as compared to servlet mode)
  2. Eleminates the need to run Forms Servlet JVMs
  • Enable dead client detection FORMSS60_TIMEOUT(AutoConfig variable--> s_f60time)
    • Set to 5 or 10 minutes
  • Use forms termination handler FORMS60_CATCHTERM(s_f60catchterm)
    • Set to 1                                                  


    Environment variable which restricts LOV fetch set  
  1. FORMS60_RECORD_GROUP_MAX(PS 15 or higher)
  2. Avoids large footprint of forms runtime process associated with none selective LOV queries.
  • Purge/archive Forms runtime log files as part of Forms server restart:
  1. $FORMS60_RTI_DIR/*.rti
  2. $FORMS60_RTI_DIR/f69webmx_dump*
  3. $FORMS60_TRACE_PATH/*.log
  • Schedule purge program "Purge Obsolete Generic File Manager Data" if the forms Export function is being used.
  • Enable Forms Dead Client Detection :
    Value specified in minutes : FORMS_TIMEOUT=10
    1: Terminates fwebmx processes for dead clients.
    2: Enable Forms Abnormal Termination Handle
  •  Disable Cancel Query
    1:Cancel Query increases middle-tier CPU as well as DB CPU
     3:To Disable Cancel Query :  Set the Profile "FND: Enable Cancel Query" to 'No'
  • Cancel Query
  1. Useful for cases where users regularly or occasionally perform "accidental queries.
  2. Not useful for cases where users have no intention of canceling the query or functionally require the results of the expensive query.
  3. Increases forms and DB session CPU utilization.
  4. Increases network traffic between client and forms tier.
  5. Enable cancel query at the application or responsibility level (where required).  
  • Review Network traffic
  1. Reports cumulative bytes and round trips (between Forms process and the client applet) in the Forms message bar.
  2. URL parameter netStats=true
  • To reduce load on the database server, ensure users are optimally utilizing the professional Forms interfaces.
  1. Avoid Blind queries
  2. Provide selective criteria in Find windows and LOVs 
  • Minimize network traffic and form open times
    • Avoid opening and closing forms across transactions
    • Combine forms from multiple-products onto a single menu
  • Forms and DB Timings
    • Help_About Oracle Applications shows performance information
    • including time spent in the Form and the DB (11i10 & R12)
 


Forms (Tracing):

  • If the form is slow, or a specific flow in the Form is slow, first generate a complete SQL trace using the Trace menu in Help-Diagnostics
  • To analyze acitivity in the forms process, you can generate a Forms Runtime Diagnostics (FRD) Trace
    • Logon to Applications with the following parameters appended to the URL: play=&record=collect&log=/tmp/oeform.trc
    • Exit Apps completely after performing the transaction



 
 

No comments:

Post a Comment

Post a Comment