Start, Stop, and Restart an Autonomous AI Database on Dedicated Exadata Infrastructure

You can manage start, stop, and restart an Autonomous AI Database from its Details page.

Required IAM Policies

use autonomous-databases

Go to the Details page of the Autonomous AI Database you want to stop.

Note: For databases that use Autonomous Data Guard, go to the Details page of the primary database.

For instructions, see View Details of a Dedicated Autonomous AI Database.
On Oracle Public Cloud, click Stop under More actions, and on Exadata Cloud@Customer, click Stop under Actions.
Click Stop to confirm.
Note: When you stop an Autonomous AI Database, the following details apply:
- Tools are no longer able to connect to the database.
- In-flight database transactions and queries are stopped.
- CPU billing is halted.

Go to the Details page of the Autonomous AI Database you want to start.

Note: For databases that use Autonomous Data Guard, go to the Details page of the primary database.

For instructions, see View Details of a Dedicated Autonomous AI Database.
On Oracle Public Cloud, click Start under More actions, and on Exadata Cloud@Customer, click Start under Actions.

Start is only shown for a stopped database.
Click Start to confirm.

Note: When you start an Autonomous AI Database, CPU billing is initiated, billed by the second with a minimum usage period of one minute.

Go to the Details page of the Autonomous AI Database you want to restart.

Note: For databases that use Autonomous Data Guard, go to the Details page of the primary database.

For instructions, see View Details of a Dedicated Autonomous AI Database.
On Oracle Public Cloud, click Restart under More actions, and on Exadata Cloud@Customer, click Restart under Actions.
In the confirmation dialog, select Restart to confirm.

Your database is restarted; that is, it is stopped and then immediately started.