Checking Whether Collections in Both the Source and Destination Databases Are Not Capped

**Table 1** Checking whether collections in both the source and destination databases are not capped
Check Item	Whether collections in both the source and destination databases are not capped
Description	Check whether collections in both the source and destination databases are not capped. If not, the migration fails.
Failure Cause and Handling Suggestion	Failure cause: the destination database has a collection whose name is the same as that of the capped collection of the source database. Handling suggestion: To ensure data consistency, you can delete the collection in the destination database with the same name as the capped collection in the source database. Alternatively, you can choose not to migrate the capped collection that will contradict with that in the destination database.
Failure Cause and Handling Suggestion	Failure cause: The collections to be migrated are capped collections and already exist in the destination database. Handling suggestion: To ensure data consistency, you can delete the collection in the destination database with the same name as the capped collection in the source database. Alternatively, you can choose not to migrate the capped collection that will contradict with that in the destination database.