< Previous section Content Next section > In the current version of application you can generate the following report types:
The following sections provide a detailed description of the available reports. ExamineReport of this type was designed for quick learning trace-file. It displayed in text form (if the application was started with command-line interface) or in the dialog form (if the application started with GUI) and includes the following data:
The following is a sample report: Pic. 23 Report “Examine”
File info >>> folder: C:\LightProfiler\trc\samples file: count_one_ora9.trc created: 12.01.2012 15:30:44 modified: 05.01.2012 00:19:16 size: 52400 bytes
Main info >>> oracle version: 9.2.0.8.0 trace level: 12 session(s): *** SESSION ID:(9.3) 2010-02-11 00:04:24.321 available "dep": 0, 1, 2 contain RPC events: False contain LOB events: False
Preamble >>> Dump file c:\oracle\admin\test9\udump\test9_ora_2816.trc Thu Feb 11 00:04:24 2010 ORACLE V9.2.0.8.0 - Production vsnsta=0 vsnsql=12 vsnxtr=3 Windows 2000 Version 5.2 Service Pack 2, CPU type 586 Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production Windows 2000 Version 5.2 Service Pack 2, CPU type 586 Instance name: test9
Redo thread mounted by this instance: 1
Oracle process number: 12
Windows thread id: 2816, image: ORACLE.EXE
Generating a report of this type can be done with any profiler's status, and does not take much time or resources. To generate a report, select "Reports" - "Examine" via application menu or press the corresponding button on the profiler's toolbar. Resource profileReport “Resource profile” is a detailed description of trace-file contents, which includes information about the database wait events1, SQL statements, runtime or parse errors and other useful information, needed to solve optimization problems, or to debug your code. The report consists of several html-files that are generated in directory specified by the option "Output folder" (by default - <application folder> / output). The file structure of this report, is schematically represented below:
Note: Report “Resource profile” can be generated only for profiler having status - “Parsed”. Generation of such report may take a long time (depending on size of source trace-file and the profiler options), so, when generating report for a file having a size, greater than 10MB, you will be asked to renounce the use of resource-intensive options: Pic. 24 Resource-intensive options To generate a report - select the menu item “Report” (“Active” / “All”) - “Profile” or use application's toolbar or active profiler's toolbar.3. Also, you can use the operation “P&P”, that doing parse and report generation as one operation. Sections for profileThe current version of application can generate the following sections of report "Resource profile":
Pic. 25 Section “Parameters”
Pic. 26 Section “Preamble”
Pic. 27 Section “Response time by
events”
Pic. 28 Section “Response time by
SQL statements”
Pic. 29 Section “Response time by
SQL cursors”
Pic. 30 Section “Events”
Pic. 31 Section “Events graph”
Pic. 32 Section “SQL statements
(Overview)”
Pic. 33 Section “SQL statements
(brief)”
Pic. 34 Section “Datafiles usage”
Pic. 35 Section “Snapshots” Sections for statementFor specific SQL statements, during resource profile creation, may be generated detailed descriptions – the reports “Statement detail”4. You can go to this reports, by clicking link “Detail” from section “SQL statements (brief). The current version of application can generate following sections for this report:
Pic. 36 Section “Stats”
Pic. 37 Section “Events”
Pic. 38 Section “Database calls”
Pic. 39 Section “Bind-set(s)”
Pic. 40 Section “Data histograms”
Pic. 41 Section “Execution plans”
Pic. 42 Section “Snapshots” Sections for snapshotFor the report “Snapshot”, can be generated following sections:
OptimizationThe current version of application provides the following types of optimization's reports:
The optimization's reports are based on two or more analyzed trace-files, and represent a comparison of general characteristics: duration time, elapsed time (in general for profile or for statement), characteristics of events. In the current version of application, comparison is occurring by the pairs (the order of comparison is user-defined on stage before report generation) - the stages. If for comparisons was selected only two trace-files, then the report will contain only one stage, if there are N files, then the report will contain the N-1 stages and the one final stage - the comparison of first and last trace-files. In the optimization reports are used color highlighting, for results of comparing characteristics of trace-files:
Resource profile optimization for sessionIn the current version of application, each stage of this report contains following sections:
Pic. 43 Section “Files info”
Pic. 44 Section “Total stats”
Pic. 45 Section “Events
(impr.(+)/degr.(-))” Generation of the report "Resource profile optimization for session" consists from the following steps:
Pic. 46 Generate a report for session
Note: To generate an optimization report, all profilers that are including in report, should be analyzed with same options. In case, if the profilers options has differences, or parsing for profiler has not yet been fulfilled, then for these profilers will be executed operations "Reset" and "Parse" with same options as for first profiler in list. Resource profile optimization for SQL statementIn the current version of application, each stage of this report contains following sections:
Process of the report generating "Resource profile optimization for SQL statement" consists from the following steps:
Pic. 47 Generate a report for SQL
statement
Note: To generate an optimization report, all profilers that are including in report, should be analyzed with same options. In case, if the profilers options has differences, or parsing for profiler has not yet been fulfilled, then for these profilers will be executed operations "Reset" and "Parse" with same options as for first profiler in list.
Note: You must select SQL statement for each trace-file.
1Depends on the trace level 2The serial number has assigned from application depending on statement’s occurrences in the source trace-file 3For parsed profilers 4By default, a report "Statement detail" will be created only for statements which was highlighted in any part of the report "Resource profile" or having error/ warnings. This behavior is governed by the profiler options. |