Stopping, Starting and Restarting a Database Deployment

Topics

About Stopping, Starting and Restarting a Database Deployment

About Stopping a Database Deployment

When you stop a Database Classic Cloud Service database deployment, no access to it is possible and you can perform no management operations on it except to start it or to delete it.

Stopping a database deployment is similar to turning off your personal computer: it has no computing capabilities because the CPU and RAM have no power, but all its other resources—disk drives and the data they contain, static IP reservations, and so on—remain and are ready to be put back into use when power is restored.

When database deployment is stopped, its CPU and RAM (an Oracle Compute Cloud Service instance) are stopped. As a consequence, it consumes no OCPU or memory resources and so metering and billing of these resources stop. However, all the other resources of the database deployment continue to exist and so continue to be metered and billed, including:

Oracle Compute Cloud Service resources such as storage volumes and IP address reservations
Oracle Storage Cloud Service storage space used by the database deployment’s backups to the Oracle Cloud (if the database deployment was being backed up to cloud storage)

Additionally, when database deployment is stopped, backups of it are not performed.

About Starting a Stopped Database Deployment

When you start a stopped Database Classic Cloud Service database deployment, access to it becomes possible again and you can perform management operations on it such as scaling and patching.

Starting a stopped database deployment is similar to turning your personal computer back on: its computing capabilities are restored because the CPU and RAM again have power, and all its other resources are put back into use.

When database deployment is started:

An Oracle Compute Cloud Service instance of the appropriate compute shape (OCPU and memory) is allocated to it.
All other Compute Cloud Service resources associated with it when it was created or as the result of a scaling operation are reattached to it.
The allocated Oracle Compute Cloud Service instance is started.

After these steps complete, the database deployment is running and available.

Because the started database deployment again consumes OCPU and memory resources, metering and billing of these resources resume.

Note:

Compute Cloud Service resources that were associated with the database deployment using the Oracle Compute Cloud Service console are not reattached when it is started. As a result, you must manually reattach the following kinds of Compute Cloud Service resources:

Storage volumes you created and attached using the Oracle Compute Cloud Service console.

You must attach such storage volumes to the new Oracle Compute Cloud Service instance once the database deployment is started, and then connect to the compute node and mount them.
Security lists to which you added the database deployment’s previous Oracle Compute Cloud Service instance.

You must add such security lists to the new Oracle Compute Cloud Service instance once the database deployment is started.

To manage custom network access to your service instance, you can use manually created security rules that refer to the database deployment’s default security list instead of using manually created and added security lists. If you do so, you can avoid the need to add the manually created security lists to the new Oracle Compute Cloud Service instance once the database deployment is started. For more information, see Enabling or Restricting Port Access by Creating an Access Rule.

About Restarting a Database Deployment

When you restart a Database Classic Cloud Service database deployment, it is stopped and then immediately started again. Thus, the information about what happens when stopping and starting a database deployment applies to restarting a database deployment as well, just in immediate succession.

Note:

Restarting a database deployment is different from rebooting a compute node of a database deployment. Rebooting a compute node, as described in Rebooting a Compute Node, does not restart the database deployment. It simply reboots the compute node.

Stopping a Database Deployment

In general, you stop a Database Classic Cloud Service database deployment for one of these reasons:

To prohibit access to it.
To reduce its cost of operation.

Before You Begin

To learn what happens when you stop a Database Classic Cloud Service database deployment, review About Stopping, Starting and Restarting a Database Deployment.

Procedure

To stop a database deployment:

View the Overview page for the database deployment:
1. Open the Oracle Database Classic Cloud Service console.
  
  For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
2. In the list of deployments, click the name of the database deployment you want to stop.
  
  The Oracle Database Classic Cloud Service Overview page is displayed.
From the menu for the database deployment’s compute node, select Stop, and then confirm the action.

The deployment first has a status of Maintenance and then Stopped in the Oracle Database Classic Cloud Service console. Note that you cannot scale a stopped deployment.

Starting a Stopped Database Deployment

Before You Begin

To learn what happens when you start a stopped Database Classic Cloud Service database deployment, review About Stopping, Starting and Restarting a Database Deployment.

Procedure

To start a stopped database deployment:

View the Overview page for the database deployment:
1. Open the Oracle Database Classic Cloud Service console.
  
  For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
2. In the list of deployments, click the name of the database deployment you want to start.
  
  The Oracle Database Classic Cloud Service Overview page is displayed.
From the menu for the database deployment’s compute node, select Start, and then confirm the action.

The deployment has a status of Maintenance in the Oracle Database Classic Cloud Service console until it is fully started.

Restarting a Database Deployment

Note:

Restarting a database deployment is different from rebooting a compute node of a database deployment. Rebooting a compute node, as described in Rebooting a Compute Node, does not restart the database deployment. It simply reboots the compute node.

Before You Begin

To learn what happens when you restart a Database Classic Cloud Service database deployment, review About Stopping, Starting and Restarting a Database Deployment.

Procedure

To restart a database deployment:

View the Overview page for the database deployment:
1. Open the Oracle Database Classic Cloud Service console.
  
  For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
2. In the list of deployments, click the name of the database deployment you want to restart.
  
  The Oracle Database Classic Cloud Service Overview page is displayed.
From the menu for the database deployment’s compute node, select Restart, and then confirm the action.

The deployment has a status of Maintenance in the Oracle Database Classic Cloud Service console until it is fully restarted.

Viewing Past Stop, Start and Restart Activity

You can see information about past stop, start and restart activity for a Database Classic Cloud Service database deployment by viewing the activity log:

View the Overview page for the database deployment:
1. Open the Oracle Database Classic Cloud Service console.
  
  For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
2. In the list of deployments, click the name of the database deployment whose past activity you want to view.
  
  The Oracle Database Classic Cloud Service Overview page is displayed.
Click the triangle icon beside the Activity title to expand the activity log.

The activity log shows information about past operations performed on the database deployment, with the most recent activity first.
Click the triangle icon beside an operation to see details about that operation.

If an operation failed, the details include information about why it failed.