Teradata Workflow not executing - JDBC Driver Issue?

#1

We are doing a POC with Knime server and a workflow that works fine locally fails when executing on server.

Here is the line from preferences.epf on the server side:

/instance/org.knime.workbench.core/database_drivers=F\:\\TeradataToolsAndUtilitiesBase__windows_indep.16.20.10.00\\TeradataToolsAndUtilitiesBase\\TeraJDBC

How can we confirm if the server is correctly seeing these drivers?

This workflow works locally, but when testing on server it gives these errors:

`Error occurred while loading workflow into memory: An error occurred during the creation of a job for ‘/02 Dev/Healthcare Economics/TestWorkflow-TD Create Table’: Errors loading workflow ‘TestWorkflow-TD Create Table’: Status: Error: TestWorkflow-TD Create Table 0 loaded with errors
Status: Error: TestWorkflow-TD Create Table 0
Status: Error: DB Connector (Labs) 0:1
Status: Error: Loading model settings failed: Could not find the [Teradata] database driver.

Error occurred while loading workflow into memory: An error occurred during the creation of a job for ‘/02 Dev/Healthcare Economics/TestWorkflow-TD Create Table’: Errors loading workflow ‘TestWorkflow-TD Create Table’: Status: Error: TestWorkflow-TD Create Table 0 loaded with errors
Status: Error: TestWorkflow-TD Create Table 0
Status: Error: DB Connector (Labs) 0:1
Status: Error: Loading model settings failed: Could not find the [Teradata] database driver.

An error occurred during the creation of a job for ‘/02 Dev/Healthcare Economics/TestWorkflow-TD Create Table’: Errors loading workflow ‘TestWorkflow-TD Create Table’: Status: Error: TestWorkflow-TD Create Table 0 loaded with errors
Status: Error: TestWorkflow-TD Create Table 0
Status: Error: DB Connector (Labs) 0:1
Status: Error: Loading model settings failed: Could not find the [Teradata] database driver.`

0 Likes

#2

Hi Austin,

I think that there are three possibilities.

  1. Either the path to the driver is wrong (the \ after F: looks a little suspicious.
  2. Permissions on the driver are not granted for the user running the KNIME Server Executor process (knime.exe).
  3. The F: drive isn’t mounted for the user running the KNIME Server Executor process (knime.exe). In that case you’ll need to either switch the driver to e.g. C: or make sure that the drive is mounted for the KNIME Server process owner.

Best,

Jon

1 Like

#3

It turns out that KNIME client and server compatibility is very finicky. If the client is setup EXACTLY the same as the server, it fails. Even if a single description character has a different case sensitivity between client and server configuration it fails. We finally gave up on trying to manually configure them to match and used the server configuration push down feature. That seems to have resolved the issue.

0 Likes

#4

Thanks for following up, good to hear that using the server managed preferences works for you!

Cheers,
Roland

0 Likes