Can you send the error logs from my and Suresh' solutions, so we can see what the next
thing to go wrong is ? :-)
----- Original Message -----
> From: "Suporte Avanutri" <suporte2@stripped>
> To: "Suresh Kuna" <sureshkumarilu@stripped>
> Cc: "Johan De Meersman" <vegivamp@stripped>, "Shafi AHMED"
> <shafi.ahmed@stripped>, mysql@stripped
> Sent: Wednesday, 25 January, 2012 1:33:54 PM
> Subject: RES: RES: Force drop table
> No good news until now... I’m starting to think that I will not
> recover it.
> When all these tips doesn’t work, should I presume that my database
> is dead?
> De: Suresh Kuna [mailto:sureshkumarilu@stripped]
> Enviada em: quarta-feira, 25 de janeiro de 2012 02:10
> Para: Suporte Avanutri
> Cc: Johan De Meersman; Shafi AHMED; mysql@stripped
> Assunto: Re: RES: Force drop table
> Enable the option innodb_force_recovery =1 in my.cnf file, restart
> the database, ( can try upto 4 depending on the description below
> url ) and take the dump of all the innodb tables, remove the ibdata
> and data file belongs to innodb and re-import. It should be fine.
> Suresh Kuna
> 2012/1/24 Suporte Avanutri < suporte2@stripped >
> I've tried this before, but the server stills going down. The first
> error is always this:
> Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */* FROM 'usuario':
> Lost connection to MySQL server during query (2013)
> This is followed by other similar errors: "couldn't execute one
> thing", couldn't execute another thing, etc".
> I've got the error while trying to execute this: mysqldump -u USER
> -pPASS --force --databases DATABASE (and tried --all-databases too).
> Thanks in advance for the help, guys. I'm starting to learn this
> thing by myself, your help has great value to me.
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel