List:Internals« Previous MessageNext Message »
From:Zardosht Kasheff Date:January 22 2010 5:37pm
Subject:Re: moving InnoDB data from 5.4.2 to 5.5.1-m2
View as plain text  
I did. That is why I got this error. .\iblogfile0 was copied from 5.4.2

On Fri, Jan 22, 2010 at 11:55 AM, Mark Leith <Mark.Leith@stripped> wrote:
>
> On 22 Jan 2010, at 15:20, Zardosht Kasheff wrote:
>
>> Hello all,
>>
>> On win32, I was attempting to move my InnoDB files from a 5.4.2
>> installation to a 5.5.1 installation. I copied the data directory of
>> 5.4.2 to the data directory of 5.5.1. Upon starting mysqld of 5.5.1, I
>> saw this error:
>>
>> 100122 10:13:09 [Note] Plugin 'FEDERATED' is disabled.
>> InnoDB: The InnoDB memory heap is disabled
>> InnoDB: Mutexes and rw_locks use Windows interlocked functions
>> InnoDB: Error: log file .\ib_logfile0 is of different size 0 134217728
>> bytes
>> InnoDB: than specified in the .cnf file 0 5242880 bytes!
>> 100122 10:13:09 [ERROR] Plugin 'InnoDB' init function returned error.
>> 100122 10:13:09 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
>> failed.
>>
>>
>> What is the recommended way of moving InnoDB data from a 5.4.2
>> installation to a 5.5.1 installation?
>
>
> Try copy your ib_logfile* files as well.. :)
>
> Regards
>
> Mark
>
> --
> Mark Leith
> MySQL Regional Support Manager, Americas
> Sun Microsystems, Inc., http://www.sun.com/mysql/
>
>
>
>
>
Thread
moving InnoDB data from 5.4.2 to 5.5.1-m2Zardosht Kasheff22 Jan
  • Re: moving InnoDB data from 5.4.2 to 5.5.1-m2Mark Leith22 Jan
    • Re: moving InnoDB data from 5.4.2 to 5.5.1-m2Zardosht Kasheff22 Jan
      • Re: moving InnoDB data from 5.4.2 to 5.5.1-m2Shane Bester22 Jan
        • Re: moving InnoDB data from 5.4.2 to 5.5.1-m2Paul DuBois23 Jan