Help Center> Data Replication Service> Troubleshooting> Solutions to Failed Check Items> Conflicts> Checking Whether the Same View Names Exist in Both the Source and Destination Databases

Updated on 2022-07-19 GMT+08:00

View PDF

Checking Whether the Same View Names Exist in Both the Source and Destination Databases

Migration from MongoDB to DDS

**Table 1** Checking whether the same view names exist in both the source and destination databases
Check Item	Whether the same view names exist in both the source and destination databases
Description	Check whether the source and destination databases have the same view names to prevent existing views from being overwritten. If view of the same name exists in the destination database, the migration cannot be performed.
Failure Cause and Handling Suggestion	Failure cause: The same view names exist in both the source and destination databases. Handling suggestions: Delete the destination database views that have the same names as those in the source database. Alternatively, do not migrate the views with the same names.

Parent topic: Conflicts

Previous topic: Checking Whether the Names of the Source and Destination Databases Are the Same

Next topic: Checking Whether the Destination Database Contains a Non-Empty Collection with the Same Name As the Source Database

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.