Oracle Cloud Infrastructure Documentation

Deleting Google Cloud Projects

Learn what to expect if you shut down (delete) a Google Cloud project.

Preparing for a Project Shut Down

When planning to shut down a Google Cloud project that contains Oracle Database@Google Cloud resources, note the following:

  • Google Cloud automatically adds a lien to all Oracle Database@Google Cloud resources for their protection. Therefore, a project owner must remove the lien on each Oracle Database@Google Cloud resource before deleting the project. See Protecting projects with liens in the Google Cloud documentation for information on working with liens.

  • When a project owner shuts down a project, Google Cloud puts the project in a suspended state for a 30 day recovery period before the shut down is complete and the project is deleted. During the recovery period, the project isn't usable. Note that applications can't access any Oracle Database@Google Cloud databases in the project during the recovery period because network access is suspended.

Important

Google Cloud continues to bill for existing Oracle Database@Google Cloud resources during the recovery period. For this reason, we recommend that you delete all Oracle Database@Google Cloud resources before shutting down a project.

See Shutting down (deleting) projects in the Google Cloud documentation for more information.

Restoring a Project During the 30-Day Recovery Period

Project owners can restore a project during the 30-day recovery period if needed. Note that billing isn't automatically enabled if the project is restored, and to resume using Oracle Database@Google Cloud in a restored project, you need to reconnect the restored project to the Google Cloud billing account with the Oracle Database@Google Cloud entitlement. If you don't reconnect the billing account to the project, you can't interact with your Oracle Database@Google Cloud resources in the Google Cloud console.

See Restore a project in the Google Cloud documentation for more information.