JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

Output where T4LogLevel is set to SEVERE
0000001 ~ 10/22/2004 10:22:19 ~ 001234 ~ 0049934 ~ ~ ~
~ SQLException Operation cancelled.
SQLSTATE = S1008
SQLCODE = 01118
Output where T4LogLevel is set to FINER
0000006 ~ 10/22/2004 10:34:45 ~ 001234 ~ 0049934 ~ FetchRowSetMessage ~ marshal
~ Entering FetchRowSetMessage.marshal( en_US
, 48345
, STMT_MX_8843
, 5
, 4192,
, 0
, 0 )
Controlling the QueryExecuteTime Logging Facility
The Type4 driver provides two properties that you can use to control the QueryExecute logging output:
queryExecuteTime: Specifies the time limit to log information about statements which are taking more than the specified time for execution. For
information on using this property, see
queryExecuteTime Property.
T4QueryExecuteLogFile: Specifies the file in which the driver must log information. For information on using this property, see
T4QueryExecuteLogFile Property.
If the application sets several property values, see
Precedence of Property Specifications to determine which setting applies.
QueryExecuteTime logging Message Format
The format of the trace output is:
sequence-number ~ time-stamp ~ ~ ~ ~ statement-id.SQL query
~
TIME TAKEN execution-time ms
where,
sequence-number is a unique sequence number in increasing order.
time-stamp is the time at which the message is generated. For example, 10/17/2004 12:48:23.
statement-id is the statement identifier within the JDBC T4 driver.
SQL query that is consuming more than the specified time.
execution-time is the time taken to execute the SQL query.
Examples of QueryExecuteTime Logging Output
The following output is an example of QueryExecuteTime logging:
00000394 ~ Jul 7, 2011 10:08:11 AM GMT ~ 10 ~ ~ ~ ~
SQL_CUR_MFC00000001.SELECT COF_NAME, PRICE FROM ctstable2() ~
TIME TAKEN 47 ms
Prev Up Next
Chapter 8. Type 4 Driver Compliance Home Chapter 10. Migration and Compatibility
Part Number
663860-001 Legal Notices