You want to stop a Database Cloud Service Database Deployment as you are not using it or for some maintenance work. When you stop a database deployment, you can't access it and can't perform any management operations other than starting or deleting the Database Deployment.
Stopping a database deployment is very simple and it is similar to powering off a computer or laptop.
It is important to note that when database deployment is stopped, its CPU and RAM are stopped. As a result, 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.
In this article we will demonstrate how to stop a Database Cloud Service Database Deployment.
Steps to Stop a Database Cloud Service Database Deployment
- Open a web browser and enter the URL you received in the Welcome email to login to Oracle Cloud Account
- Enter your username and password
- On the home page, Click "Menu" under "Database" Cloud Service as shown below
- Click "Open Service Console"
- On the this page, Click "Menu" as shown
- Click "Stop" from the list
- Click "OK" to confirm
- A message displays that the stop request is accepted
- We can see that the status has changed to "Service Maintenance..". Click on Instance name "NSM-DBaaS"
- We can see that the status is still under "Service Maintenance..". Under Overview section it says "Stopping service.."
- We can now see that the status has changed to "Service Stopped"
Login to the Oracle Cloud Compute Node to verify that the server is not accessible.
- Open PuTTY session on your desktop and enter Compute Node IP address
- On the left pane, expand "SSH" and select "Auth". On the right pane, click on "Browse" button. Select the Private Key that matches the Public Key for your Deployment. Click "Open"
- Connection timed out. It means that the server is down and not accessible
Conclusion
In this article we have learned how to stop a Database Cloud Service Database Deployment. When database deployment is stopped, its CPU and RAM are stopped. As a result, 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.
No comments:
Post a Comment