How to enable ODBC / JAVA tracing with the Connect(64) XE for ODBC Salesforce driver, Progress DataDirect for ODBC for MongoDB, Oracle Service Cloud, Google BigQuery, MSDynamics 365 drivers and Autonomous REST Connector?

How to enable ODBC / JAVA tracing with the ODBC Salesforce, MongoDB, Oracle Service Cloud, Google BigQuery, MSDynamics 365 drivers and Autonomous REST Connector?

Jul 9, 2024
Knowledge

Title

URL Name

000037182

Article Number

000160207

Environment

Product: Connect(64) XE for ODBC, Progress DataDirect for ODBC, Progress DataDirect Autonomous REST Connector Version: 7.x,8.x OS: All supported platforms Database: Salesforce, MongoDB, Oracle Service Cloud Application: All ODBC applications

Question/Problem Description

How to enable ODBC / JAVA tracing with the ODBC Salesforce, MongoDB, Oracle Service Cloud, Google BigQuery, MSDynamics 365 drivers and Autonomous REST Connector?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

Below some instructions on how to enable ODBC + JAVA tracing.

1. Locate the file "C:\Program Files (x86)\Progress\DataDirect\ODBC_80\Samples\Example\ddlogging.properties" or "/opt/ODBC_80/samples/example/ddlogging.properties"

2. Edit the property “java.util.logging.FileHandler.pattern” in that file as follows to specify where the trace file should be written:

For example to write to C:\temp or /tmp, specify the value as follows and make sure to escape any backslashes for Windows:

java.util.logging.FileHandler.pattern = C:\\temp\\ddlog%g.log or java.util.logging.FileHandler.pattern = /tmp/ddlog%.log

3. Edit the properties “java.util.logging.FileHandler.limit” and "java.util.logging.FileHandler.count" to values large enough to make sure all information is collected and Limit the messages that are printed on the console to WARNING and above:
.level= FINE
java.util.logging.ConsoleHandler.level = FINE

4. Edit the properties at the bottom of that file to specify FINEST instead of FINER / OFF.

datadirect.cloud.adapter.level = FINEST
datadirect.cloud.sql.level = FINEST
datadirect.jdbc.cloud.level = FINEST
datadirect.cloud.drivercommunication.level = FINER

5. Launch the ODBC Administrator tool or adapt the odbc.ini and configure ODBC data source to enable JAVA tracing:

If using the driver in "Direct mode (SQL Engine Mode = 0 (Direct))
- Add the file name and location of “ddlogging.properties” to the 'Log config file' property in the 'Advanced' tab of the ODBC Data Source on Windows or in the ODBC Data Source in the odbc.ini file on Unix/Linux.
Windows : C:\Program Files\Progress\DataDirect\Connect_for_ODBC_71\Samples\Example\ddlogging.properties
Unix/Linux : /opt/ODBC_80/samples/example/ddlogging.properties

If using the driver in "Server mode (SQL Engine Mode = 1 (Server))
- Copy ddlogging.properties to the location specified by the "Server DB Directory' in ODBC data source. This location is specified in the SQL Engine tab of the ODBC data source configuration.
- Rename ddlogging.properties to ddserverlogging.properties
- Restart the Progress DataDirect SQL Engine service
- The logging will be enabled at this point and will write to the "Server DB Directory" by default.

NOTE: The Server DB Directory connection option has been deprecated in Salesforce ODBC 8.0 driver. To Enable the logging in the ServerMode in Salesforce 8.0 ODBC driver use the Another option for ServerMode described below:

Another option for ServerMode
- Create a ddlogging.properties like above
- Click 'Edit Server Settings' under the SQL Engine tab in the ODBC data source
- Add the following string to the JVM Arguments -Djava.util.logging.config.file=c:\tmp\ddlogging.properties
- Click apply / OK and restart the Progress DataDirect SQL Engine service

6. Also enable general ODBC Tracing

For Windows :

under the tab 'Tracing' in the ODBC Administrator tool on Windows by following the below steps:

- Select the tab 'tracing'

- Change the name of the logfile into e.g. c:\sql.log

- Enable the check box 'Machine-wide tracing for all user identies' (only available when using ODBC Administrator 3.52 or higher)

- Click the button 'Start Tracing' (if prompted for it, confirm to enable machine-wide ODBC tracing for all user identities)

- Click the button 'Apply'

- Click the button 'OK'

For Unix/Linux :

In the odbc.ini file is a section called [ODBC].

The 'Trace' attribute enables the ODBC tracing.
The attribute 'TraceFile' specifies the directory and file name of the ODBC trace file.

In the example below, tracing is enabled and file odbctrace.out will be written to the /tmp directory.

[ODBC]
IANAAppCodePage=4
InstallDir=/opt/Progress/DataDirect/ODBC_80
Trace=1
TraceFile=/tmp/odbctrace.out
TraceDll=/opt/Progress/DataDirect/ODBC_80/lib/ddtrc27.so
#Optional trace settings
UseCursorLib=0
ODBCTraceFlush=1
ODBCTraceMaxFileSize=file_size
ODBCTraceMaxNumFiles=file_number
TraceOptions=0

6. Now reproduce the issue; and send both the ODBC Trace (sql.log) and the the JAVA logs written to the location specified in step #2.

7. After the problem has been reproduced and the logs created, don't forget to disable tracing again.

Another way to generate DDLogs/Java Logging:

Enabling Logging for Windows Service:
1. Using RegEdit navigate to the driver's services section in the registry. For example, this is the registry path for the 8.0 Dynamics driver:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Progress Software Corporation\DataDirect\Dynamics365\Services\Microsoft Dynamics 365 SQL Engine 08.00 64

2. Get the value for the DatabaseRepositoryPath. For example, Dynamics 365 has the following path:

C:\Users\stevev\AppData\Roaming\Progress\DataDirect\Microsoft Dynamics 365

3. Copy the file called ddlogging.properties in the above folder.
4. Launch the ODBC Administrator.
5. Edit the data source. This will launch the driver's configuration manager inside the browser.
6. Under the Diagnostics tab. Change "Web Service Compress Data" to 1 - None. Note this step is not necessary if you do not want to log the HTTP traffic.
7. Save the changes by clicking on Update
8. Restart the service by going to the SQL Engine tab clicking the Stop and then Start.
9. At this point, the logging should be enabled.

To Disable Logging:
1. Rename or remove the ddlogging.properties file from the database repository location.
2. Change Web Service Compress Data to 0 - Compress.
3. Restart the service again.

Workaround

Notes

Java logging can also be enabled for the JDBC drivers as well

Keyword Phrase

Last Modified Date

1/8/2026 2:37 PM

How to enable ODBC / JAVA tracing with the Connect(64) XE for ODBC Salesforce driver, Progress DataDirect for ODBC for MongoDB, Oracle Service Cloud, Google BigQuery, MSDynamics 365 drivers and Autonomous REST Connector?

Files(0)

Was this article helpful?

Was this article helpful?

How to enable ODBC / JAVA tracing with the Connect(64) XE for ODBC Salesforce driver, Progress DataDirect for ODBC for MongoDB, Oracle Service Cloud, Google BigQuery, MSDynamics 365 drivers and Autonomous REST Connector?

Information

Related Articles