[SERVER-10197] Failure in copy database across version Created: 13/Jul/13  Updated: 10/Dec/14  Resolved: 17/Jul/13

Status: Closed
Project: Core Server
Component/s: Admin, Security
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-8280 copydb command always requires creden... Closed
Related
Operating System: ALL
Participants:

 Description   

Source db: 2.2.2, no auth
destination db: 2.4.1, auth enabled

db.copyDatabase fails with

{ "ok" : 0, "errmsg" : "" }

 Comments   
Comment by Spencer Brody (Inactive) [ 17/Jul/13 ]

Hi Dharshan,
This is a known issue, SERVER-8280, which will be fixed in MongoDB v2.6.
The best workaround at the moment is to do exactly as you did and use mongodump/mongorestore.

Comment by Dharshan Rangegowda [ 16/Jul/13 ]

I am using db.copyDatabase(sourcedb, destinationdb, hostname) since the source db does not have any auth. Unfortunately the original servers are not around anymore. I used monogdump/monogorestore to move the data since the VM's were being deprovisioned.

Comment by Daniel Pasette (Inactive) [ 16/Jul/13 ]

Hi Darshan,
can you post the full command you are using as well as the log files for both servers?

Generated at Thu Feb 08 03:22:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.