Oracle Cloud Infrastructure Documentation

Managing Autonomous Database Resources in Google Cloud

After provisioning any OracleDB@GCP resource, you can use the Google Cloud console for a limited set of management functions. Some functions and features require use of the OCI console for management or implementation.

Common Management Functions from the Google Cloud Console

The following management functions are available for all resources from the Google Cloud console for that resource.

Access the Resource Console

These are the steps to perform to access the resource console.

  1. From the Google Cloud console, select Oracle Database@Google Cloud application.
  2. You have two options. One, from the left menu, select Autonomous Database. Two, from the center panel, select the EXPLORE AUTONOMOUS DATABASE button.
  3. If the console lists and manages several resources, select the resource type at the top of the console.

List Status for Autonomous Database

These are the steps to list status for Autonomous Database.

  1. Follow the steps to Access the resource console.
  2. Resources will be shown in the list as Succeeded, Failed, or Provisioning.
  3. Access the specifics of that resource by selecting the link in the Display Name field in the table.

Provision a New Autonomous Database

These are the steps to provision a new Autonomous Database.

  1. Follow the steps to Access the resource console.
  2. Select the + Create icon at the top of the console.
  3. Follow the provisioning flow for Provisioning an Autonomous Database for Google Cloud.

Refresh the Console's Info for Autonomous Database

These are the steps to refresh the console's info for Autonomous Database.

  1. Follow the steps to Access the resource console.
  2. Select the Refresh icon at the top of the console.
  3. Wait for the console to reload.

Start/Stop/Restart an Autonomous Database

These are steps to start/stop/restart an Autonomous Database.

  1. Follow the steps to List status for all Autonomous Databases.
  2. Access the specific Autonomous Database by selecting the link in the Display Name field in the table.
  3. If the Autonomous Database is stopped, there will be a START icon at the top of the page. Select the START icon to start the Autonomous Database.
  4. If the Autonomous Database is started, there will be STOP and RESTART icons at the top of the page. Select the STOP icon to stop the Autonomous Database. Select the RESTART icon to stop the Autonomous Database.
  5. Whether you are starting, stopping, or restarting an Autonomous Database, a modal window appears asking you to confirm your action. You can CANCEL your action, or select START, STOP, or RESTART to perform that action.

Remove an Autonomous Database

These are steps to remove an Autonomous Database.

  1. Follow the steps to Access the resource console.
  2. You can remove a single Autonomous Database from the console by selecting the vertical elipsis on the right side of the table. Once you have selected the resource(s) to remove, you can then select the Delete icon.

List the Backups for an Autonomous Database

These are steps to list the backups for an Autonomous Database.

Note

There are two (2) types of backups. Auto backup backups are created based on the backup settings selected when provisioning an Autonomous Database. Long-term backup backups are specifically created and can be retained for a minimum of three (3) months and a maximum of ten (10) years.
  1. Follow the steps to Access the resource console.
  2. Access the specific Autonomous Database by selecting the link in the Display Name field in the table.
  3. Select the BACKUPS tab.
  4. In the Backups section, you will see the list with timestamps for the available backups.

Create a Long-term Backup

These are steps to create a long-term backup.

  1. Follow the steps to List the backups for an Autonomous Database.
  2. Select the link to the Autonomous Database from the Display Name field in the table.
  3. Select the BACKUPS tab.
  4. In the Backups section, you will see the list with timestamps for the available backups.
  5. Select the CREATE LONG-TERM BACKUP icon at the top of the list of available backups.
  6. The Create long-term backup modal window opens.
  7. Set the Retention period values, including Years (365 days), Months (30 days), and Days. These values must be more than the minimum of three (3) months and less than the maximum of ten (10) years.
  8. If you want to create a schedule for long-term backups, select the Schedule long-term backup checkbox.
    1. Select the Date and Time for the first long-term backup to start.
    2. Select the Repeat value that is appropriate for your long-term backup.
  9. Select the SAVE button to save your long-term backup schedule, or the CANCEL button to return without saving the schedule.

Manage Auto Backup Settings

These are steps to manage auto backup settings.

  1. Follow the steps to List the backups for an Autonomous Database.
  2. Select the link to the Autonomous Database from the Display Name field in the table.
  3. Select the BACKUPS tab.
  4. In the Backups section, you will see the list with timestamps for the available backups.
  5. Select the EDIT button for the Automatic backup retention period.
  6. Select the new Backup retention period in days from 1 to 60 days.
  7. Select the SAVE button to save your long-term backup schedule, or the CANCEL button to return without saving the schedule.

Access the OCI Console

These are steps to access the OCI Console.

  1. Follow the steps to Access the resource console.
  2. Select the link to the Autonomous Database from the Display Name field in the table.
  3. Select the MANAGE IN OCI icon at the top of the details page.
  4. Manage the resource from within the OCI console.

Perform a Connectivity Test

These are steps to perform a connectivity test.

  1. Follow the steps to Access the OCI console.
  2. Navigate to the Autonomous Database Details page.
  3. Select the Database Connection.
  4. Select the Download wallet button.
  5. Open Oracle SQL Developer. If you don't have SQL Developer installed, download SQL Developer and install.
  6. Within SQL Developer, open a new connection with the following information.
    1. Name - Enter a name of your choice used to save your connection.
    2. Username - Enter ADMIN.
    3. Password - Enter the password used when creating the Autonomous Database.
    4. Role - Select default.
    5. Save Password - Select the box if you security rules allow. If not, you will need to enter the PDB password every time you use this connection in SQL Developer.
    6. Connection Type - Select Cloud Wallet.
    7. Configuration File - Select Browse, and select the wallet you downloaded.
    8. Select the Test button. The Status at the bottom of the connections list, should show as Success. If the connection is not a success, the wallet is out of date, or the ADB is not currently running.
    9. Select the Save button.
    10. Select the Connect button.

Support for OracleDB@GCP

These are steps to access support resources.

  1. Follow the steps to Access the OCI console.
  2. From the OCI console, there are two ways to access support resources.
    1. At the top of the page, select the Help (?) icon at the top-right of the menu bar.
    2. On the right-side of the page, select the floating Support icon. NOTE: This icon can be moved by the user, and the precise horizontal location can vary from user to user.
  3. You have several support options from here, including documentation, requesting help via chat, visiting the Support Center, posting a question to a forum, submitting feedback, requesting a limit increase, and creating a support request.
  4. If you need to create a support request, select that option.
  5. The support request page will auto-populate with information needed by Oracle Support Services, including resource name, resource OCID, service group, service, and several other items dependent upon the specific OracleDB@GCP resource.
  6. Select the support option from the following options:
    1. Critical outage for critical production system outage or a critical business function is unavailable or unstable. You or an alternate contact must be available to work this issue 24x7 if needed.
    2. Significant impairment for critical system or a business function experiencing severe loss of service. Operations can continue in a restricted manner. You or an alternate contact are available to work this issue during normal business hours.
    3. Technical issue where functionality, errors, or a performance issue impact some operations.
    4. General guidance where a product or service usage question, product or service setup, or documentation clarification is needed.
  7. Select the Create Support Request button.
  8. The support ticket is created. This ticket can be monitored within the OCI console or via My Oracle Support (MOS).

Request a Limit Increase for OracleDB@GCP

Learn how to request a service limit increase.

If you need to increase a service limit for your OracleDB@GCP , see Requesting a Limit Increase for Database Resources.

Create and Manage Cross-Region Disaster Recovery

Learn how to create a cross-region disaster recovery peer from the Google Cloud console to protect your Autonomous Database instance from a complete region failure with a standby database or a backup copy in a different region than the primary database.

Follow the steps to create a cross-region disaster recovery peer.
  1. From the Google Cloud console, select Oracle Database@Google Cloud application.
  2. From the left menu, select Autonomous Database. Then, click on the link to your Autonomous Database from the Display Name field.
  3. Select the DISASTER RECOVERY tab, and then click on the CREATE button.
    Note

    Adding disaster recovery creates a peer database and incurs an additional cost.
  4. From the Add peer database window, select the Region.
    Note

    You can create up to 1 local peer and 1 cross-region peer for every remote paired region that your tenancy subscribed to.
    Note

    If there is already a paired region, then that Region will not displayed in the list.
    Note

    Some regions have a paired region to support cross-region disaster recovery. The pairing is bi-directional and it will allow you to create a cross-region peer in a different region. You can only create a cross-region disaster recovery in a paired region. For more information, see the following table below.

    Table 1-2 Paired Regions

    Regional Pair A Regional Pair B
    US East US West
    UK South Germany Central
  5. Click the checkbox to Enable cross-region backup replication to disaster recovery peer.
    Note

    For the disaster recover type, Autonomous Data Guard is a supported option.
    Note

    Cross-region Autonomous Data Guard standby databases incurs an additional cost.
    Note

    For Autonomous Data Guard, Recovery time objective is approximately 15 mins and Recovery point objective is approximately 1 min. For more information, see Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) .
  6. Scroll down to the Network access for standby section to enter your Subnet range for your Autonomous Database in CIDR notation.
    Note

    You can modify and manage your network settings within the OCI console after creating a peer database.
  7. Click on the Show Advanced settings arrow and then enter the Private IP address and Hostname prefix.
  8. Check the field values you have entered, and then click on the SAVE button to create a peer database.
  9. Once the process completes successfully, the Status changes to Active.
  10. You can view the peer database in the resource list under the DISASTER RECOVERY section. If you want to manage your previously created peer database in OCI, click on the MANAGE IN OCI link from the top menu.
  11. If you perform peer database switchover in the OCI console, then the Status will change to Role change in progress.
    Note

    During this process, you can not DELETE your Autonomous Database.
  12. Once the switchover process is complete, the peer database changes to Primary while the former Autonomous Database changes to Standby.