can't edit and delete sql instance after deleting dms job

[rudiyanto]

I got stuck to delete the sql instance and even can't edit the instance . I create dms job before and my job got failed due to there is an update at source db during the dms run . and DMS stop automatically and showed errors . but unfortunately i delete the job straight away after the job failed . i intend to recreate the job and delete my last replication db . but when i try to edit the instance to disable the data protection to be able delete the instance but the instance showed You can't edit this instance right now because there's a blocking operation in progress .it's been 4 days stuck and still can't do anythin to the instance .  Is there any solution i can do to solve this problem without contacting the support? Thanks
 

[ms4446]

If you're encountering issues with editing or deleting a SQL instance in Google Cloud DMS after deleting a DMS job, here are some refined steps to address the issue:

1. Check for Lingering Operations:

   • Navigate to the "Operations" tab in the instance overview within the Google Cloud DMS console.
   • Look for any operations that are listed as "in progress" or "pending."
   • Review the details of these operations to understand their impact on your ability to edit or delete the instance.

2. Retry Deleting the Instance:

   • After ensuring no related operations are blocking the process, try to delete the instance again.
   • If this is successful, you can proceed with recreating your DMS job.

3. Force Operation Cancellation (Use with Caution):

   • If operations are persistently stuck, you might consider canceling them. However, do this cautiously as it could lead to data inconsistencies or other issues.
   • Refer to the official Google Cloud DMS documentation for guidance on how to safely cancel operations and understand the associated risks.

4. Monitor Instance State and Review Logs:

   • Keep an eye on the instance's status for any updates.
   • Check the instance settings and logs for additional information that might help in understanding the issue.

5. Prepare for Contacting Support:

   • If the issue remains unresolved, gather the following information for a support request:
     • Instance ID and Region.
     • A detailed description of the issue, including steps already taken.
     • Screenshots of any error messages and relevant logs.

Important Considerations:

• Use Command-Line Tools: If you're comfortable with it, using Google Cloud's gcloud CLI can provide more detailed insights into the instance and operations.

• Impact on Connected Services: Be mindful of how deleting the instance might affect other services or applications that rely on it.

Remember, forced operation cancellation should be a last resort due to its potential risks. Often, contacting Google Cloud support is the most effective and safest way to resolve complex issues like this.