This option is useful in the event of a crash. The ODBCTraceFlush keyword forces the trace library to write to the trace file after each ODBC API call. If set to 3, both TraceOptions=1 and TraceOptions=2 are enabled. By default, the header includes the parent process ID and process ID. If set to 2, the log file prints a header on every line. If set to 1, the log file includes a timestamp on ENTRY and EXIT of each ODBC function.
#Ti connect ce for linux driver
If set to 0, the driver uses standard ODBC tracing. The TraceOptions keyword specifies whether to print the current timestamp, parent process id, process id, and thread id for all ODBC functions to the output file. Subsequent files are named by appending sequential numbers, starting at 1 and incrementing by 1, to the end of the original file name, for example, odbctrace1.out, odbctrace2.out, and so on. Once the maximum number of log files is created, tracing reopens the first file in the sequence, deletes the content, and continues logging in that file until the file size limit is reached, after which it repeats the process with the next file in the sequence. The ODBCTraceMaxNumFiles keyword specifies the maximum number of log files that can be created.
Once this file size limit is reached, a new log file is created and logging continues in the new file until it reaches the file size limit, after which another log file is created, and so on. The ODBCTraceMaxFileSize keyword specifies the file size limit (in KB) of the log file.
0 kommentar(er)
