To help troubleshoot issues, you can enable logging in the driver. Logging is configured through driver-wide settings in the teradata.teradataodbc.ini file, which apply to all connections that use the driver.
Using any of the logging options will significantly degrade performance. Enable logging only long enough to capture an issue.
- Open the teradata.teradataodbc.ini configuration file in a text editor.
Set the LogLevel setting to one of the following values:
LogLevel Value Description 0 Disables all logging. 1 Logs severe error events that lead the driver to abort. 2 Logs error events that might allow the driver to continue running. 3 Logs events that might result in an error if no action is taken. 4 Logs general information describing the progress of the driver. 5 Logs detailed information useful for debugging the driver. 6 Logs all driver activity.
- Set the LogPath key to the full path of the target folder where you want to save the files.
Set the LogFileCount key to the maximum number of log files to keep.
After the maximum number of log files is reached, the driver deletes the oldest log files each time an additional file is created.
Set the LogFileSize key to the maximum size of each log file in megabytes.
After the maximum file size is reached, the driver creates a new file and continues logging.
- Save the teradata.teradataodbc.ini configuration file.
Restart your ODBC application to verify the new settings.
The new Teradata ODBC Driver produces two log files at the location you specify using the LogPath key, where[DriverName] is the name of the driver:
- A [DriverName]_driver.log file that logs driver activity that is not specific to a connection.
- A [DriverName]_connection_[Number].log for each connection made to the database, where [Number] is a number that identifies each log file. This file logs driver activity that is specific to the connection.