← Back to team overview

maria-discuss team mailing list archive

Re: INNODB not loading

 

i can't access innodb  tables, only aria memory myisam

2015-12-10 22:05 GMT-02:00 Peter Mclarty <
peter.mclarty@xxxxxxxxxxxxxxxxxxxxxxx>:

> Hi Rorberto
> That log looks like your innDB has started.
> the “mysql”.”innodb_table_stats”  not found is possibly an upgrade or
> something removed or damaged that mysql table. That isn't innodb not
> starting. Have you checked you can access any tables under the innodb
> engine?
>
> Cheers
>
> Peter
>
>
>
>
>
>
> On Fri, Dec 11, 2015 at 9:56 AM, Roberto Spadim <roberto@xxxxxxxxxxxxx>
> wrote:
>
>> hi guys, i was using my database and it crashed, after restart innodb
>> (Xtradb) don't start
>>
>> the log shows this:
>>
>> 151210 21:44:38 [Note] InnoDB: Using mutexes to ref count buffer pool
>> pages
>> 151210 21:44:38 [Note] InnoDB: The InnoDB memory heap is disabled
>> 151210 21:44:38 [Note] InnoDB: Mutexes and rw_locks use GCC atomic
>> builtins
>> 151210 21:44:38 [Note] InnoDB: Memory barrier is not used
>> 151210 21:44:38 [Note] InnoDB: Compressed tables use zlib 1.2.3
>> 151210 21:44:38 [Note] InnoDB: Using CPU crc32 instructions
>> 151210 21:44:38 [Note] InnoDB: Initializing buffer pool, size = 32.0G
>> 151210 21:44:48 [Note] InnoDB: Completed initialization of buffer pool
>> 151210 21:44:54 [Note] InnoDB: Highest supported file format is Barracuda.
>> 151210 21:44:54 [Note] InnoDB: The log sequence numbers 8739254920 and
>> 8739254920 in ibdata files do not match the log sequence number
>> 98318151020 in the ib_logfiles!
>> 151210 21:44:54 [Note] InnoDB: Database was not shutdown normally!
>> 151210 21:44:54 [Note] InnoDB: Starting crash recovery.
>> 151210 21:44:54 [Note] InnoDB: Reading tablespace information from the
>> .ibd files...
>> 151210 21:44:54 [Note] InnoDB: Restoring possible half-written data pages
>> 151210 21:44:54 [Note] InnoDB: from the doublewrite buffer...
>> 151210 21:44:57 [Note] InnoDB: 128 rollback segment(s) are active.
>> 151210 21:44:57 [Note] InnoDB: Waiting for purge to start
>> 151210 21:44:57 [Note] InnoDB:  Percona XtraDB (http://www.percona.com)
>> 5.6.25-73.1 started; log sequence number 98318151020
>> 151210 21:44:57 [Note] Plugin 'FEEDBACK' is disabled.
>> 151210 21:44:57 [Note] Server socket created on IP: '::'.
>> 151210 21:44:57 [Note] Event Scheduler: Loaded 0 events
>> 2015-12-10 21:44:57 7fbfd435a700 InnoDB: Error: Table
>> "mysql"."innodb_table_stats" not found.
>> 151210 21:44:57 [Note] /opt/mariadb/bin//mysqld: ready for connections.
>> Version: '10.0.21-MariaDB-log'  socket: '/tmp/mysql.BH.sock'  port: 3307
>>  MariaDB Server
>>
>>
>> any idea what could be done to start recovery from innodb?
>>
>> --
>> Roberto Spadim
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~maria-discuss
>> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-discuss
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> *Peter McLarty*
> *Data Analyst DBA*
> Compare The Market
> P: +61 7 3377 8952
> M: +61 4 0209 4238
> http://www.comparethemarket.com.au
>
>
> Compare The Market is a brand and trading name of Compare The Market (Pty) Ltd (CTM). This email is for the intended addressee and is confidential and subject to copyright.
> If you are not the intended addressee, confidentiality has not been waived and any use, interference with, or disclosure of this email is unauthorised.
> If you are not the intended addressee please immediately notify CTM and then delete the email. CTM does not warrant that this email is error or virus free.
>
>


-- 
Roberto Spadim
SPAEmpresarial - Software ERP
Eng. Automação e Controle

Follow ups

References