Hi,
I'm trying to move my 5x site to my localhost. (without this I can't run a simulation for 5x => 6x upgrade)
Because the database is pretty large (12mb gzipped and 144 tables), I have to load the file exported through Backup_Migrate module twice. PhpMyAdmin then keeps giving me the same Error:
Error
SQL query:
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
MySQL said:
#1231 - Variable 'sql_mode' can't be set to the value of 'NULL'
Do you have any ideas as to what the problem might me? and what is the solution? (or should I assume that my database is corrupt and panic, as per Readme.txt ? :)
Many thanks in advance!!!
PS: I have tried various combinations of exporting through Backup and Migrate. But the same error returns. (because I accidentally clicked the wrong place, the default selections as to which tables to import as empty is now gone. If you could remind which ones were selected by default, that's be really appreciated)
Comments
Comment #1
ronan commentedBackup files contain a header and footer that set some MySQL connection options so that the imports happen correctly. The header set's the variables and the footer resets them back to the old version. By splitting the import into 2 operations (which phpMyAdmin does when you chose to continue a timed out import), the footer runs on the second import without the header, so it can't set things back the way they were. I'm not sure what the upshot of all this is to be honest. In all likelihood everything is fine. These settings only apply to the session during which the data is imported and shouldn't have any lasting effects. If your db and phpMyAdmin is set up normally then I imagine everything is probably fine.
Comment #2
ronan commentedComment #4
pdeclarens commentedHi,
drupal version 7.10
phpmy admin 3.4.5
backup version : backup_migrate-7.x-2.x-dev.tar
I have the same problem for the same reasons... my database is 12M and if I try the restore option noting happens
and if I use the import directly in the database, I get the timeout and then the "1231 error
Question is how can I restore a database of this size?
thanks in advance
Comment #5
geek-merlinas far as i understand #1 the following happens:
* you dump som bbiiiig database
* in phpmyadmin...
* 1st import of dbdump times out... so retry
* 2nd import...
* nth import reaches the end of dbdump and freaks out
but at that moment ALL data is restored so you can happily ignore.
Comment #7
ivnish