[TYPO3-english] Best practice migrating mysql 4.1.x -> 5.0.x with mixed innodb myisam tables

[Götz Reinicke - IT-Koordinator]

Am 10.01.11 13:21, schrieb Bjoern Pedersen:
> Am 10.01.2011 11:35, schrieb Götz Reinicke - IT-Koordinator:
>> Hi,
>>
>> the dump contains 'CREATE TABLE xxx (.... ) ENGINE=InnoDB'
>>
>> I did not set a special path on both servers. All ibdata and logfiel are
>> in the same directory.
>>
>> But I do use differet config options in the old and new my.cnf file.
>>
>> Some are defaults.
>>
>> old server:
>> innodb_buffer_pool_size=920M
>>
>> new server:
>> innodb_data_file_path = ibdata1:30M:autoextend
>> innodb_flush_log_at_trx_commit=1
>>
>> Regards. Götz
>>
> So the problem really is a MYSQL problem. Can you create InnoDB-tables
> at all?

Hey,

thanks for your suggestions. Indeed I had a problem with the innodb
engine. It was disabled because of some 'we copy innodb files from
filesystem to filesystem' mismatch (I think). Removing the unused files
and generating new ones and importing my dump worked.

Thanks for pointing to in the right direction :-)

	cheers . Götz

-- 
Götz Reinicke
IT-Koordinator

Tel. +49 7141 969 420
Fax  +49 7141 969 55 420
E-Mail goetz.reinicke at filmakademie.de

Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016
Vorsitzende des Aufsichtsrats:
Prof. Dr. Claudia Hübner

Geschäftsführer:
Prof. Thomas Schadt