Louis_Frolio
Databricks Employee
Databricks Employee

Greetings Fuzail,  here are some suggestions you might want to consider:

 

The error you're encountering, "Configuration AutoCommit is not available," when using the Databricks JDBC connector in DataStage 11.7 suggests a misalignment with the auto-commit settings.

Analysis and Recommendations:

  1. Auto-Commit Behavior in Databricks JDBC Driver:
    • The Databricks JDBC driver operates with auto-commit mode enabled by default. This means that manual commit operations are generally not supported, as indicated by related error messages like "Cannot use commit while connection is in auto-commit mode" from similar issues.
  2. Resolution Steps:
    • Ensure that the DataStage JDBC properties explicitly set the AutoCommit parameter to true in its connection settings to align with the Databricks JDBC driver's behavior. This adjustment should prevent the connector from attempting manual commits, which are not supported.
    • Refer to the DataStage and Databricks configuration documentation to locate where these connection properties can be explicitly defined, such as in the configuration wizard or JDBC connection string.
  3. Additional Debugging:
    • If the error persists, verify that the latest Databricks JDBC driver version is being used, as updates might include fixes for such compatibility issues. The latest versions are recommended for addressing known problems.
    • Cross-check the logs to identify whether any test queries fired by DataStage during connection initiation might conflict with the driver's auto-commit behavior.
  4. Documentation:
    • See the Databricks JDBC Driver Installation and Configuration Guide for further insights on how the driver handles transaction-related operations and auto-commit settings.
Making these adjustments should help resolve the auto-commit configuration error. 
 
Cheers, Big Roux.

View solution in original post