Debugging JDBC Connectivity Issues with Aginity Pro or Premium - Step 1

Aginity Pro and Premium include the ability to copy the full JDBC connection string.

This is helpful for debugging what may be missing or required in the advanced parameter section when setting up database connections.  

As always you should start with reading through our documentation on connecting to databases.

If you are still struggling the first thing we recommend is to look at the JDBC connection string as shown below.

Screen_Shot_2019-09-05_at_10.49.58_AM.png

When you select Copy connection string to clipboard and then paste it to an editor you will see the following.

jdbc:redshift://redshift.aginity.com:5439/mart?allowMultiQueries=true;ssl=true;uid=XXX;pwd=*******;

This in coordination with your database administrator can now help you compare to the JDBC configuration guide of the database and determine what is missing.  For example, maybe your Redshift configuration requires the sslRootCert parameter to point to a specific "*.pem" file.  In this case you could add the advanced parameter as shown here and the corresponding JDBC configuration string.

Screen_Shot_2019-09-05_at_10.57.53_AM.png

jdbc:redshift://redshift.aginity.com:5439/mart?allowMultiQueries=true;ssl=true;sslRootCert=c:\sample\jeff.pem;uid=XXX;pwd=*****;

 

 

 

Was this article helpful?
0 out of 1 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.