Re: error 134 cause mysql to run out connections
running perror 134 shows
MySQL error code 134: Record was already deleted (or record file crashed)
Is your application trying to read deleted records?
Can you repair the table with mysqlcheck?
>mysqlcheck <dbname> <table>
The warning about the binary log file is only an issue if you have a replication slave running of this server as master, and you rename the host this master is running on.
Good luck,
Barry.
Subject
Written By
Posted
Re: error 134 cause mysql to run out connections
October 27, 2009 03:22PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.