Hello.
Have you stopped MySQL server before executing myisamchk?
sirisha gnvg [EMAIL PROTECTED] wrote:
[-- text/plain, encoding 8bit, charset: iso-8859-1, 21 lines --]
hello everybody,
I used myisamchk /path/to/datadir/mysql/*.* to find memory already in
use and free
hello everybody,
I used myisamchk /path/to/datadir/mysql/*.* to find memory already in
use and free memory available for all tables in 'mysql' database.where mysql in
above path refers to mysql database.
I got two types of errors for all tables in that directory.
They are
I recently upgraded our database from 3.22.32 to 3.23.32
We run a ISAM check every night, to check for db problems. Ever since I did
the change, I get a email from the cron daemon like this:
/usr/bin/myisamchk: MyISAM file /var/lib/mysql/cayn21/customers.MYI
/usr/bin/myisamchk: warning: 1
Don Bowyer wrote:
I recently upgraded our database from 3.22.32 to 3.23.32
We run a ISAM check every night, to check for db problems. Ever since I did
the change, I get a email from the cron daemon like this:
/usr/bin/myisamchk: MyISAM file /var/lib/mysql/cayn21/customers.MYI
In the last episode (Mar 07), Don Bowyer said:
I recently upgraded our database from 3.22.32 to 3.23.32 We run a
ISAM check every night, to check for db problems. Ever since I did
the change, I get a email from the cron daemon like this:
/usr/bin/myisamchk: MyISAM file
The reason we run the check scripts is because in the past we had all sorts
of trouble not with the daemon crashing, but with clients (who have no
technical skills) using Access ODBC to update tables, and somehow
corrupting them. This way we catch the problems before the client does.
Thanks
