Bug #55369 Importing dump.xml is not working
Submitted: 19 Jul 2010 15:32 Modified: 19 Aug 2010 16:57
Reporter: Nitin Soni Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Backup Severity:S1 (Critical)
Version:5.0.45-community-nt OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any
Tags: --xml, Backup, MySQL, mysqldump

[19 Jul 2010 15:32] Nitin Soni
Description:
I take backup of my database using following command.

cmd > mysqldump -u root -proot --xml dsr_windsor > dump.sql

Unfortunately my system got crashed and I had to format it.
After installing mysql again i tried to import the back-up data.

cmd > mysql -u root -proot dsr_windsor < dump.sql

This command is giving following error..
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the ma
nual that corresponds to your MySQL server version for the right syntax to use n
ear '<?xml version="1.0"?>
<mysqldump xmlns:xsi="http://www.w3.org/2001/XMLSchema-ins'; at line 1

I tried following command also.. but nothing seems to be working. :(

cmd > mysql -u root -proot dsr_windsor --xml < dump.sql

How to repeat:
Take a back up.

cmd > mysqldump -u root -proot --xml dsr_windsor > dump.sql

drop all the tables.

import backup

cmd > mysql -u root -proot dsr_windsor < dump.sql

Gives error:
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the ma
nual that corresponds to your MySQL server version for the right syntax to use n
ear '<?xml version="1.0"?>
<mysqldump xmlns:xsi="http://www.w3.org/2001/XMLSchema-ins'; at line 1
[19 Jul 2010 16:57] Valeriy Kravchuk
Looks like you may need MySQL 5.1.x server to load that dump properly, and some tool/actions to create tables before loading data. Read http://dev.mysql.com/tech-resources/articles/xml-in-mysql5.1-6.0.html for some hints (xmldump_load stored procedure, for example).
[19 Aug 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".