I opened mysql workbench yesterday and it was working fine, but when I tried to open my database in mysql workbench and this error shows up.
I did not change anything on my computer since the last time that I used it but it said that the database was not fully compatible with the supported versions of mysql.
I think you are using XAMPP ( with MariaDB 10.1.25). its a warning ignore it, rest of all works fine
Related
I'm having problems trying to connect to databases with DBeaver. I've managed to connect to one database fine with no problems. However, any additional connections is causing issues.
I keep getting the error
SCRAM authentication is not supported by this driver. You need JDK >= 8 and pgjdbc >= 42.2.0 (not ".jre" versions)
I've tried the exact same details in pgadmin, and can get into the database just fine.
I just much prefer DBeaver as pgadmin seems to lack some really basic features like autocompletion.
I've reinstalled postgres and dbeaver multiple times, ensuring that its the latest version of each, still nothing.
Fixed the issue. It appears that DBeaver was holding on to an outdated library, which was being checked first, and therefore failing the test.
Steps to solve issue.
Download latest JDBC and move to \Program Files\DBeaver\shared_drivers
Open DBeaver and click Database -> Driver Manager
Double click on PostgreSQL
Under libraries click Add file and find the new JDBC
Delete any of the previous libraries, so it remains the only one
I'm trying to assist user who suddenly no longer is able to connect to database using PostgreSQL JDBC driver. PostgreSQL connection tab is not clickable. All of her colleagues do not have such issues. I have re-installed SQL developer several times, backed up and deleted SQL config folders from C:\users\username\appdata\roaming, re-added driver, nothing seems to change. I have limited knowledge about SQL as I don't use it and neither is there much information about this as it doesn't seem like a common issue. User uses following software:
JDK 8 -172 64 bit,
SQL Developer 17.2.0,
PostgreSQL JDBC driver 42.2.18. Added screenshot just in case. Any help would be appreciated.
Recently I installed PostgreSQL 10.4, but it was losing connection all the time. I uninstalled it, removed the data folder and installed version 9.6, which didn't help, so I uninstalled it as well and removed the data folder. I installed 10.4 again hoping that it will work well this time.
When I opened pgAdmin it showed as if version 9.6 was still installed apart form the 10.4 (which should be there). I tried creating a user in it (to see if it really works) and it created it successfully, but after further investigation I realized that it created the same user in the 10.4 installation. It must have been the same installation, but pgAdmin saw it as two separate ones. I deleted both installations form pgAdmin and reinstalled version 10.4.
Everything works fine now, but I still wanted to ask what might have caused this issue? Can it cause problems for my existing db in the future?
It's not "PostgreSQL" that remembered the installation. It's pgAdmin where you simply didn't delete the configured connection. Connection information is something specific to the SQL client, not the database server.
The existing connection definition uses the same hostname, port and apparently password that was valid for a running 9.6 server or the new Postgres 10 server. The name of that "server" is something that is specified in pgAdmin and has nothing to do with the actual Postgres installation. You could have named the "9.6 Server" connection "Connect to some nice DBMS" instead.
That information is not stored together with the PostgreSQL installation, but in your user profile.
I'm trying to move a sonarqube 4.4 installation from one machine to another. What's more we would also like to change the database server from Oracle to Postgres 9.3.
What my plan was initially is that I would shutdown the sonar server, the database adminstrator would dump existing database, migrate it to postgres in the new server and I would zip the existing server installation and move it along to the new server. Then I would start the server.
However I've run into problems, even though sonarqube 4.4 booted fine, when I hit
http://new-server:9001/sonar4
I was getting a 404 response from sonar.
At some point I tried unzipping the server file anew in which case I managed to see the projects and the dashboards but no analysis data existed, even though last analysis time was available.
Any ideas or clues what am I missing?
Also, the driver in sonarqube for postgres is 9.1.xxx can I update this or should we use postgres 9.1 to make sure the driver is compatible with the database?
How is your ..\conf\sonar.properties? Normally, you should have changed:
sonar.jdbc.url=jdbc:oracle:thin:#localhost/XE
Did you use some tool to migrate Oracle to Postgress? I thought it was not possible.
Do not hesitate to ask for further precision.
Regards.
I am using mysql 6.1 workbench and having issues every time I turn on system. I've tried atleast 50 solutions from different sources but it is not getting fixed. Tried to change default port as well re-installed it quite a few times now. Couldn't understand why it's not getting fixed.
Error is: Can't connect to MySQL server on '127.0.0.1' (10061) (2003).
I've seen official documentation in detail and followed each step.
Please help.
I figured this out...actually when WAMP and MySQL Workbench both installed only then it shows this issue. Quitting WAMP closes connection so system shuts services down and workbench fails to start service at it's own. By removing one of both won't show such errors. Problem solved.