Using Caché with ODBC
[Home] [Back] [Next]
InterSystems: The power behind what matters   
Class Reference   

This chapter describes how to enable logging when you need 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.
When using the SQL Gateway (as discussed in Using the Caché SQL Gateway with ODBC), be sure to consult the documentation for the remote database to which you are connecting.
Enabling Logging for ODBC on Windows
On Windows, to enable logging for an ODBC data source, you generally use the ODBC Data Source Administrator screen (within the Windows Control Panel). To access this screen, open the Windows Control Panel, open the Administrative Tools subpanel, and then double-click Data Sources (ODBC). Or open the Windows Control Panel and then double-click ODBC Data Sources.
Then do the following:
The details may vary depending on your version of Windows as well as the client driver that you use for this DSN.
The default location of the CacheODBC.log file varies depending on the version of Windows. For Windows Vista and higher, the log will be created in the Public folder under %PUBLIC%\Logs (default path C:\Users\Public\Logs). This folder is accessible by all users and allows just one location for the log to be created. For earlier versions, the log is under %WINDIR% (the C:\Windows or C:\WinNT folder, depending on your version of Windows).
You can change the name and location of the log file by setting the CACHEODBCTRACEFILE environment variable (see Caché ODBC Environment Variables).
Enabling Logging for ODBC on UNIX®
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 DLL before you enabled logging. In the latter case, stop and restart the client application to force it to reload the DLL and get the logging flag.