List:General Discussion« Previous MessageNext Message »
From:Suporte Avanutri Date:January 26 2012 2:31pm
Subject:RES: RES: RES: Force drop table
View as plain text  
Ok. Well, I put the entire log right below:

 

 

120126 12:12:49  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

120126 12:12:49  InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 175700181.

InnoDB: Doing recovery: scanned up to log sequence number 0 175700181

120126 12:12:49  InnoDB: Started; log sequence number 0 175700181

120126 12:12:50 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

 

>>>>>>>>>>[Here I found the error and started trying to dump
> everything. Mysqld
> crashed]<<<<<<<<<<<<<<<<

 

 

120126 12:14:10  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

120126 12:14:11  InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 175700181.

InnoDB: Doing recovery: scanned up to log sequence number 0 175700181

120126 12:14:11  InnoDB: Started; log sequence number 0 175700181

120126 12:14:11 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:16:00120126 12:16:00 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:00120126 12:16:00 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

120126 12:16:02120126 12:16:02 [ERROR] Cannot find table avanutri/obras from the internal
data dictionary

of InnoDB though the .frm file for the table exists. Maybe you

have deleted and recreated InnoDB data files but have forgotten

to delete the corresponding .frm files of InnoDB tables, or you

have moved .frm files to another database?

See http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html

how you can resolve the problem.

 

>>>>>>>[At this point I deleted the table “obras.frm”.
> Still trying to dump, crashing every time, and restarting mysqld with a higher
> “innodb_force_recovery” value at a time]

 

120126 12:16:53  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

120126 12:16:53  InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 175700181.

InnoDB: Doing recovery: scanned up to log sequence number 0 175700191

120126 12:16:53  InnoDB: Started; log sequence number 0 175700191

120126 12:16:53 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:18:36  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

120126 12:18:36  InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 175700191.

InnoDB: Doing recovery: scanned up to log sequence number 0 175700201

120126 12:18:36  InnoDB: Started; log sequence number 0 175700201

InnoDB: !!! innodb_force_recovery is set to 1 !!!

120126 12:18:36 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:19:15  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

120126 12:19:15  InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 175700201.

InnoDB: Doing recovery: scanned up to log sequence number 0 175700211

120126 12:19:16  InnoDB: Started; log sequence number 0 175700211

InnoDB: !!! innodb_force_recovery is set to 1 !!!

120126 12:19:16 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:19:31 [Note] MyAvanutri: Normal shutdown

 

120126 12:19:31  InnoDB: Starting shutdown...

120126 12:19:34  InnoDB: Shutdown completed; log sequence number 0 175700211

120126 12:19:34 [Note] MyAvanutri: Shutdown complete

 

120126 12:19:40  InnoDB: Started; log sequence number 0 175700211

InnoDB: !!! innodb_force_recovery is set to 2 !!!

120126 12:19:40 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:20:20  InnoDB: Started; log sequence number 0 175700211

InnoDB: !!! innodb_force_recovery is set to 3 !!!

120126 12:20:20 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:21:05  InnoDB: Started; log sequence number 0 175700211

InnoDB: !!! innodb_force_recovery is set to 4 !!!

120126 12:21:05 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

120126 12:21:43  InnoDB: Started; log sequence number 0 175700211

InnoDB: !!! innodb_force_recovery is set to 5 !!!

120126 12:21:43 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on

InnoDB: Skipping log redo

120126 12:22:25  InnoDB: Started; log sequence number 0 0

InnoDB: !!! innodb_force_recovery is set to 6 !!!

120126 12:22:25 [Note] MyAvanutri: ready for connections.

Version: '5.0.26-community'  socket: ''  port: 3366  MySQL Community Edition (GPL)

 

Mateus Almeida

Avanutri & Nutrição Serviços e Informática Ltda ME 

CNPJ 07.775.666.0001-60  Insc. Estadual 780.532-67
Rua São José , Nº 1304

Triângulo - Três Rios, RJ

CEP 25820-150
Tel./fax: 24 2252-2468 ou 24 2252-2197

website:  <http://www.avanutri.com.br/> www.avanutri.com.br 

E-mail e MSN:  <mailto:suporte2@stripped> suporte2@stripped

Skype: suporteavanutri2

 

De: Johan De Meersman [mailto:vegivamp@stripped] 
Enviada em: quarta-feira, 25 de janeiro de 2012 11:02
Para: Suporte Avanutri
Cc: Shafi AHMED; mysql@stripped; Suresh Kuna
Assunto: Re: RES: RES: Force drop table

 

Can you send the error logs from my and Suresh' solutions, so we can see what the next
thing to go wrong is ? :-)

  _____  

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.

http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html

Thanks
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

 


Thread
Force drop tableSuporte Avanutri24 Jan
  • RE: Force drop tableShafi AHMED24 Jan
  • RES: Force drop tableSuporte Avanutri24 Jan
    • Re: RES: Force drop tableJohan De Meersman24 Jan
      • RES: RES: Force drop tableSuporte Avanutri24 Jan
        • Re: RES: Force drop tableSuresh Kuna25 Jan
          • RES: RES: Force drop tableSuporte Avanutri25 Jan
            • Re: RES: RES: Force drop tableJohan De Meersman25 Jan
              • RES: RES: RES: Force drop tableSuporte Avanutri26 Jan
                • Re: RES: RES: Force drop tableTodd Lyons26 Jan
                  • Re: RES: RES: Force drop tableJohan De Meersman26 Jan
                    • RES: RES: RES: Force drop tableSuporte Avanutri26 Jan
        • Re: RES: Force drop tableTodd Lyons25 Jan
          • Re: RES: Force drop tableTodd Lyons25 Jan