Using the Console to Manage Database Multicloud Integration for Oracle Database Cloud Services π
Learn how to manage database multicloud integration for Oracle Database Cloud Services.
Integrate Oracle Exadata with Azure Cloud services Oracle Database@Azure Identity Connectors, Storage Containers, and Storage Mounts are key components in the integration of Oracle Exadata with Azure Cloud services.
Create an Identity Connector from the OCI Console Creating an Identity Connector installs the Azure Arc agent on the Exadata VM Cluster VMs, registering them as Azure Arc-enabled virtual machines.
Integrate Oracle Exadata with Azure Cloud services π
Oracle Database@Azure Identity Connectors, Storage Containers, and Storage Mounts are key components in the integration of Oracle Exadata with Azure Cloud services.
Oracle Database@Azure Identity Connectors: These connectors enable seamless interaction between Oracle Exadata Database and Azure Cloud services by linking the Oracle database with Azure identity and access management. It allows for Azure-specific authentication and authorization to be utilized directly within the Exadata VM Cluster.
Azure Storage Containers: Azure Blob Storage is used to store large amounts of unstructured data such as text, images, videos, and backups. By connecting Oracle Exadata to Azure Blob Storage, users can leverage cloud storage for scalable and secure data storage.
Azure Storage Mounts: Azure Blob Storage Mount refers to the process of attaching an Azure Storage Container as a mounted file system on an Oracle Exadata Database Service VM. This mount allows database utilities like Data Pump (impdp/expdp) and RMAN to interact with Azure storage as if it were a local directory.
Create an Identity Connector from the OCI Console π
Creating an Identity Connector installs the Azure Arc agent on the Exadata VM Cluster VMs, registering them as Azure Arc-enabled virtual machines.
This enables secure communication with the Azure Key Management Service (KMS) using the Azure identity generated by the Arc agent. The Azure Arc agent can communicate with Azure services over either a public network or a private connectivity setup. Learn more about Azure Arc.
Each Exadata VM cluster must have an identity connector enabled to access Azure resources. The identity connector establishes either a public or private connection between the Exadata VM cluster and Azure Key Management resources, depending on the roles assigned.
You can create an identity connector in one of two waysβusing the Oracle Exadata Database Service on Dedicated Infrastructure interface or the Database Multicloud Integrations interface.
Oracle Exadata Database Service on Dedicated Infrastructure
Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Dedicated Infrastructure.
From the left menu, click Exadata VM Clusters under Oracle Exadata Database Service on Dedicated Infrastructure.
From the list of Exadata VM Clusters, select the cluster you are using.
Select VM Cluster information, and then navigate to Identity connector located under Multicloud information. Click the Create link.
Note
If an identity connector has not been created previously, it is displayed as None.
The Identity connector name, Exadata VM cluster, Azure subscription id, and Azure resource group name are read-only fields and will be populated with values.
Enter your Azure tenant id, and Access token.
Expand the Show advanced options section.
The Private connectivity information and Tags sections populate.
To enable a private endpoint connection, enter the Azure arc private link scope name.
To add tags for your resources, click Add tag, and then enter required values.
Review your selections, and then click Create to create the identity connector.
Database Multicloud Integrations
Open the navigation menu. Click Oracle Database, then click Database Multicloud Integrations.
Select Identity Connectors from the left navigation menu.
From the Compartment drop-down list, select your compartment that you are using.
Once you select your compartment, the Identity connector name automatically populates a name.
By default, the identity connector type is selected as Azure.
Select ARC agent as an identity mechanism.
Select your compartment from the Choose an Exadata VM cluster compartment list, and then select your Exadata VM Cluster from the Choose an Exadata VM cluster list.
Enter your Azure tenant id. The Azure subscription id and Azure resource group name fields populate values based on your Exadata VM Cluster selection.
Enter an Access token.
Expand the Show advanced options section. The Private connectivity information and Tags sections populate. These fields are optional.
To add tags for your resources, click Add tag, and then enter required values.
Open the navigation menu. Click Oracle Database, then click Database Multicloud Integrations.
Click Storage Containers.
Click Create Storage container.
Enter the following on the resulting Create storage container page.
Compartment: Select a compartment where you want to create this storage container.
Name: Enter a descriptive name for the storage container.
Account name: Enter the Azure storage container user name.
This typically refers to the identity or credentials used to authenticate and access an Azure Storage Container. Depending on the authentication method, it could be an Azure Active Directory (Azure AD) identity or an access key-based authentication.
Storage container name: Enter the name of the Azure storage container.
This is the unique name assigned to a specific storage container within an Azure Storage Account. The container name helps organize and store blobs (files and data) within the account.
IP address: Enter the IP address of the Azure Storage Container.
DNS Alias: Enter the fully qualified domain name (FQDN) that points to the Azure Storage Container.
The following resources will be made available to customers through OCI SDK, CLI, and Terraform. These APIs will be used by customers who wish to integrate Oracle Database on Exadata with Azure Cloud Services.
Capture the Azure Storage Account and Container details, which will be used when mounting the Azure Container in the ExaDB-C@C VM Cluster. Additionally, this operation will update the Azure Storage Account and Container details as needed.
updateOracleDbAzureBlobContainer
Updates the Azure Storage Account and Container details.
changeOracleDbAzureBlobContainerCompartment
Changes the compartment of the Azure Blob Container resource.
deleteOracleDbAzureBlobContainer
Deletes the Azure Blob Container Resource.
getOracleDbAzureBlobContainer
Retrieves a specific Azure Blob Container resource.
listOracleDbAzureBlobContainers
Lists Azure Blob Container resources based on the specified filters.