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.
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 teach a class where we are working with Hibernate to generate the Java classes associated with our MySQL DB. Some of my students are having this issue when creating the reverse engineering file:
Could not get list of suggested identity strategies from database.
Probably a JDBC driver problem.
When we create the configuration file, Eclipse is able to ping with the DB, so I don't think the issue has to do with the versions. We are using the latest connector (8.0.22) and the latest version of Hibernate (5.4) while our MySQL version is 8.0.19. We have tried to downgrade the connector but the error still persists.
Is there any way of checking a detailed log with the error? This error is vague enough that I don't know where to check any more information, I still don't know if it has to do with versions, or it can be a JDBC issue.
I am able to successfully get through the "Add New Data Source" steps in my C# project in Visual Studio, and get a connection to my MySQL database. However, when I then try to proceed (Note: AFTER it says my connection was successful, and I am able to select my Database name from the dropdown), I get this:
Researching this, it seems the usual suggestion is to re-download the ADO.NET Driver for MySQL (Connector/NET), which I did -- I downloaded and installed mysql-connector-net-8.0.21.msi. But I still get the same problem/error message.
Is it that I need to add one or more of the References depicted below to my project first?
If not, what am I missing to configure my project so that I can access the MySql database from my Visual Studio app?
UPDATE
This doesn't answer my question, so I won't do that, but I was able to solve my real problem, which was getting a connection to the database and inserting records into it.
I still get the same err msg I complain about above, but I guess it doesn't matter because, as I said, I successfully updated the database.
Here's how that happened:
While waiting for an answer to my question, I continued doing what I could. I found some code for inserting records using C# into MySql and added it to my code. Intellisense saw that I needed to install the MySql package:
...so I had it do just that. It automatically also added the necessary uses clause for me while it was at it.
All's well that ends swell.
To work with a MySql database you need to have a reference to the appropriate ADO driver. This driver known as MySql/Connector could be downloaded from the MySql site, or you can simply use the NuGet Package Manager right-clicking on your references node and then search for MySql.Data package.
After installing it into your project you should still add a using MySql.Data.MySqlClient; in all files when you interact with this library.
I work on Django using VS Code with MySQL database
i had to install mysqlclient to connect with my database
Try installing mysqlclient on terminal with command pip install mysqlclient on the directory you are working.
I'm using HeidiSQL to edit a MYSQL database, and it's asking which library I want to use for the edits:
libmysql-6.1.dll
libmysql.dll
How do I know which one to use?
These alternative libmysql*.dll and libmariadb*.dll libraries are there to solve (SSL) connectivity issues on newer MySQL and MariaDB servers. For example on MySQL 5.7, some users reported the following error with the older libmysql.dll:
ASN: bad other signature confirmation
Using libmariadb.dll may cause another error:
Unknown SSL error (0x80090308)
Especially when you provide a SSL certificate, you may run into such issues.
For this and any other connectivity issue, HeidiSQL provides alternative libraries the user can try. Apart from that, I never heard of any other advantage or disadvantage of one or another of these libraries.
While the question of which library to use for MariaDB seems pretty obvious (libmariadb.dll), what to make of the other two?
As a clue, I looked a the file properties.
libmysql.dll shows ProductVersion 5.6.6.0
libmysql-6.1.dll shows ProductVersion 6.1.11.0
Given that these files are included in HeidiSql v11.3, I concluded they are NOT generated by building HeidiSql. So, where did those version numbers come from?
Poking around in C:\Program Files\MySQL\MySQL Server 8.0\lib, I see a libmysql.dll there too (ProductVersion 8.0.25).
So, my guess is that HeidiSql acquired those files from builds of MySQL. And the newer one (libmysql-6.1.dll) is probably the better bet for current releases of MySQL.
That does leave open the question of where the number "6.1" came from. It doesn't appear there was ever a 6.1 release of MySQL?
And it also doesn't address which one is best for MSSQL, PostgreSQL, etc. But that wasn't the question here.
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).