Oracle Cloud Infrastructure Documentation

Managing Autonomous Database Resources in Azure

After provisioning any OracleDB@Azure resource, you can use the Microsoft Azure blade for a limited set of management functions.

Note

There are prerequisites that must be completed before you can provision Autonomous Database Services. You need to complete the following:
  1. An existing Azure subscription
  2. An Azure VNet with a subnet delegated to the Oracle Database@Azure service (Oracle.Database/networkAttachments)
  3. Permissions in Azure to create resources in the region, with the following conditions:
    • No policies prohibiting the creation of resources without tags, because the OracleSubscription resource is created automatically without tags during onboarding.
    • No policies enforcing naming conventions, because the OracleSubscription resource is created automatically with a default resource name.
  4. Purchase OracleDB@Azure in the Azure portal.
  5. Select your Oracle Cloud Infrastructure (OCI) account.
For more detailed documentation, including optional steps, see Onboarding with Oracle Database@Azure.

Common Management Functions from the Microsoft Azure Blade

The following management functions are available for all resources from the Microsoft Azure blade for that resource.

Access the Resource Blade

These are the steps to perform the most common management function for Autonomous Database Services.

  1. From the Microsoft Azure portal, select OracleDB@Azure application.
  2. From the left menu, select Oracle Autonomous Database@Azure.
  3. Select the resource from the list.

List Status for All Resources of the Same Type

These are the steps to list the status of all the Autonomous Database Services resources.

  1. Follow the steps to Access the Resource Blade.
  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 Name field in the table.

Provision a New Resource

These are the steps to provision a new resource in Autonomous Database Services.

  1. Follow the steps to Access the Resource Blade.
  2. Select the + Create icon at the top of the blade.
  3. Follow the provisioning flow for Provisioning an Autonomous Database for Azure.

Refresh the Blade's Info

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

  1. Follow the steps to Access the Resource Blade.
  2. Select the Refresh icon at the top of the blade.
  3. Wait for the blade to reload.

Remove a Resource

These are the steps to remove a resource in Autonomous Database Services.

  1. Follow the steps to Access the Resource Blade.
  2. You can remove a single or multiple resources from the blade by selecting the checkbox on the left side of the table. Once you have selected the resource(s) to remove, you can then select the Delete icon at the top of the blade.
  3. You can also remove a single resource by selecting the link to the resource from the Name field in the table. From the resource's detail page, select the Delete icon at the top of the blade.

Add, Manage, or Delete Resource Tags

These are the steps for adding, managing, and deleting resource tags in Autonomous Database Services.

  1. Follow the steps to Access the resource blade.
  2. Select the link to the resource from the Name field in the table.
  3. From the resource's overview page, select the Edit link on the Tags field.
  4. To create a new tag, enter values in the Name and Value fields.
  5. To edit an existing tag, change the value in the existing tag's Value field.
  6. To delete an existing tag, select the Trashcan icon at the right-side of the tag.

Access Autonomous Database Backups

These are steps for accessing Autonomous Database Backups from Microsoft Azure console.

  1. From the Microsoft Azure portal, select OracleDB@Azure application.
  2. From the left menu, select Oracle Autonomous Database@Azure.
  3. Select your Autonomous Database, and click the Settings link located on the resource's overview page.
  4. Select the Backups link to access and manage all backup information and actions.

Restore Autonomous Database Backups

These are steps to restore your Autonomous Database from backups located on the Microsoft Azure portal.

  1. From the Microsoft Azure portal, select OracleDB@Azure application.
  2. From the left menu, select Autonomous Database.
  3. Select your Autonomous Database, and then click the Settings link located on the resource's overview page.
  4. To restore your Autonomous Database from a backup, select the Backups link, and then click Restore.
  5. From the drop-down list, select the Backup timestamp, and then click Restore.

Clone Autonomous Database from Backups

These are steps to clone your Autonomous Database from backups located on the Microsoft Azure portal.

  1. From the Microsoft Azure portal, select OracleDB@Azure application.
  2. From the left menu, select Autonomous Database.
  3. There are two paths to clone your Autonomous Database from backups.
    1. Click the Setting link located at the resource's overview page. To clone your Autonomous Database from a backup, select the Backups link, and then click Create clone from backup.
    2. Click the Overview link, and then click Create clone.
  4. From the Basics tab of the Clone Oracle Autonomous Database flow, enter the following information.
    1. Select your Subscription. The current Subscription field is automatically selected. If you have any other subscriptions that your account can assess, those will be available in the drop-down list.
    2. Select your Resource group from the drop-down list.
    3. Enter a Name for your Oracle Autonomous Database instance clone.
    4. Select the Region from the drop-down list. The current Region is automatically selected.
    5. The current Source database name is automatically selected.
    6. Select the Clone type from the drop-down list. If you want to create a new database with source database's data and metadata, select Full Clone. If you want to create a new database that includes all source database schema metadata but not the source database data, select Metadata Clone.
    7. The Clone source is a drop-down list containing two existing options. To create a clone from a backup, select Clone from a backup. To create a clone of a running database, select Clone from database instance.
    8. The Backup timestamp field is drop-down list that allows you to select the timestamp of the backup to clone.
    9. The Backup time ended field provides the end time of the backup. This field is automatically changed based on your Backup timestamp selection.
    10. Click the checkbox next to Latest backup timestamp, if you want to use the latest backup timestamp.
    11. Select Next to continue.
  5. For the Oracle Autonomous Database instance cloning flow, see Provisioning an Autonomous Database, and follow the instructions from the Step 4.
    Note

    Supported Workload type for creating a clone from backups include Data Warehouse and Transaction Processing. Select your Workload type from the drop-down list.

Manage Disaster Recovery for Autonomous Database Services

Disaster recovery is an essential service for any production Autonomous Database. There are multiple options available, and you can select the option that works best for your Autonomous Database. These are steps to manage disaster recovery for your Autonomous Database on the Microsoft Azure portal.

Disaster recovery provides a peer database instance in a different availability zone. With a peer database in the local region, if the primary database becomes unavailable, disaster recovery switches to role of the peer database to primary and begins recreating a new peer database.

Note

One local backup-based standby is provided by default and at no additional cost. This capability is provided as a minimum available feature.
Note

You can create up to 1 local peer and 1 cross-region peer for every remote paired region.

These are the steps to manage disaster recovery for Autonomous Database Services.

  1. Follow the steps to Access the Resource Blade.
  2. Select the link in the Name column for the Autonomous Database you want to manage.
  3. The Autonomous Database details will open on the Overview page.
  4. Select Settings > Disaster recovery from the left-menu.
  5. The Disaster recovery page opens, and shows the existing standby databases.

Change Disaster Recovery Type

To change the DR type, follow these steps.

  1. Follow the steps to Manage Disaster Recovery for Autonomous Database Services.
  2. Select the Peer Autonomous Database you wish to change from the list.
  3. Select the Edit button at the top of the list of peer databases.
  4. Select the Disaster recovery type from the drop-down list. By default, a local backup-based disaster recovery peer database is provided. You can opt to change this to use Autonomous Data Guide.
    Note

    Using Autonomous Data Guide for your Disaster recovery type will incur additional costs.
  5. Select the Submit button to commit the changes, if any. Select the Cancel button to return to the Peer Autonomous Database list without saving any changes.

Switchover or Failover a Peer Database

When you perform a switchover, the primary database becomes the standby database and the standby database becomes the primary database, with no data loss. A switchover is typically done to test failover to the standby database for audit or certification reasons, or to test your application's failover procedures when you have added an Autonomous Data Guard standby database. A failover is an unplanned action. To perform either, follow these steps.

  1. Follow the steps to Manage Disaster Recovery for Autonomous Database Services.
  2. Select the Peer Autonomous Database you wish to change from the list.
  3. Select the Switchover or Failover button at the top of the list of peer databases.
  4. Select the Disaster recovery type from the drop-down list.
  5. Enter Switchover or Failover in the field.
  6. Select the Submit button to commit the changes, if any. Select the Cancel button to return to the Peer Autonomous Database list without saving any changes.

Create Cross-Region Disaster Recovery

In addition to in-region disaster recovery peer, you can create a cross-region disaster recovery peer from the Microsoft Azure portal 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.

These are steps to create a cross-region disaster recovery peer from Microsoft Azure console.

  1. From the Microsoft Azure portal, select the OracleDB@Azure application.
  2. From the left menu, select Autonomous Database.
  3. Click the Disaster recovery link located on the resource's overview page.
  4. Select + Add button to create an Oracle disaster recovery.
  5. From the Basics tab of the Add Oracle disaster recovery flow, enter the following information.
    Note

    You can create up to 1 local peer and 1 cross-region peer for every remote paired region that your tenancy subscribed to.
    1. From the drop-down list, select the Region .
      Note

      The regions where the OracleDB@Azure service is available are limited.
      Note

      The Region may not be displayed if there is already a paired region or if there are other limitations.
      Note

      Many regions have a paired region to support cross-region disaster recovery. The pairing is bi-directional. This capability allows you to create a cross-region peer in a different region. For example, if your Autonomous Database is located in the East US region, you can create a cross-region peer in West US, Canada Central, Brazil South. You can only create a cross-region disaster recovery in a paired region.

      Table 1-2 Paired Regions

      Regional Pair A Regional Pair B
      UK South UK West
      Germany West Central France Central
      Italy North France Central
      Australia Southeast UK South
      East US West US
      Canada Central East US
      Brazil South East US
    2. The Resource group list contains resources that share the same lifecycle, permissions and polices. Select the Resource group from the drop-down list.
    3. Enter an unique Name for your Oracle Autonomous Database.
    4. Disaster recovery type field is a drop-down list that allows to select the disaster recovery type for Autonomous Database . Two available disaster recovery types are Back-up based disaster recovery and Autonomous Data Guard.
      Note

      If you select Autonomous Data Guard, Recovery time objective is approximately 15 minutes and Recovery point objective is approximately 1 minute. For more information, see Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
      Note

      If you select Back-up based disaster recovery, Recovery time objective is 1 hour + 1 hour per 5TB and Recovery point objective is 1 minute. For more information, see Backup-Based Disaster Recovery Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
    5. Select the Virtual network from the drop-down list. You can select virtual networks that are located within the subscription of the primary database and within the region selected previously in Step 5a .
    6. Select the Subnet. You can select delegated subnets that are contained within the virtual network that you have selected previously in Step 5e.
    7. If you select the Enable cross-region backup replication to disaster recovery peer checkbox, this enables the backup replication to replicate the backups to the remote peer up to 7 days or less if the selected backup retention period is shorter.
      Note

      Replicated backups incurs an additional costs for backup storage.
    8. Select the Next button to continue.
    9. From the Review + create tab, you can review the field values you have entered. All validations must pass for the creating a disaster recovery process to be started. Once your validations complete successfully, click Create button to create a disaster recovery.

Manage Resource Allocation for Oracle Autonomous Database Serverless Instances

These are the steps for managing resource allocation for Autonomous Database Services.

Note

You can only change the resource allocation settings for Oracle Autonomous Database Serverless instances using these steps. This does not apply to any other resource type.
  1. Follow the steps to access the Access the Resource Blade.
  2. Select the link to the resource from the Name field in the table.
  3. From the resource's overview page, select the Setting link left-menu, and then the Resource allocation link.
  4. Select the Manage button at the top of the Resource allocation page.
  5. From the Manage resource allocation window, you can set the ECPU count from 2 to 512. The Compute auto scaling checkbox allows you to enable your Oracle Autonomous Database to scale its computing allocation automatically up to 512. The Storage is a slider UI that allows setting the Storage allocation from 1 TB to 384 TB. The Storage auto scaling checkbox allows you to enable your Oracle Autonomous Database to scale its storage allocation automatically up to 384 TB.
  6. After you have set or reviewed the fields, select the Apply or Cancel button as appropriate.

Perform a Connectivity Test

These are the steps to perform a connectivity test for Autonomous Database Services.

  1. Follow the steps to access the Access the Resource Blade.
  2. Select the link to the resource from the Name field in the table.
  3. From the resource's overview page, select the Settings link left-menu, and then the Connections link.
  4. Select the Download wallet icon and save the file.
  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.

Access the OCI Console

These are the steps to access the OCI console for Autonomous Database Services.

  1. Follow the steps to Access the Resource Blade.
  2. Select the link to the resource from the Name field in the table.
  3. From the resource's detail page, select the Go to OCI link on the OCI Database URL field.
  4. Login to OCI.
  5. Manage the resource from within the OCI console.

Access Oracle Apex from OCI console

These are steps to access Oracle APEX from the OCI console.

  1. Follow the steps to Access the OCI console.
  2. From the Navigation menu, select Oracle Database, and then select Autonomous Database.
  3. After selecting your Autonomous Database, click the Tool configuration.
  4. Under the Tools section, Oracle APEX with Public access URL is listed. Copy the Public access URL and paste it into your website address bar to access Oracle APEX.

Request Increased Storage or ECPU Limits

These are the steps to request increased storage or ECPU limits for Autonomous Database Services.

  1. From the OracleDB@Azure home, select Overview.
  2. Select the View Oracle Subscription button.
  3. Select the default subscription.
  4. From the left menu for the default subscription, select Help > Support + Troubleshooting.
  5. In the Tell us about the issue to get solutions and support field, enter Oracle Database@Azure and the select the Go button.
  6. In the Which service are you having an issue with? drop-down field, select Databases / Oracle Database@Azure from the list.
  7. Select the Next button.
  8. In the message that appears, select the OCI Support portal link.
  9. Follow the steps as discussed in the Support for OracleDB@Azure process.

Support for OracleDB@Azure

These are the steps to request support for OracleDB@Azure.

  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@Azure 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@Azure

Learn how to request a service limit increase.

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