diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md index 0e2824a..b474d6c 100644 --- a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md +++ b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md @@ -173,22 +173,20 @@ This lab requires completion of the following: ## Task 4: List VM Cluster Configuration using CLI ->**Note:** To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***. +>**Note:** For this lab, we will be using the ***Azure Cloud Shell tool*** with an **OCI CLI** configured. -1. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section. +1. From the Azure portal, In the Oracle Exascale VM Cluster properties page, Copy the Exascale VM Cluster OCID by clicking on the ***copy to clipboard*** button in the ***OCID*** field under the **Properties** section. ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") Paste the VM Cluster OCID to a text editor. -2. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. +2. Click the **Azure Cloud Shell** icon in the console header. - ![navigate to oci cloudshell](./images/oci-cloud-shell.png "navigate to oci cloudshell") - - This displays the Cloud Shell in a "drawer" at the bottom of the console: - - ![oci cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") + ![navigate to oci cloudshell](./images/azure-cloud-shell.png "navigate to oci cloudshell") + This displays the Azure Cloud Shell in a "drawer" at the bottom of the portal. + 3. Run the OCI CLI Command to get the VM Cluster Configuration. >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 4 Step 1)* diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/azure-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/azure-cloud-shell.png new file mode 100644 index 0000000..58e26e6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/azure-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png index 19bbf8f..7c43965 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png index e73b3e7..fdbd16a 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png index a4e97a1..8506f21 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png index b16c295..3b287f2 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png index f6b702d..26f2568 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png index f6385dd..650b9b4 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png index 02a9a80..148eb1c 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png index 0fec12f..051c230 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png index 0f32146..b2007e7 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png index 5bdca95..5d644e8 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png index 2de56d3..d6fe8bb 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png index f361b4a..58a3a01 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png index 0cf3716..6926198 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png index 360a51e..a9dc162 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md index 9539ba6..2db5d0c 100644 --- a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md +++ b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md @@ -21,48 +21,23 @@ This lab requires the completion of the following: ## Task 1: Get the VM Cluster Details using OCI CLI ->**Note:** To use **OCI CLI** for this lab, we will be using the ***OCI Cloud Shell tool***. +>**Note:** For this lab, we will be using the ***Azure Cloud Shell tool*** with an **OCI CLI** configured. - -1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. - -2. Select your ***Compartment***, and Select your **VM Cluster**. +1. From the Azure portal, In the Oracle Exascale VM Cluster properties page, Copy the Exascale VM Cluster OCID by clicking on the ***copy to clipboard*** button in the ***OCID*** field under the **Properties** section. - ![Navigate to the VM Cluster ](./images/navigate-vmcluster.png "Navigate to the VM Cluster") - -3. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. - - ![navigate to oci cloudshell](./images/oci-cloud-shell.png "navigate to oci cloudshell") - - This displays the Cloud Shell in a "drawer" at the bottom of the console: - - ![oci cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") + ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") - >**Note:** For this lab, we will be using the ***OCI Code Editor*** to store the required details in this lab. - - Click on the ***Expand*** icon in **Actions** and select ***Open Code Editor***. + Paste the VM Cluster OCID to a text editor. - ![expand actions to show open code editor](./images/expand-code-editor.png "expand actions to show open code editor") +2. Click the **Azure Cloud Shell** icon in the console header. - This displays the Code Editor in a side by side view with the Cloud Shell. - - ![launch code editor](./images/code-editor-launch.png "launch code editor") - - You can use the code editor to copy and paste obtained environment details in the lab. For better code viewing, under ***View*** select ***View: Toggle Word Wrap***. + ![navigate to oci cloudshell](./images/azure-cloud-shell.png "navigate to oci cloudshell") - -4. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section. + This displays the Azure Cloud Shell in a "drawer" at the bottom of the portal. - ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") - - - Paste the VM Cluster OCID value in your code or text editor. - +3. Run the OCI CLI Command to get the VM Cluster Configuration. - -5. Run the OCI CLI Command to get the VM Cluster Configuration. - - >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 4)* + >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 1)* ``` @@ -99,12 +74,13 @@ This lab requires the completion of the following: 1. From the Cloud Shell terminal, make an OCI REST API call to get a list of the available Database Homes in a compartment by running the **OCI RAW-REQUEST** command below: - > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{CompartmentOCID}"*** with the **Compartment OCID** obtained from ***Task 1 Step 5*** + > **Note:** Replace the [**API endpoint region**](https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/) "***{region}***" with your **assigned region** and ***"{CompartmentOCID}"*** with the **Compartment OCID** obtained from ***Task 1 Step 3*** + ``` - oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10" + oci raw-request --http-method GET --target-uri "https://database.{region}.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10" ``` @@ -167,12 +143,12 @@ This lab requires the completion of the following: 1. Run the OCI CLI Command to list the available Pluggable Databases in a Container Database. - >**Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***{ContainerDatabaseOCID}*** with the ***Container Database (CDB) OCID*** obtained from ***Task 3*** + > **Note:** Replace the [**API endpoint region**](https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/) "***{region}***" with your **assigned region** and ***{ContainerDatabaseOCID}*** with the ***Container Database (CDB) OCID*** obtained from ***Task 3*** ``` - oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" + oci raw-request --http-method GET --target-uri "https://database.{region}.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" ``` @@ -199,8 +175,6 @@ This lab requires the completion of the following: 1. Prepare the JSON file for the Create Pluggable Database REST API call request body that contain the Create Thin Clone Pluggable Database Details resource. - Open the ***Code Editor*** tab. - Create a JSON file ***MyThinClonePDB.json*** with the required ***Create Pluggable Database*** details below * **pdbName:** ***"ThinPDB2"*** @@ -218,14 +192,14 @@ This lab requires the completion of the following: Open the **OCI Cloud Shell** tab and run the following command - >**Note:** Replace the API endpoint region "***{region}***" with your **assigned region** + > **Note:** Replace the [**API endpoint region**](https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/) "***{region}***" with your **assigned region** ![create thin clone using REST API](./images/create-thin-clone-cloud-shell.png "create thin clone using REST API") ``` - oci raw-request --http-method POST --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases" --request-body file://MyThinClonePDB.json + oci raw-request --http-method POST --target-uri "https://database.{region}.oraclecloud.com/20160918/pluggableDatabases" --request-body file://MyThinClonePDB.json @@ -252,12 +226,12 @@ This lab requires the completion of the following: 1. Make an OCI REST API call to get a list of the Exascale Storage Vaults in the specified compartment by running the **OCI RAW-REQUEST** command below: - > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***{CompartmentOCID}*** with the ***Compartment OCID*** obtained from ***Task 1*** + > **Note:** Replace the [**API endpoint region**](https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/) "***{region}***" with your **assigned region** and ***{CompartmentOCID}*** with the ***Compartment OCID*** obtained from ***Task 1*** ``` - oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/exascaleDbStorageVaults?compartmentId={CompartmentOCID}&limit=10" + oci raw-request --http-method GET --target-uri "https://database.{region}.oraclecloud.com/20160918/exascaleDbStorageVaults?compartmentId={CompartmentOCID}&limit=10" diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/azure-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/azure-cloud-shell.png new file mode 100644 index 0000000..58e26e6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/azure-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png index a4e97a1..8506f21 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png index cdf1766..b7f6d51 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png index f2d59b2..b57eb38 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png index cce8914..713e681 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png index 77755d7..92d52b9 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png index 13232b0..35d032b 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png index a3964a4..56c739f 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png index 60eeb0f..3257db4 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png index e8c9d1b..22ec14c 100644 Binary files a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/get-started-gs/get-started-gs.md b/exadata-database-service-at-azure-xs-get-started/get-started-gs/get-started-gs.md index 4d75104..f7ae2cc 100644 --- a/exadata-database-service-at-azure-xs-get-started/get-started-gs/get-started-gs.md +++ b/exadata-database-service-at-azure-xs-get-started/get-started-gs/get-started-gs.md @@ -40,7 +40,7 @@ Oracle Cloud is the industry's broadest and most integrated cloud provider, with | Limits Name | Description | Value | |-------------|-------------|----------| | exadbxs-vm-instance-base-count|Exadata Database Service on Exascale Infrastructure - Instance Count| >= **2**| - | exadbxs-total-cpu-base-count | Exadata Database Service on Exascale Infrastructure - Total ECPU Count | >= **24** | + | exadbxs-total-cpu-base-count | Exadata Database Service on Exascale Infrastructure - Total ECPU Count | >= **32** | | exadbxs-local-storage-base-gb | Exadata Database Service on Exascale Infrastructure - Local Storage (GB) | >= **600** GB | | exadbxs-hc-storage-base-gb | Exadata Database Service on Exascale Infrastructure - High Capacity Storage (GB) | >= **600** GB diff --git a/exadata-database-service-at-azure-xs-get-started/introduction-gs/introduction-gs.md b/exadata-database-service-at-azure-xs-get-started/introduction-gs/introduction-gs.md index d6e4357..7fbdded 100644 --- a/exadata-database-service-at-azure-xs-get-started/introduction-gs/introduction-gs.md +++ b/exadata-database-service-at-azure-xs-get-started/introduction-gs/introduction-gs.md @@ -2,7 +2,7 @@ ## About this Workshop -This workshop is designed to provide you with hands on experience using the Exadata Database Service on Exascale Infrastructure, which is Oracle’s next generation architecture of the Exadata Database Service. +This workshop is designed to provide you with hands on experience using the Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure. In this workshop, you will use several of the OCI management interfaces to conduct various database lifecycle tasks on the Exadata Database Service on Exascale Infrastructure.