|
| 1 | +--- |
| 2 | +title: "Known issues: Migrate from MongoDB to Azure CosmosDB" |
| 3 | +titleSuffix: Azure Database Migration Service |
| 4 | +description: Learn about known issues and migration limitations with migrations from MongoDB to Azure Cosmos DB using the Azure Database Migration Service. |
| 5 | +services: database-migration |
| 6 | +author: pochiraju |
| 7 | +ms.author: rajpo |
| 8 | +manager: craigg |
| 9 | +ms.reviewer: craigg |
| 10 | +ms.service: dms |
| 11 | +ms.workload: data-services |
| 12 | +ms.custom: "seo-lt-2019" |
| 13 | +ms.topic: article |
| 14 | +ms.date: 02/27/2020 |
| 15 | +--- |
| 16 | + |
| 17 | +# Known issues/migration limitations with migrations from MongoDB to Azure Cosmos DB's API for MongoDB |
| 18 | + |
| 19 | +Known issues and limitations associated with migrations from MongoDB to Cosmos DB's API for MongoDB are described in the following sections. |
| 20 | + |
| 21 | +## Migration fails as a result of using the incorrect SSL Cert |
| 22 | + |
| 23 | +* **Symptom**: This issue is apparent when a user cannot connect to the MongoDB source server. Despite having all firewall ports open, the user still can't connect. |
| 24 | + |
| 25 | +| Cause | Resolution | |
| 26 | +| ------------- | ------------- | |
| 27 | +| Using a self-signed certificate in Azure Database Migration Service may lead to the migration failing because of the incorrect SSL Cert. The Error message may include “The remote certificate is invalid according to the validation procedure.” | Use a genuine certificate from CA. Self-signed certs are generally only used in internal tests. When you install a genuine cert from a CA authority, you can then use SSL in Azure Database Migration Service without issue (connections to Cosmos DB use SSL over Mongo API).<br><br> | |
| 28 | + |
| 29 | +## Unable to get the list of databases to map in DMS |
| 30 | + |
| 31 | +* **Symptom**: Unable to get DB list on the **Database setting** blade when using **Data from Azure Storage** mode on the **Select source** blade. |
| 32 | + |
| 33 | +| Cause | Resolution | |
| 34 | +| ------------- | ------------- | |
| 35 | +| The storage account connection string is missing the SAS info and thus cannot be authenticated. | Create the SAS on the blob container in Storage Explorer and use the URL with container SAS info as the source detail connection string.<br><br> | |
| 36 | + |
| 37 | +## Using an unsupported version of the database |
| 38 | + |
| 39 | +| Cause | Resolution | |
| 40 | +| ------------- | ------------- | |
| 41 | +| You attempt to migrate to Azure Cosmos DB from an unsupported version of MongoDB. | As new versions of MongoDB are released, they are tested to ensure compatibility with Azure Database Migration Service, and the service is being updated periodically to accept the latest version(s). If there is an immediate need to migrate, as a workaround you can export the databases/collections to Azure Storage and the point the source to the resulting dump. Create the SAS on the blob container in Storage Explorer, and then use the URL with container SAS info as the source detail connection string.<br><br> | |
| 42 | + |
| 43 | +## Next steps |
| 44 | + |
| 45 | +* View the tutorial [Migrate MongoDB to Azure Cosmos DB's API for MongoDB online using DMS](tutorial-mongodb-cosmos-db-online.md). |
| 46 | +* View the tutorial [Migrate MongoDB to Azure Cosmos DB's API for MongoDB offline using DMS](tutorial-mongodb-cosmos-db.md). |
0 commit comments