When i want to create a database connection from apache superset 2.0.0 on docker environment to vertica then i get this error
i already installed sqlalchemy-vertica-python library
my connection string is: vertica+vertica_python://user:passwd#host:port/db_name
Related
I am using the MyXQL driver with Ecto in Phoenix, and am trying to connect to an already existing MySQL database running on a Debian 11 server.
I can access the server normally using mysql -p, and can access it through Express (which is what I was using before I started migrating to Phoenix / Elixir).
When I try to run:
{ :ok, pid } = MyXQL.start_link([ username: "{username}", password: "{password}" ])
I get an error that reads:
[error] MyXQL.Connection (#PID<0.449.0>) failed to connect: ** (DBConnection.ConnectionError) (/tmp/mysql.sock) no such file or directory - :enoent
I understand that this means it can't find a /tmp/mysql.sock socket, however I cannot figure out how to fix this error, or why it even is an error, considering ExpressJS can access the server (using the npm package mysql).
When I try to connect WhereHows backend to MySQL DB in Docker environment I am getting following error message (I checked IP, Username and Password and all 3 are good):
1) Error in custom provider, Configuration error: Configuration error[Cannot connect to database [wherehows]]
At the same time, WhereHows web is connecting without any problem.
Docker version is 17.12.0-ce and I am using following images:
wherehows/backend
wherehows/web
wherehows/mysql
This is my config file - /backend-service/conf/application.conf
# connection to wherehows mysql database
db.wherehows.driver = com.mysql.jdbc.Driver
db.wherehows.url="jdbc:mysql://localhost/wherehows?useUnicode=true&characterEncoding=utf8&zeroDateTimeBehavior=convertToNull&useSSL=false"
db.wherehows.username="wherehows"
db.wherehows.password="wherehows"
My Ruby app connects to 2 databases in production: a PG database on the heroku server(successful) and a remote mysql database (unsuccessful).
The database URLs are stored in environment variables (in application.yml locally, and in config vars on Heroku).
The app is successfully retrieving data from both of these databases in development mode, so I know the URLs and credentials are valid.
On Heroku, only the pg connection is successful;
the MySQL connection throws a generic error: Mysql2::Error (Can't connect to MySQL server on 'villageprint.mypresswise.com' (110)):.
So both URLs are definitely being read from the config vars but the MYSQL connection is still unsuccessful.
Is there any reason the MySQL database might not accept the connection from Heroku? Or is it more likely that the connection is failing due to some application error? How can I debug this?
I'm trying to connect MySQL database to weblogic so that I can use it in my project, I'm very new to this, anyway, I have created a data-source, I selected MySQL as a database type > I put my database name, host: localhost, port:3306, database username, and password, driver class name: com.mysql.jdbc.Driver
when ever I test connection it gives: Cannot load driver: com.mysql.jdbc.Driver
I downloaded J-connector I have put it in:
C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\mysql
But it's not working!
What version of mysql are you using?
If it is version 8 of mysql you must update the driver in the Weblogic. In this link https://dev.mysql.com/downloads/connector/j/
luck
I'm trying to create datasource for connection pooling mysql database in Websphere Application Server.
I've set the JDBC Provider, I set the
Implementation class name : com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
my mysql driver version is 5.1.6.
but I got this error while I try to connect the datasource:
The test connection operation failed for data source btn_itb_ds on server server1 at node qnode with the following exception: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Unknown command. View JVM logs for further details.
I have read this http://bugs.mysql.com/bug.php?id=38388 trouble shooting. But they just suggest to upgrade mysql driver version 5.1.X and I have do that. but I've got the same error.