Consultor Eletrônico

Status: Verified

GOAL:

List debug options that can be used with Oracle DataServer?

GOAL:

-Dsrv qt_debug,SQL
-Dsrv qt_debug,EXTENDED
-Dsrv qt_no_debug
-Dsrv qt_debug,CURSOR
-Dsrv qt_debug,DATA-BIND
-Dsrv qt_debug,PERFORMANCE
-Dsrv qt_debug,SUMMARY
-Dsrv qt_debug,VERBOSE

FIX:

There are 8 connection/startup query tuning parameters that can be used with -Dsrv.

Standard Debug options
-Dsrv qt_debug,SQL
-Dsrv qt_debug,EXTENDED
-Dsrv qt_no_debug

Performance Debug options
-Dsrv qt_debug,CURSOR
-Dsrv qt_debug,DATA-BIND
-Dsrv qt_debug,PERFORMANCE
-Dsrv qt_debug,SUMMARY
-Dsrv qt_debug,VERBOSE

There are 3 QUERY-TUNING phrases/options that can be included into Progress statements. Please note that if you decide to implement QUERY-TUNING phrases into your Progress code, you can not use the startup parameters to override the QUERY-TUNING settings.

QUERY-TUNING DEBUG ExTENDED
QUERY-TUNING DEBUG SQL
QUERY-TUNING NO-DEBUG

These parameters specify whether the DataServer should print debugging information that it generates for the query to the dataserv.lg file.

1. By default, DataServer uses qt_no_debug
2. qt_debug,SQL prints the SQL that the DataServer executes against the ORACLE DBMS.
3. qt_debug,EXTENDED prints information in addition to the SQL statements executed by the DataServer, such as cursor statistics.
4. qt_debug,option to override the NO-DEBUG default.

In addition to the standard debug options, there are other options that can assist in analyzing performance. Please refer to Progress DataServer for Oracle Guide; Chapter Analyzing Performance for how to implement these parameters and how they can help.

Example:Implement connection/startup query tuning parameters,
_progres -db oschema -1 -db oracle -dt ORACLE -U user -P password -Dsrv qt_debug,EXTENDED

Example:Implement QUERY-TUNING DEBUG phrase,
FOR EACH customer WHERE cust_num < 100 QUERY-TUNING(DEBUG SQL):