You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/exadata-examples-services.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -317,7 +317,9 @@ data "azapi_resource_list" "listDbSystemShapesByLocation" {
317
317
In this section, you will find examples of how to use the `AzAPI` provider to manage Oracle Exadata services in Azure.
318
318
319
319
### Create an Oracle Database Home on an Exadata VM Cluster on an Exadata Infrastructure with a Delegated Subnet in Microsoft Azure
320
-
__NOTE:__ The following script creates an Oracle Exadata Infrastructure and an Oracle Exadata VM Cluster using the `AzAPI` Terraform provider followed by creating an Exadata Database deployment using the OCI Terraform provider ([https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_db_home](https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_db_home)).
320
+
>[!NOTE]
321
+
>The following script creates an Oracle Exadata Infrastructure and an Oracle Exadata VM Cluster using the `AzAPI` Terraform provider followed by creating an Exadata Database deployment using the OCI Terraform provider ([https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_db_home](https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_db_home)).
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/exadata-multicloud-landing-zone-azure-services.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,12 +52,12 @@ For module details, see [Oracle Multicloud Landing Zone for Azure](https://githu
52
52
|[az-oci-rbac-n-sso-fed](https://github.com/oracle-quickstart/terraform-oci-multicloud-azure/tree/main/templates/az-oci-rbac-n-sso-fed)| Set up both identity federation and RBAC roles/groups | All the following |
53
53
|[az-oci-sso-federation](https://github.com/oracle-quickstart/terraform-oci-multicloud-azure/tree/main/templates/az-oci-sso-federation)| Set up [SSO Between OCI and Microsoft Entra ID](https://docs.oracle.com/iaas/Content/Identity/tutorials/azure_ad/sso_azure/azure_sso.htm)|[hashicorp/azuread](https://registry.terraform.io/providers/hashicorp/azuread/)|
54
54
|| 1. Get service provider metadata from OCI IAM. |[hashicorp/azurerm](https://registry.terraform.io/providers/hashicorp/azurerm)|
55
-
|| 2. Create an Entra ID application. |[hashicorp/oci](https://registry.terraform.io/providers/hashicorp/oci)|
56
-
|| 3. Set up SAML SSO for the Entra ID application. ||
57
-
|| 4. Set up attributes and claims in the Entra ID application. ||
58
-
|| 5. Assign a test user to the Entra ID application. ||
59
-
|| 6. Enable the Entra ID application as the Identity Provider (IdP) for OCI IAM. ||
60
-
|| 7. Set up [Identity Lifecycle Management Between OCI IAM and Entra ID](https://docs.oracle.com/iaas/Content/Identity/tutorials/azure_ad/lifecycle_azure/azure_lifecycle.htm#azure-lifecycle). ||
55
+
|| 2. Create an Microsoft Entra ID application. |[hashicorp/oci](https://registry.terraform.io/providers/hashicorp/oci)|
56
+
|| 3. Set up SAML SSO for the Microsoft Entra ID application. ||
57
+
|| 4. Set up attributes and claims in the Microsoft Entra ID application. ||
58
+
|| 5. Assign a test user to the Microsoft Entra ID application. ||
59
+
|| 6. Enable the Microsoft Entra ID application as the Identity Provider (IdP) for OCI IAM. ||
60
+
|| 7. Set up [Identity Lifecycle Management Between OCI IAM and Microsoft Entra ID](https://docs.oracle.com/iaas/Content/Identity/tutorials/azure_ad/lifecycle_azure/azure_lifecycle.htm#azure-lifecycle). ||
61
61
|[az-odb-rbac](https://github.com/oracle-quickstart/terraform-oci-multicloud-azure/tree/main/templates/az-odb-rbac)| Create [roles and groups in Azure](https://docs.oracle.com/iaas/Content/multicloud/oaagroupsroles.htm) for Exadata and Autonomous Database services. |[hashicorp/azuread](https://registry.terraform.io/providers/hashicorp/azuread/)|
62
62
|| 1. Create Azure role definition for ADBS Administrator role.|[hashicorp/azurerm](https://registry.terraform.io/providers/hashicorp/azurerm)|
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/exadata-provision-infrastructure.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,8 @@ For more detailed documentation, including optional steps, see [Onboarding with
28
28
>[!NOTE]
29
29
> Review the [Troubleshoot issues for Exadata services](exadata-troubleshoot-services.md), specifically the IP Address Requirement Differences, to ensure you have all the information needed for a successful provisioning flow.
30
30
31
+
## Provision Oracle Exadata infrastructure and VM Cluster resources
32
+
31
33
1. Provision your Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create an Oracle Exadata VM Cluster resource, select that tab first.
32
34
1. Select the **+ Create** icon at the top of the blade to begin the provisioning flow.
33
35
1. Check that you're the **Create** Oracle Exadata Infrastructure flow. If not, exit the flow.
@@ -36,18 +38,17 @@ For more detailed documentation, including optional steps, see [Onboarding with
36
38
1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource. A resource group is a collection of resources sharing the same lifecycle, permissions, and policies.
37
39
1. Enter a unique **Name** for the Oracle Exadata Infrastructure on this subscription.
38
40
1. Select the **Region** where this Oracle Exadata Infrastructure is provisioned.
39
-
40
-
>[!NOTE]
41
-
>The regions where the OracleDB@Azure service is available are limited.
42
-
41
+
>[!NOTE]
42
+
>The regions where the OracleDB@Azure service is available are limited.
43
43
1. Select the **Availability zone** where this Oracle Exadata Infrastructure is provisioned.
44
-
> [!NOTE]
45
-
> The availability zones where the OracleDB@Azure service is available are limited.
46
-
44
+
> [!NOTE]
45
+
> The availability zones where the OracleDB@Azure service is available are limited.
47
46
1. The **Oracle Cloud account name** field is display-only. If the name isn't showing correctly, your OracleDB@Azure account setup hasn't been successfully completed.
48
47
1. Select **Next** to continue.
49
48
1. From the Configuration tab of the Create Oracle Exadata Infrastructure flow, enter the following information.
50
-
1. From the dropdown list, select the **Exadata infrastructure model** you want to use for this deployment. NOTE: Not all Oracle Exadata Infrastructure models are available. For more information, see [Oracle Exadata Infrastructure Models](https://docs.oracle.com/iaas/exadatacloud/exacs/ecs-ovr-x8m-scable-infra.html#GUID-15EB1E00-3898-4718-AD94-81BDE271C843).
49
+
1. From the dropdown list, select the **Exadata infrastructure model** you want to use for this deployment.
50
+
> [!NOTE]
51
+
> Not all Oracle Exadata Infrastructure models are available. For more information, see [Oracle Exadata Infrastructure Models](https://docs.oracle.com/iaas/exadatacloud/exacs/ecs-ovr-x8m-scable-infra.html#GUID-15EB1E00-3898-4718-AD94-81BDE271C843).
51
52
1. The **Database servers** selector can be used to select a range from 2 to 32.
52
53
1. The **Storage servers** selector can be used to select a range from 3 to 64.
53
54
1. The **OCPUs** and **Storage** fields are automatically updated based on the settings of the **Database servers** and **Storage servers** selectors.
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/exadata-provision-vm-cluster.md
+26-11Lines changed: 26 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@ ms.service: oracle-on-azure
8
8
ms.date: 08/01/2024
9
9
---
10
10
11
-
12
11
# Provision Exadata virtual machine clusters
13
12
14
13
Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Exadata Infrastructure, and is a prerequisite for Oracle Exadata Databases that runs on the cluster.
@@ -17,23 +16,27 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
17
16
18
17
There are prerequisites that must be completed before you can provision Exadata Services. You need to complete the following:
19
18
20
-
1. An existing Azure subscription
21
-
1. An Azure virtual network with a subnet delegated to the Oracle Database@Azure service (`Oracle.Database/networkAttachments`)
22
-
1. Permissions in Azure to create resources in the region, with the following conditions:
19
+
- An existing Azure subscription
20
+
- An Azure virtual network with a subnet delegated to the Oracle Database@Azure service (`Oracle.Database/networkAttachments`)
21
+
- Permissions in Azure to create resources in the region, with the following conditions:
23
22
* No policies prohibiting the creation of resources without tags, because the OracleSubscription resource is created automatically without tags during onboarding.
24
23
* No policies enforcing naming conventions, because the OracleSubscription resource is created automatically with a default resource name.
25
-
1. Purchase OracleDB@Azure in the Azure portal.
26
-
1. Select your Oracle Cloud Infrastructure (OCI) account.
24
+
- Purchase OracleDB@Azure in the Azure portal.
25
+
- Select your Oracle Cloud Infrastructure (OCI) account.
27
26
For more detailed documentation, including optional steps, see [Onboarding with Oracle Database@Azure](onboard-oracle-database.md).
28
27
29
28
>[!NOTE]
30
29
>Review the [Troubleshoot Exadata services](exadata-troubleshoot-services.md), specifically the IP Address Requirement Differences, to ensure you have all the information needed for a successful provisioning flow.
31
30
32
-
1. You provision Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create an Oracle Exadata VM Cluster resource, select that tab first.
31
+
1. You provision Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected.
32
+
To create an Oracle Exadata VM Cluster resource, select that tab first and follow these instructions.
33
+
33
34
1. Select the **+ Create** icon at the top of the blade to begin the provisioning flow.
34
35
1. Check that you're using the **Create** Oracle Exadata VM Cluster flow. If not, exit the flow.
35
-
1. From the **Basics** tab of the Create Oracle Exadata VM Cluster flow, enter the following information. NOTE: Before you can provision an Oracle Exadata VM Cluster, you must have a provisioned Oracle Exadata Infrastructure which you'll assign for your Oracle Exadata VM Cluster.
36
-
1. Select the Microsoft Azure subscription to which the Oracle Exadata VM Cluster will be provisioned.
36
+
1. From the **Basics** tab of the Create Oracle Exadata VM Cluster flow, enter the following information.
37
+
> [!NOTE]
38
+
> Before you can provision an Oracle Exadata VM Cluster, you must have a provisioned Oracle Exadata Infrastructure which you'll assign for your Oracle Exadata VM Cluster.
39
+
1. Select the Microsoft Azure subscription to which the Oracle Exadata VM Cluster will be provisioned.
37
40
1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource.
38
41
1. Enter a unique **Name** for the Oracle Exadata VM Cluster on this subscription.
39
42
1. Select the **Region** where this Oracle Exadata Infrastructure is provisioned. NOTE: The regions where the OracleDB@Azure service is available are limited, and you should assign the Oracle Exadata VM Cluster to the same region as the parent Oracle Exadata Infrastructure.
@@ -59,7 +62,9 @@ For more detailed documentation, including optional steps, see [Onboarding with
59
62
1. The **Virtual network** is limited based on the **Subscription** and **Resource group** that you selected earlier in the provisioning flow.
60
63
1. The **Client subnet** is selectable based on the selected **Virtual network**.
61
64
1. To use a custom DNS domain, select the **Custom DNS** checkbox. If unchecked, the Oracle Exadata VM Cluster uses the default domain, oraclevcn.com.
62
-
1. If checked, a list of existing DNS private views from OCI is presented. Select the view to use. To create a new private view and zones, see [Configure Private DNS](https://docs.oracle.com/iaas/exadatacloud/exacs/ecs-network-setup.html#ECSCM-GUID-69CF2720-31BE-455B-93E3-D2E39B2DA44B). **NOTE:** In order for the list of DNS private views to be populated correctly, the network link's compartment in OCI must match the Microsoft Azure subscription.
65
+
1. If checked, a list of existing DNS private views from OCI is presented. Select the view to use. To create a new private view and zones, see [Configure Private DNS](https://docs.oracle.com/iaas/exadatacloud/exacs/ecs-network-setup.html#ECSCM-GUID-69CF2720-31BE-455B-93E3-D2E39B2DA44B).
66
+
> [!NOTE]
67
+
> In order for the list of DNS private views to be populated correctly, the network link's compartment in OCI must match the Microsoft Azure subscription.
63
68
1. Enter the **Host name prefix**. The prefix forms the first portion of the Oracle Exadata VM Cluster host name.
64
69
1. The **Host domain name** and **Host and domain URL** for your Oracle Exadata VM Cluster are read-only and populated with derived naming.
65
70
1. Within the **Network ingress rules** section, the **Add additional network ingress rules** checkbox allows you to define addition ingress CIDR rules. Additional network CIDR ranges (such as application or hub subnet ranges) can be added, during provisioning, to the network security group (NSG) ingress rules for the VM cluster. The selected virtual network's CIDR is added by default. CIDR ranges are specified. The port can be a single port, port range (for example, 80-8080), a comma-delimited list of ports (for example, 80,8080), or any combination of these. This only updates the OCI network security group ingress rules. Microsoft Azure virtual network network security rules must be updated in the specific virtual network in Microsoft Azure.
@@ -69,4 +74,14 @@ For more detailed documentation, including optional steps, see [Onboarding with
69
74
1. From the **Tags** tab of the Create Oracle Exadata VM Cluster flow, you can define Microsoft Azure tags. NOTE: These tags aren't propagated to the Oracle Cloud Infrastructure (OCI) portal. Select **Next** to continue.
70
75
1. From the **Review _+ create** tab of the Create Oracle Exadata VM Cluster flow, a short validation process is run to check the values that you entered from the previous steps. If the validation fails, you must correct any errors before you can start the provisioning process.
71
76
1. Select the **Create** button to start the provisioning flow.
72
-
1. Return to the Oracle Exadata VM Cluster blade to monitor and manage the state of your Oracle Exadata VM Cluster environments.
77
+
1. Return to the Oracle Exadata VM Cluster blade to monitor and manage the state of your Oracle Exadata VM Cluster environments.
78
+
79
+
## Next steps
80
+
-[Onboard with Oracle Database@Azure](onboard-oracle-database.md)
81
+
-[Provision and manage Oracle Database@Azure](provision-oracle-database.md)
82
+
-[Oracle Database@Azure support information](oracle-database-support.md)
83
+
-[Network planning for Oracle Database@Azure](oracle-database-network-plan.md)
84
+
-[Groups and roles for Oracle Database@Azure](oracle-database-groups-roles.md)[Provision and manage Oracle Database@Azure](provision-oracle-database.md)
85
+
-[Oracle Database@Azure support information](oracle-database-support.md)
86
+
-[Network planning for Oracle Database@Azure](oracle-database-network-plan.md)
87
+
-[Groups and roles for Oracle Database@Azure](oracle-database-groups-roles.md)
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/exadata-whats-new-services.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,4 +18,13 @@ Oracle Database@Azure (OracleDB@Azure) provides you with seamless integration of
18
18
| ---------- | ------- | ------------|
19
19
| July 2024 | Added a Quickstart Terraform Templates and Modules section. | This section grows as the templates and modules are revised and new content is added. |
20
20
21
-
The above table only lists the changes within the Oracle Database@Azure product specific to Oracle Exadata Infrastructures or Oracle Exadata VM Clusters. For changes to the Oracle Exadata Infrastructure or the Oracle Exadata VM Cluster products, see [What’s New in Oracle Exadata Database Service on Dedicated Infrastructure](https://docs.oracle.com/en/engineered-systems/exadata-cloud-service/ecscm/exa-whats-new.html).
21
+
The above table only lists the changes within the Oracle Database@Azure product specific to Oracle Exadata Infrastructures or Oracle Exadata VM Clusters. For changes to the Oracle Exadata Infrastructure or the Oracle Exadata VM Cluster products, see [What’s New in Oracle Exadata Database Service on Dedicated Infrastructure](https://docs.oracle.com/en/engineered-systems/exadata-cloud-service/ecscm/exa-whats-new.html).
0 commit comments