When I try to export a DB in workbench, it tells me error as in the screenshot below:
As I understood, it wants me to downgrade MySQL, which is currently v5.7.19 came with the wampserver. But when I went to wampserver website I didn't find such MySQL version in older wampserver versions.
Also, when I check updates fro workbench, I am told it is latest version.
If the solution to this problem not by going that way, Please tell me.
In all cases, please help me to solve the problem showed in the screenshot.
That's not an error, but a generic warning Workbench shows when the server is newer than the tools it ships with. This is to let you know that some new features may not be supported. In this particular case the difference should be minimal and you can ignore the message. Alternatively, you can point MySQL Workbench to the mysqldump binary of the current server (using the application settings).
Related
It seems that an SSL connection is required to use MySQL Workbench, and I don't think this is the case with previous versions.
I remember SSL connections used to be optional. After I updated it, all options are locked to require SSL.
How do I bypass this? I'm just a student and setting up SSL is out of my reach.
Screenshot:
Here is the correct solution for version +8.0.x.
When the program starts, the edited configuration files are changed again.
Therefore, you need to add useSSL=1 in advanced.
I solved this by editing the connections.xml configuration file.
Under ~/.mysql/workbench/connections.xml, I searched for the connection name and changed
<value type="int" key="useSSL">2</value>
to
<value type="int" key="useSSL">1</value>
MySQL Workbench has released 8.0.28
It solves this bug. Wow. I am happy.
In Mac OS X there is this issue.
My version is mysql-workbench-community-8.0.27-macos-x86_64.dmg.
I have downgraded to mysql-workbench-community-8.0.26-macos-x86_64.dmg, and it has solved it.
This issue has been reported to the MySQL team. See Test Connection in Workbench fails since SSL required (Bug #105327).
In the bug report, the development team replies that this issue will be fixed in 8.0.28.
Someone may be waiting for the fix, but check for the newest version on the download page.
I found this solution on Stack Exchange and worked for me just fine on Windows 10. This is the original post: MySQL Workbench: "ssl is required but the server doesn't support it".
Look for the fehrlich's answer. I will describe it here as in the original post:
You can bring back the old SSL options in 8.0.27:
Close MySQL Workbench
Go to you MySQL Workbench install folder (p.e. C:\Program Files\MySQL\MySQL Workbench 8.0 CE)
open the file modules/data/mysql_rdbms_info.xml
replace all occurrences of
">2|Require,3|Require and Verify CA,4|Require and Verify Identity"
with ">0|No,1|If available,2|Require,3|Require and Verify CA,4|Require
and Verify Identity"
Now you have the old options back.
Original image
I don't know if it may be the right approach for you, but I downgraded my version of MySQL Workbench to 6.3 and uninstalled the previous version. It will then give you the "if available" option for SSL. As you are right, it is not the case for previous versions, however you do lose a few more modern features in the process.
MySQL Product Archives
Another solution as well is to connect to connect to the database in 6.3 and since the configuration saves are in the same location, upgrade to 8.0 where it will still have the old configuration file and won't use SSL due to backwards compatibility.
I am using MySQL server 5.6. Uninstall and install MySQL Workbench 8. It's working.
I encountered this error when I was trying to export or import database from AWS RDS. I had Mysql Workbench on my system and also had Mysql installed locally.
As none of the solution mentioned here worked for me, I went further to investigate the error. I found out that the Workbench Default Target Mysql is 8.0.15 and my natively installed version of Mysql was 5.7.24, meaning the Mysqldump tool I was using didn't support the SSL protocol.
I bumped the natively installed Mysql to 8.0.18, and pointed the dump tool to it and it worked as expected.
Hope this helps someone too.
I am trying to see the visual explain plan of my query in mysql workbench. But when I click on execution plan it shows tabular plan in default when I change the plan to Visual Plan; nothing happens and it keeps on displaying tabular plan.
I have mySQL 10 and Workbench 8.0.18.
I have surfed internet alot but found only one solution to upgrade mysql and workbench. I did but still same issue..
Can anyone suggest what is the reason behind that?
Thank you for the support, I have resolved the problem now. I was having MySQL Server 5.5 which does not support json. Thats why, Visual Explain plan was not available. Now Upgrading to 8.0 version worked things out for me..
You have to download a mysql installer and execute, and click on 'Add' and select mysql version from there. Afterwards, it will ask for configurations and you will be able to access that version in workbench after installation.
Thanks alot..
I'm installing Jira locally with the latest version (7.13 x64 version).
When doing the custom install and trying to switch to using MySQL as the database,
I get the error:
You have specified a database that is not empty, please specify an empty database.
The database is brand new, I literally just created it and if I query it I can see it has no tables created.
I created the database (and several others) using either the standard CREATE DATABASE ... or be specifying UTF-8 as well, which is how the Atlassisn docs suggest it is done.
But, no matter what I do, the same error keeps appearing. Topics on the Atlassian site mentioning this error haven't been any help and all seem to do with version conflicts which aren't relevant here.
I have installed the Java/MySQL connector version 8.0.13. Is it something to do with that?
Thanks in advance.
It was the JDBC connector that was the problem. I downloaded and installed the latest (version 8.0.13) but it was causing the error.
Installing version 5.1.47 works just fine, even though it isn't recommended for use with MySQL 5.6, which I'm using.
But, using that connector, I have a database installed and Jira is functioning as it should.
I know is so late for answer but say answer to other searcher this question
I found this error in the logs which lead me to https://jira.atlassian.com/browse/JRASERVER-67274
Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
The long and short of it is you need an older mysql-connector-java-5.1.x.jar driver instead of the latest mysql-connector-java-8.0.x.jar that the documentation would lead you to install.
Reverting my driver to mysql-connector-java-5.1.49.jar fixed the issue for me.
MySQL workbench was working properly till last login(yesterday). When I tried to open an existing connection(today), this error was popped up. I was trying to convert tables from MSSQL to MySQL yesterday.
Detailed error message
MySQL workbench has encountered a problem
Parameter is not valid
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below.
Please make sure to include a detailed description of your actions that lead to this problem.
Thanks a lot for taking the time to help us improve MySQL Workbench!
The MySQL Workbench Team
For future reference, I had the same problem out of the blue with Workbench on Windows 7 so I re-ran MySQL Workbench installer, selected Repair and everything went back to normal.
I guess some update messed up the install.
This is not about the normal login but migration in MySQL Workbench. This part uses separate logins to source and target servers. If your connection to the MS SQL server worked yesterday and you didn't change anything in MySQL Workbench then it is very likely something with your MS SQL server happened. So, someone needs to check if that server is still running properly and can be accessed from your machine.
Okay listen up. Go to your downloads where you had actually downloaded workbench setup right click on it, you will find an option called "Repair", click on it, follow all steps, open your workbench, open your connection now!(Mine is Windows 10)
Note : You can do it by re-installing workbench too! But Repairing the tool is more convenientPFA Image
when I click on a database in the "Object Browser" section of my MySQL Workbench to see its schema, I get lines that display the message "fetching...". The object browser hangs on this and the schema of the database is never displayed. I get the same error on different servers. Does anybody know how to remedy this?
I just ran into this exact same issue on OSX / XAMPP and figured out that the permissions on my MySQL config file were the ultimate culprit. See the details here.
It seems Workbench is an easy to hang app. Try testing your connections from a console.
Thanks bmoeskau for your answer. The 'fetching' message actually disappeared a couple of weeks after I posted this question after I installed a new version of Workbench. I am not sure what version of Workbench is included in the XAMPP stack, but the Workbench included in this package is usually not the latest release.