Using the InterSystems ODBC Driver
Logging and Environment Variables
This chapter describes some tools you can use to perform troubleshooting. It discusses the following topics:
Enable logging only when you need to perform troubleshooting. You should not enable logging during normal operation, because it will dramatically slow down performance.
To enable logging for the client driver, find the definition of the DSN that you want to log, open it, and check the box labeled ODBC Log
On UNIX®, enable logging for ODBC as follows:
If you enable logging but the log file is not updated, either you might not have privileges to write to the file or the client application may have loaded the SO before you enabled logging. In the latter case, stop and restart the client application to force it to reload the SO and get the logging flag.
This section describes the environment variables that control the InterSystems ODBC client driver. Typically you use these only for debugging or diagnostics.
This variable allows you to specify the duration of a timeout for a default login. Its value is in seconds.
This boolean variable controls the automatic appending of the process ID number to the log file name. Set the value to 1
to enable appending, or 0
to disable. By default, appending is off.
IRISODBCTRACE (UNIX® Only)
This variable specifies the location and name of the log file. This can be useful for placing the log file in a unique directory or giving it a unique name. The default name for the log file is IRISODBC.log
. The default location is as follows:
This variable controls whether the log also includes threading information. Set the value to 1
to enable inclusion of threading information, or 0
It can be useful to enable this additional kind of logging, if you need to debug a threaded application. However, it adds many extra lines to the log for most ODBC applications.
Content Date/Time: 2019-04-23 13:43:21