Restart an Autonomous Container Database
You restart an Autonomous Container Database by clicking Restart on its Details page.
The restart of an Autonomous Container Database occurs in a rolling fashion, first stopping and starting one of the container database’s database instances and then stopping and starting its other database instance. Thus, at no time are the container database or any of the Autonomous AI Databases created in it unavailable.
Note: You may experience performance degradation while restarting an Autonomous Container Database with Database In-Memory enabled Autonomous AI Databases. For additional information on Database In-Memory, see Database In-Memory.
Required IAM Policies
use autonomous-container-databases
Procedure
-
Go to the Details page of the Autonomous Container Database you want to restart.
For instructions, see View Details of an Autonomous Container Database.
-
Click Restart.
-
In the Restart dialog:
-
Enter the name of the Autonomous Container Database.
-
Optionally, select Force Restart to ignore drain timeouts and immediately restart the Autonomous Container Database. A force restart will terminate all sessions for all Autonomous AI Databases within the Autonomous Container Database and may result in a longer database startup time. It’s recommended to only force a restart in urgent, time-critical situations.
-
Click Restart to begin the rolling restart operation.
Note: In an Autonomous Data Guard configuration, clicking Restart on a primary or standby database does not restart its peer ACDs.
-