Bug #3609 Restore from a backupfile failed with error exception
Submitted: 30 Apr 2004 8:53 Modified: 3 Jun 2004 12:44
Reporter: Steffen Schlaer Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.0.3 ALPHA OS:Windows (Windows XP)
Assigned to: Ulrich Bayer CPU Architecture:Any

[30 Apr 2004 8:53] Steffen Schlaer 
Description:
I've created a backup from one database and try do restore this file. The restore failed with the following Error:

The following Exception occured:
Access violation at address 00626627 in module 'LIBMYSQL.dll'. Read of address 00000000

MySQL Server 4.0.17-standard-log is running under SuSE 9.0 Prof. Linux 2.4.21-192-default.

How to repeat:
Create a new backup and the same error exception occured.

Suggested fix:
Workarround: The same backupfile imported by MySQL ControlCenter 0.9.4-beta running on the same Windows XP machine works fine and produces no errors.
[12 May 2004 20:07] chris harwood 
hi

myself and a coleague (mohammed shamma) experienced this same issue with the exception the mysql 4.0.18 server is running on RHAS 2.1.

i uploaded the file manually to the server and tried 

mysql -p db < backup_file.sql

it bombed on line 5.

apparently mysql doesn't like the single quotes in USE 'db'; on line 5.

simply removing them allowed the command line to work fine. Mysql Administrator continued to fail when restoring the modified backup file.

chris
[3 Jun 2004 12:44] Ulrich Bayer 
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info:

Hello,

I think that this problem is character-set related. We have fixed these problems in the 1.0.4 beta release on Windows.

@chris harwood:
I am not sure what Mysql-Administrator version you have used but I would think  that you have already used a new version which dumps the data into a utf-8 encoded sql-file. If so the problem with mysql command line tool was that there was a line missing explaining the character-set of the sql-file. This is also fixed.