1.1.1    How to Use Performance Collection Services

  1.1.2    Events Collected by Performance Services

  1.1.3    Analyzing the Performance Data

  1.1.4    Default Events

 

　1.2  　Using Oracle Trace Instead of PECS for Performance Analysis

 

  1.2.1    Initiating Trace Data Collection

  1.2.2    Using the Oracle Trace Command-Line Interface

  1.2.3    Oracle Trace Collection Files

  1.2.4    Events Collected by Trace

  1.2.5    Using the Oracle Trace Statistics Reporting Utility

  1.2.6    Viewing the Trace Data

  1.2.7    Trace Tables

 

 

 

 

  1.1     Performance Collection Services Now Available

 

           The Forms runtime diagnostics have been enhanced with the

           addition of Performance Collection Services.  These provide you

           with information you can use to better understand and improve

           your application's runtime performance.

           The following subsections provide details.

 

  1.1.1   How to Use Performance Collection Services

 

           To activate Performance Collection Services, include

           "record=performance" in the command line argument (for runtime

           in a client/server environment), or as a part of "serverArgs"

           parameter in the HTML file (for web deployment).

 

           For example, if running in the client/server mode, invoke using

 

            ifrun60  module=.. userid=.. record=performance log=yourlogname

 

           The results are written onto file yourlogname. If the file name

           is not specified, a file with a unique filename is created. This

            name is in the format "perf_xxxx" where "xxxx" is the ProcessId

           of the runtime process running.

 

           In the HTML file, this invocation will be:

             <param name= "serverArgs" value = "module=.. userid=..

              record=performance log=yourlogname">

 

 

  1.1.2   Events Collected by Performance Services

 

           Event              Meaning

           ___________     _________________________

           ClientTime      Time spent at the Client

           Logon Time      Time to logon to the Database Server

           LogoffTime      Time to logoff the from the Database Server

           DB Time       Time for any database operations, such as query

           APServerTime     Processing time at the Forms Server

 

 

 

  1.1.3   Analyzing the Performance Data

 

           The data collected by Performance Services is analyzed using

           PERL scripts "f60parse.pl", which are located in the

           ORACLE_HOME\forms60\perl directory

 

            perl f60parse.pl -input=infile -eventf="evfile" -outputf="ofile"

 

           where:

                 Infile  Recorded data while running the application.

                 Evfile  Event Description File.

                 Ofile   Results file generated by the PERL Script.

 

                 Eventf and outputf are optional parameters.

 

           A typical event description file is of the following form:

 

            Client       ThinkTime      THINK_START      THINK_END

            _______      __________     _______________  ____________

            DBLOGON       Logon       DBLOGON_START   DBLOGON_END

            APServer       Logon_Wr     DBLOGON_END    THINK_START

            DBPROC        DB         DB_START     DB_END

            APServer       DB_App       DB_END      DB_START

            APServer       DB_Write      DB_END      THINK_START

            APServer       DB_Logoff     DB_END       DBLOGOFF_START

            DBLOGOFF       Logoff      DBLOGOFF_START  DBLOGOFF_END

 

           If an events file is not specified, the following default events

           are assumed by Performance Collection Services:

 

           FSPreLogon  - Time Spent at the FS Server before Logon

           DBLOGON  -  Logon time at the DB Server

           FSPostLogon  - FS processing time after LOGON at the DBServer

           FSPreDB - User Input processing at the FS before query to DB

           DBPROC - Processing time at the DB Server

           FSMidDB - Processing  Time at FS between successive DB actions

           FSPostDB - Processing Time at FS after DB query

           PreLogoff  -  Processing Time at FS before Logoff

           DBLOGOFF - Time to Logoff from the DB Server

           Client+Net  - Time spent at the Client and the Network

           Client+Net+User  - Time spent at the Client, Network and the

           User while waiting for user interaction.

 

  1.1.4   Default Events

 

           By default, the output appears in the following HTML files

           (which can be viewed in a browser):

 

           1.  index.html  - Summary of user action

           2.  detailed1.html  - Detailed events

           3.  detailed2.html - Detailed event collection

           4.  event.html - Event definitions

 

           When specified, an XLS output file is created with the given

           name.

 

           A typical results file has three sections:

 

            1. Summary

            2. Detailed Description (Level1)

            3. Detailed Description (Level2)

 

  1.2     Using Oracle Trace Instead of PECS for Performance Analysis

 

           Although PECS is supported in this 6i release, such support is

           not planned for any future Forms releases.

           You can use Oracle Trace to provide functionality that is

           similar to PECS. Integration of Oracle Trace functionality with

           Forms is a beta feature introduced in Forms Developer 6i.

 

           The Oracle Trace-based Forms implementation supports a subset of

           the events defined in PECS. In addition, a few new events are

           also defined and supported. The event definitions reside in the

           file ORACLE_HOME\otrace80\admin\fdf\oforms.fdf on Windows NT,

           and ORACLE_HOME\otrace\admin\fdf\oforms.fdf on Unix. This file

           is essential for activating Trace in Forms, and is supplied as

           collateral on the Forms Developer 6i CD.

 

 

  1.2.1   Initiating Trace Data Collection

 

           Data collection on the Forms Server needs to be initiated either

           through the command line, or through Trace Manager -- which

           comes as part of Oracle Enterprise Manager with Diagnostic Pack

           ver.2.1.

 

           The command line interface requires Oracle Trace CLI version 9,

           which comes as part of the 8.0.6 components and is supplied as

           collateral on the Forms Developer 6i CD.

 

           To enable actual data collection in a web environment, include

           ?pecs=trace? as part of the ?serverArgs? parameter defined in

           the HTML file used for running the form.

 

 

  1.2.2   Using the Oracle Trace Command-Line Interface

 

           You invoke this interface by variations of the OTRCCOL command,

           which provide the following functions:

 

            OTRCCOL START job_id input_parameter_file

            OTRCCOL CHECK col_name

            OTRCCOL STOP job_id input_parameter_file

            OTRCCOL DCF col_name cdf_file  [to delete collection file]

 

           The parameter job_id can be any numeric value.  The input

           parameter file contains specific parameter values required for

           each function as shown in the following examples. COL_NAME

           (collection name) and CDF_FILE (collection definition file)

           are initially defined in the START function input parameter

           file.

 

           The OTRCCOL START command invokes a collection based upon

           parameter values contained in the input parameter file.

           For example:

                  otrccol start 1234 my_start_input_file

           where my_start_input_file contains the following input

           parameters:

                  col_name= my_collection

                  dat_file= <usually same as collection name>.dat

                  cdf_file= <usually same as collection name>.cdf

                  fdf_file= <server event set>.fdf

                  regid= 1 192216243 0 0 45 <database SID>

 

           These parameter file records are all required for otrace

           collection, and the regid record must contain the values shown,

           including your SID value.

 

           The OTRCCOL STOP command halts a running collection as follows:

                  otrccol stop 1234 my_stop_input_file

           where my_stop_input_file contains the collection name and

           cdf_file name.  You can use the same otrace input parameter file

           as used with the START command.

 

  1.2.3   Oracle Trace Collection Files

 

           Running an Oracle Trace collection produces the following

           collection files located in the directory specified in INIT.ORA

           or in the default collection path:

 

             collection_name.cdf   This is the Oracle Trace collection

                                   definition file for your collection.

 

             collection_name.dat   These files are the Oracle Trace output

                                   files containing the data in binary

                                   format.

 

  1.2.4   Events Collected by Trace

 

           These are the events collected by Trace Collection Services.

 

           Subset of PECS Events:

              * Application    - (a session with the Oracle Forms Server)

              * Form           - (from opening to closing of a form)

              * ExeQuery       - (Query Execution)

              * Trigger        - (Trigger)

              * LOV            - (LOV)

              * MenuCreate     - (MenuCreation)

              * Alert

              * Timer

              * Window

              * Canvas

 

           Additional Events:

              *  DB Logon

              *  DB Logoff

              *  ServerTime

              *  DBTime

 

           You can access the Oracle Trace data contained in the collection

           files in the following ways:

 

            - Create Oracle Trace reports from the binary file.

 

            - Use Oracle Trace Data Viewer (data must be formatted).

 

            - Format the data to the tables in the Oracle database for SQL access and reporting.

 

  1.2.5   Using the Oracle Trace Statistics Reporting Utility

 

           The Oracle Trace statistics reporting utility displays

           statistics for all items associated with each occurrence of a

           server event.

           These reports can be quite large. You can control the report

           output by using command parameters. Use the following command

           and optional parameters to produce a report:

                otrcrep [optional parameters] collection_name.CDF

 

           The first step y