Enabling Debug Record Mode
- Last Updated: November 25, 2025
- 1 minute read
- DataDirect Connectors
- JDBC
- Aha! 6.0
- Amazon Redshift 6.0
- Apache Cassandra 6.0
- Apache Hive 6.0
- Apache Spark SQL 6.0
- Atlassian Jira 6.0
- Autonomous REST Connector 6.0
- Cloudera Impala 5.1
- + 24
The Autonomous REST Connector and Google Analytics 4 drivers support a debug record mode that provides a method for troubleshooting issues that occur when accessing data on a REST service. When Debug Record Mode is enabled, the driver captures and records server requests and responses to a set of files stored in a designated location. Technical Support can then use these files to analyze and reproduce the issue without requiring access to your private data source.
To generate debug record files:
- Using the DebugRecord property, specify the location where the driver will generate the files used to record server requests and responses.
- Start the JDBC application and reproduce the issue.
- Stop the application.
Note: When
deploying that Autonomous REST Connector in a SaaS application, the Composer provides a
dedicated Diagnostics tab to manage debug recording. See Diagnostic recording in the Autonomous REST Composer for details.
The driver generates a
set of files containing the server requests and responses that occurred during the session.
After generating the debug files, you can remove the location specified for the DebugRecord
property. If you do not remove this value, the driver will overwrite debug files in the
specified location the next time you start the application.Contact Technical Support for assistance analyzing the files and
reproducing the issue.
Important: Debug record files may capture
security-related headers, such as auth or token headers. Before sending Technical Support
debug files, review the content to remove any confidential information that may have been
recorded.