@kapa.ai I recently moved from standalone mongodb to mongodb atlas. I have different database name in both of these connections. While I am able to create the source connection with the mongodb atlas, I am not able to sync the data. Everytime I run the sync it returns 0 record. In the log it says things like:

Skipping stream old_db_name.collection_name because it is not in the source

How can I fix this?

It seems like you're encountering an issue where the sync process is skipping streams because it cannot find the corresponding collections in the MongoDB Atlas source. This issue is similar to the one reported in the [source-oracle issue](https://github.com/airbytehq/airbyte/issues/33832), where the log message indicates that a stream is being skipped because it is not found in the source. Here are some steps you can take to troubleshoot and potentially resolve this issue: 1. Verify Database and Collection Names: Ensure that the database and collection names in your MongoDB Atlas source match exactly with what you have configured in Airbyte. Even a small discrepancy in names (like case sensitivity) can cause the sync to skip streams. 2. Check User Permissions: Make sure that the user account used for the sync has the necessary permissions to read from the new database and collections in MongoDB Atlas. The user should have at least read access to the database and collections. 3. Update Connector Version: If you are not using the latest version of the MongoDB source connector, consider updating it. There have been significant updates and improvements to the connector, as mentioned in the [closed issue](https://github.com/airbytehq/airbyte/issues/29993) and [another closed issue](https://github.com/airbytehq/airbyte/issues/31338). Updating to the latest version might resolve the issue. 4. Reconfigure the Connection: Sometimes, reconfiguring the connection from scratch can help. Delete the existing connection and set it up again, ensuring that all details are correct. 5. Check Logs for Detailed Errors: Review the logs carefully for any additional error messages or warnings that might give more context about why the streams are being skipped. The log message you provided (

Skipping stream old_db_name.collection_name because it is not in the source

) suggests that the stream names might not match. If these steps do not resolve the issue, you might want to seek further assistance from the Airbyte community or support. You can also refer to the [Airbyte documentation](https://docs.airbyte.com/) for more detailed troubleshooting steps. If you have any more specific log outputs or error messages, feel free to share them for more targeted assistance.