odbcinst.ini
file's [ODBC]
section to set the values Trace=Yes
and TraceFile
to the path of the file which is to contain the trace output; for example:/dev/stdout
or any other device name to send trace output there instead of to a persistent file.) With the above settings, every time an application loads the unixODBC Driver Manager, it will record all the ODBC API calls which it performed into the output file.Trace=Yes
from the odbcinst.ini
file to avoid the performance penalty of tracing, and ensure any unnecessary trace files are removed.odbcinst.ini
. To not trace all applications (for example, to avoid disclosing sensitive per-user information), you can trace an individual application instance by providing it the location of a private odbcinst.ini
, using the ODBCSYSINI
environment variable. For example:Trace=Yes
to the [ODBC Driver 13 for SQL Server]
section of /home/myappuser/odbcinst.ini
.odbc.ini
is in use, or the path to the odbc.ini
file. However, information about which odbc.ini
file is in use is available from the unixODBC tools odbc_config
and odbcinst
, and from the unixODBC Driver Manager documentation.odbc.ini
files which contain, respectively, system and user DSNs:odbc::odbcListDrivers()
.odbcinst
, which can be used toquery and modify the DSN files. However, these are plain text files youcan also edit by hand if desired.odbcinst.ini
defines driver optionsodbc.ini
defines connection optionsodbcinst.ini
./etc/odbc.ini
or /opt/local/etc/odbc.ini
. The file location depends onwhat option was used when compiling unixODBC; odbcinst -j
can be used to findthe exact location. Alternatively, the ODBCSYSINI
environment variable can beused to specify the location of the configuration files. Ex. ODBCSYSINI=~/ODBC
~/.odbc.ini
and ~/.odbcinst.ini
.dbConnect()
function.