If a pluggable database is showing in failed state on the Oracle Cloud Infrastructure (OCI) console however it is in fact up and running on VM/ Exadata DB system, the below steps can help fix the issue.
Capture the UID for the failed PDB resource from OCI Console
Login to OCI console, navigate to the compartment where the Exadata DB system is running, and copy the CON_UID from the error message by clicking on the small informational “i” icon.
Now, login to the Exadata DB system VM and login to the database and ensure that there is no PDB running with the same CON_UID.
[oracle ~]$ sqlplus / as sysdba SQL*Plus: Release 184.108.40.206.0 - Production on Wed Jul 13 12:50:56 2022 Version 220.127.116.11.0 Copyright (c) 1982, 2021, Oracle. All rights reserved. Connected to: Oracle Database 19c EE Extreme Perf Release 18.104.22.168.0 - Production Version 22.214.171.124.0 SQL> select NAME, CON_ID from V$PDBS where CON_UID=123456789; no rows selected SQL>
Once confirmed, go back to the OCI console and delete the PDB that is showing in a failed state. Once the PDB is terminated, a new PDB resource will be created by the agent sync process which is typically scheduled to run every 30 minutes.
For some time, you will see two PDB resources in OCI console with the same name. One in terminated state and another in available state. This is absolutely fine as the resource in the terminated state will be automatically removed in some time.