Analyzing Performance
The qt_debug option of the DataServer (-Dsrv) startup parameter (and the QUERY-TUNING DEBUG phrase) instructs the DataServer to print information on the queries it generates to the dataserv.lg
log file. The qt_debug option provides extended diagnostic capabilities that you can use to determine which parts of your application might be causing additional network traffic or processing by ORACLE. Table 4–8 lists the diagnostic capabilities of qt_debug. Note that the log file uses the numeric values (in parentheses) to identify information that a specific option generates.
Table 4–8: Diagnostic Options
Option
|
Description
|
CURSOR (18835)
|
Information about the ORACLE cursors that the DataServer uses for internal ORACLE Call Interface (OCI) calls and for opening queries. It tracks when cursors open, close, and when the DataServer reuses them. It also summarizes each cursor’s activity. These diagnostics are especially helpful when determining Progress and ORACLE maximum cursor settings or cursor “leaks” that your application might have.
|
DATA-BIND (1029)
|
Information about the data types, buffer sizes, and addresses that the DataServer and ORACLE use when binding variables.
|
PERFORMANCE (55775)
|
Information on the time certain operations take. These statistics are available only for some platforms. Note that any time differences between what the DataServer reports and what the ORACLE tkprof utility reports might be due to network performance issues, rather than to DataServer or ORACLE behavior.
|
SUMMARY (1073797455)
|
Information on cursors and timing in summary form as a Progress data (.d) file. Call Progress Software Corporation Consulting for assistance with this file. This option is not available as a QUERY-TUNING phrase option.
|
VERBOSE (122879)
|
Information on all of the above. This option generates a very large log file. Remember to clear your log file before using this option to test a procedure.
|
NOTE: Turning on debugging options decreases DataServer performance. Be sure to turn off debugging options when running DataServer applications in production mode.
This connection statement causes the DataServer to report on the time that certain operations take: