# How To Capture a Log for the ODBC Wrapper in Linux

**URL:** <https://community.cdata.com/t/how-to-capture-a-log-for-the-odbc-wrapper-in-linux/411>\
**Category:** Editions\
**Tags:** article, odbc, linux-unix\
**Created:** [September 22, 2023, 2:03pm UTC](https://community.cdata.com/t/how-to-capture-a-log-for-the-odbc-wrapper-in-linux/411 "2023-09-22T14:03:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BobbyQ](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@BobbyQ](https://community.cdata.com/u/BobbyQ)\
**Post date:** [September 22, 2023, 2:03pm UTC](https://community.cdata.com/t/how-to-capture-a-log-for-the-odbc-wrapper-in-linux/411/1 "2023-09-22T14:03:16Z")

</div>

The CData ODBC Driver targeting Linux distributions is based off of JNI. The JNI layer has its own separate logging implementation which differs from the standard driver logs. It allows you to capture more detailed information on the ODBC Wrapper layer for advanced troubleshooting when dealing with errors of this nature.

To enable this separate logging, you will need to set the CDATA\_ODBC\_LOG environment variable.

If you would like to log to a specific location, say /var/odbcwrapper.log, you can follow the listed instructions:

1. In your Linux distro run the terminal

2. Use the ‘export’ command to set the CDATA\_ODBC\_LOG environment variable

3. $export CDATA\_ODBC\_LOG=”FILE:///var/odbcwrapper.log|DEBUG"

After the Pipe character you can specify the level of detail you require in the desired log.

Possible values are: FATAL, ERROR, WARNING, INFO, DEBUG.

In case there is trouble generating the log check for write permissions in the directory you chose to write the log into.