Autonomous AI Database Service
Use the information in this section to resolve common errors and provisioning issues for Autonomous AI Database Functions in your Oracle AI Database@Google Cloud environments.
Troubleshooting
No currently known troubleshooting topics.
Known Issues
| Known Issue | Resolution |
|---|---|
| From the Google Cloud console, the Autonomous AI Database Details page's Oracle-managed service account field's value is not updated. | After update encryption key settings from Oracle-managed encryption key (OMEK) to Customer-managed encryption key (CMEK), it may take 30 minutes or more for the Oracle-managed service account to appear on the Autonomous AI Database Details page. Wait for the update to complete before attempting allocation of the Oracle-managed service account. |
| If the Autonomous AI Database is unable to access your key for some reason, such as a network outage, then Autonomous AI Database handles the outage with the following process. | There is a 2-hour grace period where the Autonomous AI Database remains up and running. If the key is not reachable at the end of the 2-hour grace period, the Autonomous AI Database Lifecycle state is set to Inaccessible. In this state existing connections are dropped and new connections are not allowed. If Autonomous Data Guard is enabled when using Oracle Cloud Infrastructure Vault, during or after the 2-hour grace period you can manually perform a failover operation. Autonomous Data Guard automatic failover is not triggered when you are using customer-managed encryption keys and the Oracle Cloud Infrastructure Vault is unreachable. |