Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The destination database was not empty. #1009

Closed
kimhongyeon opened this issue Mar 13, 2016 · 10 comments
Closed

The destination database was not empty. #1009

kimhongyeon opened this issue Mar 13, 2016 · 10 comments

Comments

@kimhongyeon
Copy link

I made a cluster of mLab.com and one app's DB had been migrated successful.

  1. I added new DB for another app in my cluster.
  2. I tried to migrate hosted parse DB to mLab DB.
  3. But error was occured!!
  4. Migration tool shown "The destination database was not empty.".

Help me...

@drew-gross
Copy link
Contributor

Did you maybe use the DB that already had data in it? The migration tool won't migrate an app to a database that already has data in it. If that is not the case, please open a ticket on parse.com/help, as that is where do support for migration issues.

@StolenCouchGames
Copy link

I have the same issue We've made a new server after we tried transferring to another. Now I can't start the migration again.

[EDIT: Nevermind. Go to App Settings and click op Migrate. There you can connect to your new IP.]

@MostafaS
Copy link

I have the same issue , i've made everything ready on azure and the db is EMPTY , but getting this error

@sidan5
Copy link

sidan5 commented May 22, 2016

Same issue here using mLab on AWS. Happen after an hour of migration (estimate 3 hours).

Using dedicated program to migrate 3 GB of data.

@christianpbrink
Copy link

Has anyone found a resolution to this issue?

@kimhongyeon
Copy link
Author

I had resolved this issue. Only changed DB name...

@cs-marcoblagoiev
Copy link

Same issue, I tried creating 3 different databases with no results...

@bill-lin
Copy link

I got same issue. However, after clear all collections from mLab, the problem went away :)

@pcg92
Copy link

pcg92 commented Oct 30, 2016

open mongo cli, show dbs -> use mydata -> db.dropDatabase()

@dariuxmx
Copy link

dariuxmx commented Jan 4, 2017

I resolved this issue, if you are setting with heroku, go to Mongo Add on to open the Database and erase all collections. Try again to migrate your database from Parse and vuala!

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants