Feedback
Did this article resolve your question/issue?

   

Article

ODBC trace file is overwritten everytime that the application is re-started or a new connection is made

Information

 
TitleODBC trace file is overwritten everytime that the application is re-started or a new connection is made
URL NameODBC-trace-file-is-overwritten-everytime-that-the-application-is-re-started-or-a-new-connection-is-made
Article Number000183357
EnvironmentProduct: Connect for ODBC Drivers
Version: 7.1
OS: UNIX/LINUX
Database: All supported databases
Application: All supported applications
Question/Problem Description
A trace file is overwritten everytime that the application (for example the example application) is re-started or a new connection is made.
Steps to Reproduce
Clarifying Information

Approach:

  1. ODBC Tracing will read an additional Tracing Option call TraceFilePerProcess, the default will be 1 (enabled). Users can set this Tracing option in the ODBC DSN TraceFilePerProcess=1 to enable this.
  2. If this option is disabled; the ODBC tracing behavior remains as is.
  3. If this option is enabled; the ODBC Tracing will append the Process ID to the Trace File name present in the ODBCINI. like <ODBC_TRACE_FILE>_<PROCESS_ID> to create unique ODBC Trace file per process.
  4. The TraceOption behavior will defautlt like TraceOptions is set to 3.
  5. Rest of the of trace options would be still applicable and can be used with this new approach.
Error Message
Defect NumberDefect 83911
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.16.0276 (U0246)
Refer to  Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/20/2020 7:18 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.