Skip to content

Commit c30bc9f

Browse files
committed
fixed publishing feedback
1 parent 228f82a commit c30bc9f

File tree

3 files changed

+25
-9
lines changed

3 files changed

+25
-9
lines changed

articles/oracle/oracle-db/provision-manage-oracle-resources.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ After you provision an OracleDB@Azure resource, for example an Oracle Exadata In
1717

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

20-
* Access the resource blade.
20+
* **Access the resource blade**.
2121
1. From the Microsoft Azure portal, select OracleDB@Azure application.
2222
1. From the left menu, select the resource type. For example, select **Oracle Exadata Database@Azure** or **Oracle Autonomous Database@Azure**.
2323
1. If the blade lists and manages several resources, select the resource type at the top of the blade. For example, the **Oracle Exadata Database@Azure** blade accesses both Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources.
@@ -45,8 +45,8 @@ The following management functions are available for all resources from the Micr
4545
1. To create and use a new resource group, select the **Create new** link below the Resource group field. Enter a new resource group name in the **Name** field. Select the **OK** button to save your new resource group and use it. Select the **Cancel** button to return without creating a new resource group.
4646
* **Move the resource to a new subscription.**
4747

48-
> [!NOTE]
49-
> You must have access to another Microsoft Azure subscription, and that subscription must have been setup for access to OracleDB@Azure. If both of these conditions are not met, you will not be able to successfully move the resource to another subscription.
48+
> [!NOTE]
49+
> You must have access to another Microsoft Azure subscription, and that subscription must have been setup for access to OracleDB@Azure. If both of these conditions are not met, you will not be able to successfully move the resource to another subscription.
5050
5151
1. Follow the steps to access the resource blade.
5252
1. Select the link to the resource from the Name field in the table.
@@ -59,18 +59,24 @@ The following management functions are available for all resources from the Micr
5959
1. To create a new tag, enter values in the **Name** and **Value** fields.
6060
1. To edit an existing tag, change the value in the existing tag's **Value** field.
6161
1. To delete an existing tag, select the **Trashcan** icon at the right-side of the tag.
62-
* **Manage Resource Allocation for Oracle Autonomous Database Serverless Instances.**
62+
63+
## Manage resource allocation for Oracle Autonomous Database Serverless instances
64+
65+
The following management functions are available for Oracle Autonomous Database Serverless instances from the Microsoft Azure blade for that resource.
6366

6467
> [!NOTE]
6568
> 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.
6669
67-
1. Follow the steps to access the Oracle Autonomous Database@Azure blade.
70+
Follow the following steps to access the Oracle Autonomous Database@Azure blade.
71+
6872
1. Select the link to the resource from the **Name** field in the table.
6973
1. From the resource's overview page, select the **Setting** link left-menu, and then the **Resource allocation** link.
7074
1. Select the **Manage** button at the top of the Resource allocation page.
7175
1. 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.
7276
1. After you have set or reviewed the fields, select the **Apply** or **Cancel** button as appropriate.
73-
* **Use the OCI console for complete management of the resource.**
77+
78+
* **Use the OCI console for complete management of the resource.**
79+
7480
1. Follow the steps to access the resource blade.
7581
1. Select the link to the resource from the **Name** field in the table.
7682
1. From the resource's detail page, select the **Go to OCI** link on the **OCI Database URL** field.

articles/oracle/oracle-db/provision-oracle-exadata-infrastructure.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,12 @@ Provisioning Oracle Exadata Infrastructure is a time-consuming process. Provisio
4343
1. You can then enter up to 10 **Names** and **Email addresses** that are used as contacts for the maintenance process.
4444
1. Select **Next** to continue.
4545
1. From the **Consent** tab of the Create Oracle Exadata Infrastructure flow, you must agree to the terms of service, privacy policy, and agree to access permissions. Once accepted, select **Next** to continue.
46-
1. From the **Tags** tab of the Create Oracle Exadata Infrastructure flow, you define Microsoft Azure tags. **NOTE:** These tags aren't propagated to the Oracle Cloud Infrastructure (OCI) portal. Once you have created the tags, if any, for your environment, select **Next** to continue.
46+
1. From the **Tags** tab of the Create Oracle Exadata Infrastructure flow, you define Microsoft Azure tags.
47+
48+
>[!NOTE]
49+
> These tags aren't propagated to the Oracle Cloud Infrastructure (OCI) portal.
50+
51+
1. After you create the tags, if any, for your environment, select **Next** to continue.
4752
1. From the **Review _+** create tab of the Create Oracle Exadata Infrastructure 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.
4853
1. Select the **Create** button to start the provisioning flow.
4954
1. Return to the Oracle Exadata Infrastructure blade to monitor and manage the state of your Oracle Exadata Infrastructure environments.

articles/oracle/oracle-db/provision-oracle-exadata-vm-cluster.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,11 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
2121
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.
2222
1. Select the **+ Create** icon at the top of the blade to begin the provisioning flow.
2323
1. Check that you're using the **Create** Oracle Exadata VM Cluster flow. If not, exit the flow.
24-
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.
24+
1. From the **Basics** tab of the Create Oracle Exadata VM Cluster flow, enter the following information.
25+
26+
>[!NOTE]
27+
> 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.
28+
2529
1. Select the Microsoft Azure subscription to which the Oracle Exadata VM Cluster will be provisioned.
2630
1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource.
2731
1. Enter a unique **Name** for the Oracle Exadata VM Cluster on this subscription.
@@ -43,6 +47,7 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
4347
1. **Usable Exadata Storage (TB)** is limited by the Oracle Exadata Infrastructure.
4448
1. **Use Exadata sparse snapshots**, **Use local backups**, and **Usable storage allocation** are options that can only be set at this time before the Oracle Exadata VM Cluster has been provisioned.
4549
1. Select **Next** to continue.
50+
4651
1. From the **Networking** tab of the Create Oracle Exadata VM Cluster flow, enter the following information.
4752
1. The **Virtual network** is limited based on the **Subscription** and **Resource group** that you selected earlier in the provisioning flow.
4853
1. The **Client subnet** is selectable based on the selected **Virtual network**.
@@ -55,6 +60,6 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
5560
1. From the **Diagnostics Collection** tab of the Create Oracle Exadata VM Cluster flow allows you to specify the diagnostic events, health monitoring, and incident logs and tracing that Oracle can use to identify, track, and resolve issues. Select **Next** to continue.
5661
1. From the **Consent** tab of the **Create Oracle Exadata VM Cluster** flow, you must agree to the terms of service, privacy policy, and agree to access permissions. Select **Next** to continue.
5762
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.
58-
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.
63+
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.
5964
1. Select the **Create** button to start the provisioning flow.
6065
1. Return to the Oracle Exadata VM Cluster blade to monitor and manage the state of your Oracle Exadata VM Cluster environments.

0 commit comments

Comments
 (0)