Try OpenEdge Now
skip to main content
DataServer for Oracle
Connecting the DataServer : Connecting a schema holder : Analyzing application execution with Enhanced Logger : qt_debug logging
 
qt_debug logging
The existing qt_debug logging only logs server information. This option is available only for backward compatibility and no further logging enhancements will be done in the current and future releases.
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. The syntax for the qt_debug options is:
CONNECT <dbname> -U <username> -P <password>
-Dsrv qt_debug,<option>[,qt_debug,<option>...]
The default setting is for all debugging information to be turned off (-qt_no_debug). Specify qt_debug,option to override the NO-DEBUG default.
The following table lists the diagnostic capabilities of qt_debug.
Table 55. Diagnostic options
Option
Description
SQL
Specify qt_debug,SQL to print the SQL that the DataServer executes against the Oracle DBMS in the dataserv.lg file.
EXTENDED
Specify qt_debug,EXTENDED to print the SQL information that the SQL option generates, plus additional information such as cursor statistics in the dataserv.lg file.
CURSOR
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 ABL and Oracle maximum cursor settings or cursor "leaks" that your application might have.
DATA-BIND
Information about the data types, buffer sizes, and addresses that the DataServer and Oracle use when binding variables.
PERFORMANCE
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
Information on cursors and timing in summary form as an OpenEdge data (.d) file. This option is not available as a QUERY-TUNING phrase option.
VERBOSE
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:
CONNECT oradb -U user -P password
-Dsrv qt_cache_size,32000,QT_BYTE,qt_debug,PERFORMANCE.