Hi @HamoudaAlbakri-3924
When did you receive the error information, after migrating the mailboxes or deleting the mailbox database?
You may try setting the -BadItemLimit for the move request.
The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again.
Get-Moverequest <identity> | Set-Moverequest –baditemlimit <input value>
Resume-Moverequest <identity>
And a related thread which discussed about Remove a Database that is part of a DAG for your reference as well
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.