Having trouble in copy data between cosmos mongodb

Rajagopal Venkataramani 5

Operation on target ForEach_q2g failed: Activity failed because an inner activity failed; Inner activity name: Copy_q2g, Error: Failure happened on 'Sink' side. ErrorCode=MongoDbOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=>Failed to operate data via MongoDB client.,Source=Microsoft.DataTransfer.Runtime.MongoDbAtlasConnector,''Type=MongoDB.Bson.BsonSerializationException,Message=Element name 'underwriting.naics_number' is not valid'.,Source=MongoDB.Bson,'

Sajeetharan 2,261 Reputation points Microsoft Employee

2024-01-29T17:35:21.95+00:00

What tool you are using ?
Bhargava-MSFT 31,196 Reputation points Microsoft Employee

2024-02-03T00:46:45.57+00:00

Hello Rajagopal Venkataramani,

Did you get a chance to look into the above response.
Rajagopal Venkataramani 5 Reputation points

2024-02-08T09:06:29.04+00:00

Sorry for late reply, I am using Terraform with Azure Data factory.

In addition to that, Based on my analysis issue in converting json to bson.
Bhargava-MSFT 31,196 Reputation points Microsoft Employee

2024-02-14T21:19:21.2466667+00:00

Hello Rajagopal Venkataramani, Can you please let me know your mongo DB driver version.
Sajeetharan 2,261 Reputation points Microsoft Employee

2024-08-05T04:52:21.43+00:00

@Rajagopal Venkataramani what is the command you ran?
Mamidi Vasavi 0 Reputation points

2025-02-04T14:20:17.8066667+00:00
Hi @Bhargava-MSFT , @Sajeetharan

We're facing similar errors while trying to restore the collections to azure cosmos dB for mongo api serverless vcore model database using adf pipeline's copy activity task, the weird issue is that it has been the issue with only four set of collections json where as it succeeds fine for the rest of 15 collections with in the source database, so have been wondering on what's the issue with these four collections json files, any ideas?

I've been searching online and the forum/community for similar questions and answers and came across this thread https://learn.microsoft.com/en-us/answers/questions/804862/copy-data-from-mongodb-3-2-)-mongodb-3-6-fails-mongodb-3-6-fails) where the author concluded that the issue was with the element name character length however our collections names are normal like 'researches', 'people' etc., so I'd really need some help or guidance on how to mitigate this error and get the json collections restored to our destined cosmos db.

Exception received is as below:

"Code": 23405, "Message": "Failure happened on 'Sink' side. ErrorCode=MongoDbOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=>Failed to operate data via MongoDB client.,Source=Microsoft.DataTransfer.Runtime.MongoDbAtlasConnector,''Type=MongoDB.Bson.BsonSerializationException,Message=Element name '@odata.context' is not valid'.,Source=MongoDB.Bson,'", "EventType": 0, "Category": 5, "Data": { "FailureInitiator": "Sink" },

Share via

Having trouble in copy data between cosmos mongodb

Your answer