Hello. > MyISAM table of about 1.8 GB it stops restoring with no error output.
It looks strange. Get the debug binary of mysql command line tool and create a trace file to find out the place where if fails. See: http://dev.mysql.com/doc/refman/5.0/en/debugging-client.html Jose Maria de Dios wrote: > I am trying to restore a backup on a two processor machine with a Debian > installation with 2.4 kernel and 2GB or RAM, but when it reaches a > MyISAM table of about 1.8 GB it stops restoring with no error output. > The MySQL version is Distrib 5.0.16. > I have tried to restore it in many other systems (unstable Debian, > Ubuntu, Windows 2000) and all of them worked fine. > Trying to figure out if the table had problems, I used myisamchk and it > returned OK. > I tried to backup and restore just this table and it restored fine. > I have tried almost everything, but the only way it worked is by > restoring the table independently. It is not an acceptable way for > backing up the database because it will grow up to a size in which it > could be very hard to backup. > The backup was created with "mysqldump --opt ..." and I try to restore > it with "mysql -u root -pPwd DB < file.sql". > > Any ideas??? > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
