I'm moving from MySql to MariaDB and I have several databases using federated tables. Everything works fine in the MariaDB but when the server restarts, all federated tables stop working as if the remote server's entry doesn't exists on the local MariaDB server.
After every restart the servers' entries remain in the servers table in the mysql db. If I try to add them again with the CREATE SERVER command, I get an error as if they exist. If I try to drop them with DROP SERVER, I get an error as if they don't exist.
The only way to make it work again is to manually remove the entries from the server table with DELETE FROM servers and create them again with the command CREATE SERVER. How can I make those configurations persistent?
I've searched extensible and couldn't find any solution or mention about this issue. The tables work fine in MySql. The logs doesn't mention anything related to the FederatedX engine between restarts. I'm using MariaDB 10.3.18 on CentOS 7.
I just found that this issue only occurs if the servers table is using the InnoDB engine. Changing it to MyISAM or Aria solves the problem.
For some reason my server was installed with the wrong engine for this table.
Edit: bug report here.
I am new to using MySQL and I needed to download it for school, however, I keep getting this error message (picture below). I am using xampp and connecting using the username root. the port also matches what it is telling me. It will let me proceed but a lot of the features are missing. Any help at all would be appreciated.
Incompatible/nonstandard server version or connection protocol
detected (10.0.10).
A connection to this database can be established but some MySQL
Workbench features may not work properly since the database is not
fully compatible with the supported versions of MySQL.
MySQL Workbench is developed and tested for MySQL Server versions 5.1,
5.5, 5.6 and 5.7
As I can see, You are using latest XAMPP.
All you need to do is, after opening MySQL Workbench, and instead of setting up a new connection, Press CTRL+R or click on DATABASE tab in the top menu. Select Reverse Engineer and provide necessary information. You are good to go now.
The MySql workbench wont crash or show any compatibility issue now.
The current version of XAMPP uses MariaDB instead of MySQL.
Because MySQL Workbench is designed to work with MySQL and not with the very similar drop in replacement MariaDB, you are gonna have problems ...
So, if you want to use MySQL Workbench with XAMPP then a solution would be to try installing the last version of XAMPP that uses MySQL. That version is probably 1.8.3 from (August of 2014?). You can download it here:
XAMPP Sourceforge old versions
If you are using the latest XAMPP that uses MariaDB, in that case in your MySQL Workbench don't use 'Connect to Database' instead use 'Reverse Engineer' and provide the necessary credentials. That's all, No hassle.
I encounter the same message followed by a crash of MySQL Workbench, with version 6.3.7 (build 1199).
I didn't find a solution, but here is a work-around:
Once you press the button Continue anyway, just open a database use toto, and then wait a bit (a minute is enough in my case), and then you can call a query without a crash. I found this trick here.
I experimented the same with WAMP 3.2.0.
MariaDB was configured to listen to port 3306 (the usal MySQL port) and MySQL 8 was listening on port 3308. If you are in this case, don't be fooled by the fact you have 2 DBs.
To solve this, you have to choose the DB you want. I wanted MySQL and I just ask MySQLWorkBench to open a connection on port 3308 to MySQL.
You can ditch MySQL Workbench, and use the browser made for the MariaDB, they have a free version here: https://www.upscene.com/downloads/dbw
It's limited in its abilities, but I had no troubles connecting and browsing.
I had the similar problem because i was using Denwer at the same time.
To solve the problem:
Stop Denwer
Restart MySQL server
Profit! Now you can open your database in the Workbench
The idea is that denwer was starting its local server which didnt allow MySQL to start normally.
If you want to use denwer at the same time wth MySQL you can just start it after MySQL (Point 4).
In my case I already had MySql server and workbench installed and setup prior to my XAMPP installation. I wanted to continue with my existing setup.
I also installed MySql server with my XAMPP. I started mysql inside XAMPP and when I connected to MySql Workbench, I encountered the same error. Because Workbench was trying to connect with the server which was installed with XAMPP, apparently this was incompatible.
So I stopped mysql in XAMPP and started started mysql server manually(the previous setup and installed server).
Refer this to know how to start mysql manually in windows.
You can also config XAMPP to use your existing SqlServer.
So I had the same problem. For me none of the methods worked, but then I found out that my MariaDB was occupying the same port, so I uninstalled it and that solved the problem.
i had same issue, i changed the mysql server port from 3306 to 3308 in XAMPP config file.
[mysqld]
port=3308
I got the solution for joomla 3 installation problem(installation stucks in creating databases) in stackoverflow.
The solution that to replace "ENGINE=innoDB" with "ENGINE=MyIsam"
in
joomla-folder\installation\sql\mysql\joomla.sql, it works well.
Anyone know the reason why innoDB is not working with joomla 3 installation.
And do I need to restore the engine from "MyIsam" to "innoDB" again(after installed successfully)?
It is because MyIsam is supported and compatible more with Joomla. You can check here
And do I need to change the engine to "innoDB" again(after installed
successfully)
If you have changed it while installing it then there is no need to change it again.
I am currently running Pphpmyadmin 3.3.2 on Ubuntu 10.04 with Mysql 5.1.41 and I want to create an Innodb table. However, I can't find the option in Phpmyadmin and using "engine=innodb" in a "Create Table"-query results in the creation of a Mylsam table.
After looking up the problem on google, I found several posts saying that I need to search for "skip innodb" in my config file and remove it, but I could not find it anywhere.
I use the default config for Mysql and Phpmyadmin.
Any suggestions?
Thanks
I am planning an upgrade of some MySQL servers (5.1 to 5.5). I am aware that the InnoDB plugin is now built in to MySQL.
Currently we use the InnoDB plugin...
When upgrading to 5.5, is it just a case of removing the relevant lines in my.ini that load the plugin before restarting the server, or is there something I need to do (or should be doing) to the databases and tables in addition to this to take account of the change?
Will the tables just "pick up" the change to the storage engine, or do they need to be converted in some way.
I don't intend on doing a dump and reload of the tables as there are many large databases and this would be a bit of a pain!
Hope this all makes sense!
thanks!
Remove or comment out the plugin options in my.cnf or my.ini file.
Upgrade MySQL.
Run mysql_upgrade script which does the following.
mysqlcheck --all-databases --check-upgrade --auto-repair
mysql < fix_priv_tables
mysqlcheck --all-databases --check-upgrade --fix-db-names --fix-table-names
MySQL Manual recommends doing the dump and reload instead of running mysql_upgrade script as it is a safer way to upgrade.
Review MySQL documentation for all details on upgrade steps and gotchas along the way.