Get error when connecting to Amazon Redshift
7 January, 2014
I am attempting to connect to an Amazon Redshift database from Yellowfin. I can connect with my sql tools and with Excel using ODBC from this same machine. However when I attempt to create a new data source using the
org.postgresql.Drive, I get the following error:
java.net.SocketException: Permission denied: connect
Is there something I'm missing?
Thanks,
Clayton
org.postgresql.Drive, I get the following error:
java.net.SocketException: Permission denied: connect
Is there something I'm missing?
Thanks,
Clayton
I switched from postgresql-9.1-901.jdbc3.jar to postgresql-8.4-703.jdbc4.jar and not it works.
.. and NOW it works.
Hi Clayton,
that's great news, and thanks very much for posting your findings here as it will no doubt help someone else one day!
regards,
Dave
that's great news, and thanks very much for posting your findings here as it will no doubt help someone else one day!
regards,
Dave
THE REPLY BELOW HAS BEEN MOVED TO HERE : http://www.yellowfinbi.com/YFForum-Redshift-error-on-saving-data-source-?thread=160255#p1 .
THIS REPLY WILL BE REMOVED IN THE COMING DAYS
Hi, I had a similar problem to Clayton with Redshift. I changed the driver to 8.4, and now instead of no connection, I get a successful test (listing driver version 8.4) and my tables list.
However, when I save the data source, I get the following error in my Yellowfin log:
[quote="">
YF:2014-04-16 05:01:56:ERROR (StdGetSequence:getNextSequence) - Error occured getting sequence Nbr: User does not have access to metadata required to determine stored procedure parameter types. If rights can not be granted, configure connection with "noAccessToProcedureBodies=true" to have driver generate parameters that represent INOUT strings irregardless of actual parameter types.
YF:2014-04-16 05:01:56:ERROR (MIAdminProcess:saveDataSource) - Error: java.lang.Exception: Database error obtaining sequence number
[/quote]
I think noAccessToProcedureBodies is a MySQL connection string parameter. Anyway I tried adding it to the connection string, but same error.
I'm using the Redshift superuser (for testing) and I also select the Public schema before saving it, so the user should have all necessary permissions.
I get this same error whether I use the full connection string with the generic Postgres 8.4 driver, or when I select the Amazon Redshift database source.
Any ideas? Thanks!
THIS REPLY WILL BE REMOVED IN THE COMING DAYS
Hi, I had a similar problem to Clayton with Redshift. I changed the driver to 8.4, and now instead of no connection, I get a successful test (listing driver version 8.4) and my tables list.
However, when I save the data source, I get the following error in my Yellowfin log:
[quote="">
YF:2014-04-16 05:01:56:ERROR (StdGetSequence:getNextSequence) - Error occured getting sequence Nbr: User does not have access to metadata required to determine stored procedure parameter types. If rights can not be granted, configure connection with "noAccessToProcedureBodies=true" to have driver generate parameters that represent INOUT strings irregardless of actual parameter types.
YF:2014-04-16 05:01:56:ERROR (MIAdminProcess:saveDataSource) - Error: java.lang.Exception: Database error obtaining sequence number
[/quote]
I think noAccessToProcedureBodies is a MySQL connection string parameter. Anyway I tried adding it to the connection string, but same error.
I'm using the Redshift superuser (for testing) and I also select the Public schema before saving it, so the user should have all necessary permissions.
I get this same error whether I use the full connection string with the generic Postgres 8.4 driver, or when I select the Amazon Redshift database source.
Any ideas? Thanks!