-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
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. |
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.] |
I have the same issue , i've made everything ready on azure and the db is EMPTY , but getting this error |
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. |
Has anyone found a resolution to this issue? |
I had resolved this issue. Only changed DB name... |
Same issue, I tried creating 3 different databases with no results... |
I got same issue. However, after clear all collections from mLab, the problem went away :) |
open mongo cli, show dbs -> use mydata -> db.dropDatabase() |
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 |
I made a cluster of mLab.com and one app's DB had been migrated successful.
Help me...
The text was updated successfully, but these errors were encountered: