MySQL Blog Posts

MySQL Error Invalid lost+found Schema

If within a MySQL instance a schema name such as "#mysql#lost+found" or "#lost+found" is listed when the "show schemas" or “show databases” command is run, it's not a true schema but will appear when MySQL is installed in a root directory on a Linux server. At the...

read more

MySQL User With wildcard and localhost Hosts

There's often confusion over why MySQL users are created with a host of localhost in addition to a user created with wildcard, %, for their host. create user 'some_user'@'localhost' identified by 'some_password_here'; create user 'some_user'@'%' identified by...

read more

Using the Mysqlbinlog Utility

MySQL binary logging is used for replication and also for point-in-time recovery of a MySQL database instance. It records any changes to database contents and may be recorded in a "statement-based" or "row-based" format. The default location to find the binary logs is...

read more

MySQL Max Connect Errors

When connection requests to a MySQL database from a given host are interrupted, MySQL keeps track of the number of successive interruptions in the host cache. MySQL will eventually block the host, giving them a message [1129] "Host 'host_name' is blocked because of...

read more

Migrating MySQL Data to Amazon Aurora

Switching database engines—for instance, going from a MySQL-compatible database to an Amazon Aurora MySQL DB cluster—and migrating data can be a long and confusing process. For the purpose of offering a little clarity, this article will go through and highlight...

read more

ERROR 1114 – The table is full

At XTIVIA, we have encountered the MySQL Error 1114, "table is full" on quite a few occasions. The description for the error is usually misleading as it implies that a table has reached or exceeded a maximum set limitation. Tables utilizing the InnoDB storage engine...

read more

Speak with an Expert DBA now!

Call: (888) 685-3101 ext. 2 or fill out the form below