[cgmchris]

Deleting the database emailassault-com.old resolved the problem. I must have incorrectly created that database via a file copy.

So, example of what NOT to do:

cd /var/lib/mysql

cp -rfv [database_name] [database_name].old

/etc/init.d/mysqld restart

[cgmchris]

Upon further investigation, this is a mysql issue. When running “mysql_upgrade” I get the following output:

/usr/bin/mysqlcheck: Got error: 1102: Incorrect database name 'emailassault-com.

old' when selecting the database

Error executing '/usr/bin/mysqlcheck –defaults-extra-file=/var/lib/mysql/upgrad

e_defaults –check-upgrade –all-databases –auto-repair –user=root'

Any advice would still be much appreciated. Thanks!

[cgmchris]

I recently became the admin for this server. I have been informed that the mysql database files themselves were copied into /var/lib/mysql from backups, so if the old server had an older version of mysql that would explain the version change. However, in the last stable release, v5.19, SQLyog does NOT crash. This is a new problem with the beta release only.

Here is the information you requested:

SELECT version();

5.0.16-standard-log

SHOW columns FROM mysql.user;

Host char(60) NO PRI

User char(16) NO PRI

Password char(16) NO

Select_priv enum('N','Y') NO N

Insert_priv enum('N','Y') NO N

Update_priv enum('N','Y') NO N

Delete_priv enum('N','Y') NO N

Create_priv enum('N','Y') NO N

Drop_priv enum('N','Y') NO N

Reload_priv enum('N','Y') NO N

Shutdown_priv enum('N','Y') NO N

Process_priv enum('N','Y') NO N

File_priv enum('N','Y') NO N

Grant_priv enum('N','Y') NO N

References_priv enum('N','Y') NO N

Index_priv enum('N','Y') NO N

Alter_priv enum('N','Y') NO N

[cgmchris]

Thanks. This issue seems to be resolved in the beta version, however I immediately noticed a few unrelated bugs that I will report in a seperate thread. Thanks again.

[Author]

Posts