MySQL Import Database Error because of Extended Inserts

Posted by Castgame on Stack Overflow See other posts from Stack Overflow or by Castgame
Published on 2009-03-25T07:35:33Z Indexed on 2010/04/17 8:33 UTC
Read the original article Hit count: 205

Filed under:
|

Hello all,

I'm importing a 400MB(uncompressed) MySQL database. I'm using BIGDUMP, and I am getting this error:

Stopped at the line 387.

At this place the current query includes more than 300 dump lines. That can happen if your dump file was created by some tool which doesn't place a semicolon followed by a linebreak at the end of each query, or if your dump contains extended inserts. Please read the BigDump FAQs for more infos.

I believe the file does contain Extended Inserts, however I have no way to regenerate the database as it has been deleted from the old server. How can I import this database or convert it to be imported?

Thanks for any help.

Best Nick

EDIT: It appears the only viable answer is to separate the extended inserts, but I still need help figuring out how to split the file as the answer below suggests. Please help. Thank you.

© Stack Overflow or respective owner

Related posts about mysql

Related posts about mysqldump