Home/ Questions/Q 197027
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T16:49:03+00:00

I’m importing a 400MB (uncompressed) MySQL database. I’m using BIGDUMP, and I am getting

  • 0

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?

Edit

It appears the only viable answer is to separate the extended inserts, but I still need to figure out how to split the file as the answer below suggests.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I was able to import the database successfully after increasing the memory buffer and doing an ordinary MySQL import via SSH.

    I used the following command with the absolute path:

    mysql -u <username> -p < /home/dir/dumpfile.sql
    • 0