-
Attempting to make a connection to a redshift instance with the standard redshift driver gives the following error:
Other databases seem to work fine. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
Please post the error stacktrace (you can get it in Error Log view) |
Beta Was this translation helpful? Give feedback.
-
I don't see any errors in the error log. This issue occurs when I attempt to connect to redshift. |
Beta Was this translation helpful? Give feedback.
-
What driver (exact version) do you use? |
Beta Was this translation helpful? Give feedback.
-
@BaronWR did you ever find a solution to this? I'm having the same problem |
Beta Was this translation helpful? Give feedback.
-
@BaronWR @WillSidebottom In case you are still having issues, I think that you may have made the same mistake I initially did when following the Amazon Redshift Getting Started directions step 5. It says to grab the JDBC URL and copy it into your connection settings. If you just grab the URL, which looks like this:
it includes the You need to take both of those out of your URL because DBeaver connection dialog adds them in. Basically verify that the read-only DBeaver "JDBC URL" matches the Redshift "JDBC URL" at the end of the day because it's easy to mess up. |
Beta Was this translation helpful? Give feedback.
-
Thanks Urbushey, |
Beta Was this translation helpful? Give feedback.
-
Thanks Urbushey... worked like a wonder !! :) |
Beta Was this translation helpful? Give feedback.
@BaronWR @WillSidebottom In case you are still having issues, I think that you may have made the same mistake I initially did when following the Amazon Redshift Getting Started directions step 5.
It says to grab the JDBC URL and copy it into your connection settings. If you just grab the URL, which looks like this:
jdbc:redshift://xxx.xx.us-east-1.redshift.amazonaws.com:5439/dev
it includes the
jdbc:redshift://
as well as:5439/dev
bit.You need to take both of those out of your URL because DBeaver connection dialog adds them in. Basically verify that the read-only DBeaver "JDBC URL" matches the Redshift "JDBC URL" at the end of the day because it's easy to mess up.