Concurrent Operations on Autonomous Database
Describes the actions that cause Oracle Cloud Infrastructure Console to ask you to confirm pausing or canceling a concurrent operation.
When you initiate certain operations that take some time to complete, including scaling the system, these operations do not prevent you from performing other operations. For example, database connections, database operations, and most Autonomous Database actions proceed normally while you scale the system. However, certain database lifecycle management actions such as stopping the database have an impact on concurrent long-running operations.
For some actions a confirmation dialog displays to let you know when a concurrent operation is active. This allows you to proceed or to cancel the operation. For example, while stopping Autonomous Database you see a message such as the following:
Description of the illustration adb_confirm_stop.png
- Manage Scaling with Concurrent Operations
Describes the impact on scaling operations when you initiate certain actions during an ongoing scaling request. - Long-Term Backup with Concurrent Operations
Describes the impact on a long-term backup operation when you initiate certain actions during an ongoing long-term backup.
Parent topic: Lifecycle Operations
Manage Scaling with Concurrent Operations
Describes the impact on scaling operations when you initiate certain actions during an ongoing scaling request.
| Action | Description |
|---|---|
| Stop |
Stop pauses scaling. The scaling restarts when the database starts. |
| Restart |
Restart pauses scaling. The scaling restarts when the database starts. |
| Restore |
Restore pauses scaling. The scaling restarts when the restore completes if resources allow. |
| Switchover |
Switchover pauses scaling. The scaling restarts when the switchover completes. The scaling also occurs on the standby database after the switchover. |
| Failover |
Failover pauses scaling. The scaling restarts when the failover completes. The scaling also occurs on the standby database if it is available after the failover. |
| Terminate |
Scaling stops and the database is terminated. |
| Change Database Mode Read-Write or Read-Only |
A mode change pauses scaling. The scaling restarts when the database starts after the mode change completes. |
Parent topic: Concurrent Operations on Autonomous Database
Long-Term Backup with Concurrent Operations
Describes the impact on a long-term backup operation when you initiate certain actions during an ongoing long-term backup.
| Action | Description |
|---|---|
| Stop |
Stop cancels an ongoing long-term backup. The long-term backup does not restart when the database starts. |
| Restart |
Restart cancels an ongoing long-term backup. The long-term backup does not restart when the database starts. |
| Restore |
Restore cancels an ongoing long-term backup. |
| Switchover |
Switchover cancels an ongoing long-term backup. The long-term backup does not restart after the switchover completes. |
| Failover |
Failover cancels an ongoing long-term backup. The long-term backup does not restart after the failover completes. |
| Terminate |
Terminate cancels an ongoing long-term backup. |
Parent topic: Concurrent Operations on Autonomous Database