New answers tagged mysql-5.1
I have resolved the issue myself only using following process : Change the replication mode to ROW. Restrict the size of max_binlog_size=30M In this way binary log file cant be of huge size and easy to replicate.
It looks like it must have been the zone (sub-region) that was the issue. The slow loading happened when the EC2 container with the *.sql file was in us-east-1a and the RDS instance was in us-east-1b.
it permissions conflict when try create file - c:>mydatabase.sql create new folder c:\backup, change string to C:\>mysql\bin\mysqldump.exe -u root -p mydatabase > c:\backup\mydatabase.sql I think it just mistake when type there - c:\>mydatabase.sql it is also not correct, correct: c:\mydatabase.sql correct, but still will return ...
Well that appears the correct way as far as you're using right path to binary mysqldump! Can you confirm if you can login (and it behaves well?): mysql -uroot -p Not sure if there are some security issues! Run the command prompt as administrator and attempt to run the mysqldump again.
Top 50 recent answers are included