I'm trying to set the lower_case_table_name value to 2, since it is a Windows server. But when I start MySQL Workbench and connect to my server I get the following error:
A server is in a system that does not properly support the selected lower_case_table_names option value.
Shouldn't a Windows server support a value of 2? I'm running MySQL 5.6 on Windows Server 2012 and using MySQL Workbench 6.3.
You can safely ignore this error.
I recently installed MySQL on a new Windows computer and got this error as well after setting lower_case_table_names to 2. I don't remember seeing it previously. However, despite the error it seems to be working properly..tables are created with the proper case and I can do case-insensitive lookups.
Changing the value to lower_case_table_names = 1 prevents the warning. The windows default is 1. For the setting of this variable see:
https://dev.mysql.com/doc/refman/8.0/en/identifier-case-sensitivity.html
Related
I have a mysql 8.0.3 database over top of that maxscale server is running when i tried to connect with that mysql jdbc driver this error is coming unknown system variable 'query_cache_size'. But when i tried to connect directly to database is working for me. query_cache_size parameters removed from mysql 8.
The query cache has been deprecated. BTW 8.0.3 is a very old version (4 years) and was pre-general availability (a release candidate) so please do not use it for production.
Edit: With MXS-2890 fixed, you should now be able to configure version_string=8.0.16-mysql in MaxScale to solve this problem
This is most likely caused by the following bug: https://jira.mariadb.org/browse/MXS-2890
The MariaDB JDBC connector should not suffer from this problem which means installing it instead of the MySQL JDBC connector can be used as a workaround.
In your /etc/maxscale.cnf you can add version_string=5.6
[Read-Write-Service]
type=service
router=readwritesplit
servers=master
version_string=5.6
user=user
password=********```
after that i am able to access mysql8 on top of maxscale server.
I've installed XAMPP and am running the built in SQL server, but for some reason whenever I try to test the connection of the XAMPP default (test) database through PhpStorm it comes up with an error message of:
The specified database user/password combination is rejected: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'GMT Summer Time' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone.
I haven't changed any settings in phpMyAdmin in XAMPP or anything i've left all settings as default. I followed some video tutorials on YouTube and they didn't get this error.
I can create databases and tables fine in phpMyAdmin with no username or password so i'm not sure what the issue is.
Any help will be appreciated
That's a known problem with latest JDBC drivers, see: https://youtrack.jetbrains.com/issue/DBE-7727. Workarounds:
In DataSource configuration window go to Advanced tab and set serverTimezone property to UTC.
Switch DataSource driver to MySQL Connector/J for 5.1 (my version is 5.1.46)
I recently setup a new AWS server to be used as a web server for some small utility apps. It's running Windows 2012. I then:
Installed Chrome
Installed Lucee 5.2.7.63 using installer
Installed MySQL 8.0.11 Community Edition using installer
Installed MySQL Workbench
Created a new schema via MySQL Workbench (which connects to MySQL just fine)
Created a datasource in Lucee server administrator which fails verification with:
Could not create connection to database server.
I tried using both a Lucee specific user, and the root user, and neither worked. When I checked the Lucee error log I saw this occur several times, once for each verification attempt:
Wed Jul 18 19:52:08 UTC 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
My guess is that I either need to force Lucee to use SSL, or force MySQL to allow a non SSL connection. Unfortunately, the Lucee administrator has no option related to SSL and doesn't allow me to modify the connect string manually. And I'm unsure how to alter settings for MySQL as I can't seem to find a my.ini file anymore.
The last time I setup a server was with MySQL 5.7 and I had no problems from start to finish, so I assume this must be a MySQL 5.8+ issue, but that is contradicted by the error message.
Update
In the end I decided to uninstall MySQL 8 and install MySQL 5.7. It was difficult to download the installer for 5.7 (I got 8 again the first time for some reason), and then there was a conflict with the MySQL installer, that didn't want to recognize the 5.7 I downloaded, but after getting through it all Lucee began connecting immediately with no problem.
I would still be interested in a solution, though, so that I can use MySQL 8 in the future.
You could try defining the datasource in your Application.cfc which will give you more control over the connection parameters. For example:
this.datasource = {
database: "mydatabase"
,type: "mysql"
,host: "hostname"
,port: 3306
,username: "myusername"
,password: "encryptedpassword"
,custom: {
useSSL: false
,useUnicode: true
,characterEncoding: "UTF-8"
}
};
I work with Eclipse and I want to use the version 7 of Liferay but when I run my Tomcat server I have an error with MySQL.
Please upgrade to at least MySQL 5.6.4. The portal no longer supports older versions of MySQL
Like this the problem is pretty obvious but my SQL version is already 5.7.19
I have check my driver of MySQL in preference->data management->connectivity->driver definition and my MySQL JDBC Driver is 5.1
I want to know if someone already had this issue and know how to fix it
This is how the version gets validated, and this is how the version string gets constructed. I'd say: Please make extra extra extra sure that you are addressing the mysql server that you intend to address:
You can check your mysql version from the mysql command line client by executing select version();. Get your credentials and database URL from Liferay's portal-ext.properties or your appserver's connection pool configuration, depending on where you configured it.
Our MySQL error log contains several thousands of the following Warning: Client failed to provide its character set. 'utf8' will be used as client character set.
We're using MySQL 5.6.14 CE Server on Windows Server 2012. I can't figure out how to get the warning to go away.
I've tried updating the ODBC DSN to use a specific character set, tried setting the charset in the connection string, and tried setting numerous variables in my.ini, and restarted the database. Nothing seems to work.
I updated the connector for our websites to the latest version and this warning has stopped appearing. I'm just going to go out on a limb and guess that the 1.10.1.0 version of MySQL Connector/.Net was not passing the charset variable I had placed in our connection strings.
Still curious why --log-warnings=0 parameter prevents the MySQL service from starting, and why log-warnings=0 in the my.ini did not stop the warning from showing up in the error log, but I guess that is another question.