Skip navigation links

MySQL Forums :: Backup :: Can´t restore backuped DB´s with MySQL Administrator


Advanced Search

Can´t restore backuped DB´s with MySQL Administrator
Posted by: Rudy Flagg ()
Date: December 10, 2009 06:12AM

Hi everyone.

I´ve backuped my MySQL Databases using MySQL Administrator to transport them from Windows to UNIX Server. Backup worked fine, but the restore won´t. It typically get´s the following errors:


090428 13:22:21 mysqld started
090428 13:22:21 InnoDB: Started; log sequence number 0 2444128912
/opt/mysql/bin/mysqld: ready for connections.
Version: '4.1.22-standard' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
090428 13:28:27 InnoDB: Error: Write to file ./ibdata1 failed at offset 0 1072693248.
InnoDB: 1048576 bytes should have been written, only 1048064 were written.
InnoDB: Operating system error number 0.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 0 means 'Error 0'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
090428 13:36:24 [Note] /opt/mysql/bin/mysqld: Normal shutdown

090428 13:36:26 InnoDB: Starting shutdown...
090428 13:36:28 InnoDB: Shutdown completed; log sequence number 0 2453836734
090428 13:36:28 [Note] /opt/mysql/bin/mysqld: Shutdown complete

090428 13:36:28 mysqld ended


-------------------------------

090428 13:45:04 mysqld started
090428 13:45:04 InnoDB: Started; log sequence number 0 2453836734
/opt/mysql/bin/mysqld: ready for connections.
Version: '4.1.22-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
090428 13:51:31 InnoDB: Error: Write to file ./ibdata1 failed at offset 0 1072693248.
InnoDB: 1048576 bytes should have been written, only 1048064 were written.
InnoDB: Operating system error number 0.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 0 means 'Error 0'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html


The MySQL Admin Message goes like: The server has returned this error message:Can't create table '' (errno: 135)
MySQL Error.

or table is full.


Some tables are restored if i turn off the stop on errors option, but that´s it. Drive Space is not the problem, also the file size for the UNIX System shouldnt be. Maybe someone could tell me where to look for.

thanks in advance.



Edited 1 time(s). Last edit at 12/10/2009 08:09AM by Rudy Flagg.

Options: ReplyQuote


Subject Views Written By Posted
Can´t restore backuped DB´s with MySQL Administrator 2942 Rudy Flagg 12/10/2009 06:12AM
Re: Can´t restore backuped DB´s with MySQL Administrator 1603 Rick James 12/15/2009 09:59AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.