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 new file mode 100644 index 0000000..0e2824a --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md @@ -0,0 +1,242 @@ + + + +# Configure & Validate Notifications for Monitoring ECPU Scaling changes + + +## Introduction + +This lab walks you through the steps to configure & validate notifications for monitoring ECPU Scaling changes. + +**Estimated Lab Time:** ***15 minutes*** + +**How Notifications Work?** + +The OCI Notifications service communicates when something happens with your resources in Oracle Cloud Infrastructure. + +The Notifications service lets you to set up communication channels for publishing messages using topics and subscriptions. When a message is published to a topic, the Notifications service sends the message to all of the topic's subscriptions. + +![Introduction Notifications](./images/notifications-events-intro.png "Introduction Notifications") + +**Notifications Concepts** + +The following concepts are essential to working with OCI Notifications Service: + +***Notification*** - A configuration for sending messages, such as an alarm or event rule. Each message is sent to subscriptions in the specified topic. + +***Subscription*** - An endpoint for a topic. Published messages are sent to each subscription for a topic. + + You can get human-readable messages through supported subscription protocols: + + * **Email** + * **Function** + * **HTTPS (Custom URL)** + * **PagerDuty** + * **Slack** + * **SMS** + +***Topic*** - A communication channel for sending messages to subscriptions. Each topic name is unique across the tenancy. + +***Event Rules*** - When triggered, an event rule sends an event message to the configured topic. Notifications then deliver the message to active subscriptions. + +***Database Service Events*** - Database Service Events enables you to be notified about health issues with your Oracle Databases or other components on the Database Cloud Service. + +**Create Events Rule to Create Notification Automation for Database Service Events** + +The Database Service Events feature implementation generates events for Data Plane operations and conditions and Notifications by leveraging the existing OCI Events service and Notification service. Users can subscribe to the Database Service Events and receive notifications. To receive notifications, subscribe to the Database Service Events and get notified using the Oracle Notification service. + +### Objectives + +- After completing this lab, you should be able to configure notifications and events rules for monitoring ECPU Scaling changes for Exadata Database Service on Exascale Infrastructure + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** +* Required IAM Policies for [**Managing Topics and Notifications**](https://docs.oracle.com/en-us/iaas/Content/Security/Reference/notifications_security.htm#iam-policies) and [**Managing Events**](https://docs.oracle.com/en-us/iaas/Content/Identity/policyreference/cloudeventspolicyreference.htm) + +## Task 1: Configure Notification Topic and Subscription for Enabled ECPU change + +1. Open the navigation menu and click **Developer Services**. Under **Application Integration**, click **Notifications**. + + ![Navigate to Notifications](./images/navigate-notifications.png " ") + +2. The **Topics** page is selected by default, select your Compartment and Click **Create Topic**. + + ![Click Create Topic](./images/create-topic.png " ") + +3. Provide the Topic name. For this lab, use ***MyExaDBXSTopic*** for the Topic name. + + ![Provide Topic display name and Create Topic](./images/create-topic-name.png " ") + +4. Click **Create**. + + ![Click Create Topic](./images/click-create-topic.png " ") + + Once the Topic has been created, you will see the created Topic with the state of ***Active***. + + ![Display Topic Status](./images/create-topic-active.png " ") + +5. Click the name of the Topic you created to open the **Topic Details** page. + + ![Click on Created Topic](./images/click-on-created-topic.png " ") + +6. On the Topic Details page, click **Create Subscription**. + + ![Click Create Subscription](./images/create-subscriptions.png " ") + +7. In the Create Subscription panel, for **Protocol**, select ***Email***. Provide your ***Email Address***, then Click **Create** + + ![Create Subscription](./images/click-create-subscription.png " ") + + >**Note:** Notifications creates the email subscription and sends a confirmation URL to your assigned email address. + + The subscription is ***pending*** until confirmation is received. + + ![Subscription Pending Status](./images/subscription-pending-status.png " ") + +8. Open your assigned Email, Check for the ***OCI Notifications Service Subscription Confirmation*** email, and Click the ***Confirm subscription*** link. + + ![Confirm Subscription](./images/confirm-subscription.png " ") + + By clicking the confirmation link, it will launch a browser displaying that the subscription has been confirmed and that you have subscribed your assigned Email to the Topic you selected. + + ![Subscription Confirmation Display](./images/subscription-confirmation-page.png " ") + + You can now see that the subscription is ***Active***. + + ![Subscription Active](./images/subscription-active.png " ") + + +## Task 2: Create Events Rule to Create Notification Automation for Enabled ECPU Change + +1. Open the navigation menu and click **Observability & Management**. Under **Events Service**, click **Rules**. + + ![Navigate Rules in OCI Console](./images/navigate-rules.png " ") + +2. Select your ***Compartment*** and Click **Create Rule** + + ![Click Create Rule](./images/click-create-rule.png " ") + +3. In the Create Rule panel, provide the Rule name. For this lab, use ***MyExaDBXSEventsRule***. + + ![Create Events Rule](./images/create-events-rule.png " ") + +4. Configure **Rule Conditions**: + + * In the **Rule Conditions** section, For Condition, Select ***Event Type***. + * For **Service Name**, select ***Database*** + * For **Event Type**, Select ***Exadb VM Cluster - Update Begin*** and ***Exadb VM Cluster - Update End*** + + ![Configure Rule Conditions](./images/configure-rule-conditions.png " ") + +5. Configure **Actions**: + + * In the **Actions** section, For **Action Type**, Select ***Notifications***. + * For **Notifications Compartment**, select your ***Compartment*** + * For **Topic**, Select ***MyExaDBXSTopic*** + + + ![Configure Actions](./images/configure-actions.png " ") + +6. Click **Create Rule** + + ![Create Rule](./images/create-rule.png " ") + +## Task 3: Validate the Current VM Cluster Resource Allocation and Scale up the Enabled ECPUs using the Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + +2. Select your ***Compartment***, and Select your **VM Cluster**. + + ![Navigate to the VM Cluster ](./images/navigate-vmcluster.png "Navigate to the VM Cluster") + + The VM Cluster Details page displays information about the selected VM cluster. Under the **Resource allocation**, pay attention to the number of ***Enabled ECPUs:*** + + ![Navigate to the Resource allocation](./images/resource-allocation.png "Navigate to the Resource allocation") + +3. In the VM Cluster Details page, Click **Scale VM Cluster**. + + ![Scale VM Cluster](./images/scale-vmcluster.png "Scale VM Cluster") + + ![View Enabled ECPU](./images/current-ecpu.png "View Enabled ECPU") + + Scale Up the number of ***ECPUs enabled per VM*** from ***8 ECPU*** to ***12 ECPU*** + + ![Scale Up ECPU](./images/scale-ecpu.png "Scale Up ECPU") + + +4. Click **Save Changes** + + >**Note:** ECPU scaling activities are done online with no downtime. Once the scale up operation is complete, the VM Cluster status changes from ***Updating*** to ***Available***. + +## 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***. + +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. + + ![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. + + ![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") + +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)* + + ``` + + + oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state"}' + + + ``` + + After running the command, you will see similar output below. + + ![show new enabled ecpus](./images/show-new-enabled-ecpu-ocicli.png "show new enabled ecpus") + + You can see the new ***Enabled ECPU*** for the VM Cluster and with the ***Lifecycle State*** of ***Available***. + +## Task 5: Confirm Notifications output in the notification email that was configured + +1. Open your assigned email. You should be receiving two notification emails. + + Review the details of the following notification email events: + + * Start of the ECPU scale up operation - ***(updateexadbvmcluster.begin)*** + + ![Image showing sample notification email for update vm cluster begin](./images/begin-notification.png "Image showing sample notification email for update vm cluster begin") + + * End of the ECPU scale up operation ***(updateexadbvmcluster.end)*** + + ![Image showing sample notification email for update vm cluster begin](./images/end-notification.png "Image showing sample notification email for update vm cluster begin") + + The Notification email for the Update VM Cluster Events shows the before and After VM Cluster ECPU Allocation. + + Pay attention to the following fields from the notification email message: + * ***CPU Core Count*** + * ***Reserved CPU Core Count*** + * ***Enabled ECPU Core Count*** + * ***Reserved ECPU Core Count*** + +***!!! Congratulations:*** You may now **proceed to the next lab**. + +## Learn More + +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/exadata-cloud-infrastructure-events.html) to learn more about Oracle Exadata Database Service on Exascale Infrastructure Events. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, March 2025. 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 new file mode 100644 index 0000000..19bbf8f Binary files /dev/null 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-create-rule.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-rule.png new file mode 100644 index 0000000..ee2bb0a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-rule.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png new file mode 100644 index 0000000..46bcff4 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.png new file mode 100644 index 0000000..5cea5bb Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.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 new file mode 100644 index 0000000..e73b3e7 Binary files /dev/null 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/cloudshelllaunch.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png new file mode 100644 index 0000000..dea470a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png new file mode 100644 index 0000000..708c9cb Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png new file mode 100644 index 0000000..4166697 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png new file mode 100644 index 0000000..4de451b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.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 new file mode 100644 index 0000000..a4e97a1 Binary files /dev/null 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-events-rule.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-events-rule.png new file mode 100644 index 0000000..de83859 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-events-rule.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.png new file mode 100644 index 0000000..89f6245 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.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 new file mode 100644 index 0000000..b16c295 Binary files /dev/null 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 new file mode 100644 index 0000000..f6b702d Binary files /dev/null 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-name.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-name.png new file mode 100644 index 0000000..3b749cb Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-name.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 new file mode 100644 index 0000000..f6385dd Binary files /dev/null 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 new file mode 100644 index 0000000..02a9a80 Binary files /dev/null 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/enabled-ecpu.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png new file mode 100644 index 0000000..02a9a80 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/enabled-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 new file mode 100644 index 0000000..0fec12f Binary files /dev/null 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 new file mode 100644 index 0000000..0f32146 Binary files /dev/null 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-rules.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-rules.png new file mode 100644 index 0000000..48120ee Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-rules.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 new file mode 100644 index 0000000..5bdca95 Binary files /dev/null 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/notifications-events-intro.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png new file mode 100644 index 0000000..5b4be29 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png new file mode 100644 index 0000000..4f245a3 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png new file mode 100644 index 0000000..eb55e58 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.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 new file mode 100644 index 0000000..2de56d3 Binary files /dev/null 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 new file mode 100644 index 0000000..f361b4a Binary files /dev/null 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 new file mode 100644 index 0000000..0cf3716 Binary files /dev/null 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 new file mode 100644 index 0000000..360a51e Binary files /dev/null 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/configure-notifications-for-exascale-ecpu/images/subscription-active.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-active.png new file mode 100644 index 0000000..4b198b0 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-active.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png new file mode 100644 index 0000000..b56b50f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png new file mode 100644 index 0000000..2814d23 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md new file mode 100644 index 0000000..94ea782 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md @@ -0,0 +1,77 @@ +# Create Thin Clone of an Oracle Pluggable Database (PDB) + +## Introduction + +This lab walks you through how to create thin clone of an Oracle Pluggable Database on the Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Console. +  + +**Estimated Time:** ***10 minutes*** + +### **Objectives** + +- After completing this lab, you should be able to create thin clone of an Oracle Pluggable Database on the Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Console. + + +### **Prerequisites** + +This lab requires the completion of the following: + +* Successful creation of a VM Cluster on Exadata Database Service on Exascale Infrastructure. +* Successful creation of Container Database on the VM Cluster, which will also includes the initial PDB. +* Completion of **Lab 2** + +## Task 1: Create Thin clone of a Pluggable Database + + +1. In the **Pluggable Database Details** page, click **Clone** to initiate the **Clone PDB** action. + +![Initiate Clone Pluggable Database Action](./images/click-clone-pdb.png "Initiate Clone Pluggable Database Action") + + > **Note:** This will cause the **Clone Pluggable Database** configuration page to be displayed. + +2. Configure clone PDB options and select **Enable Thin Clone**. + + In the **Clone Pluggable Database** configuration page, select **Local Clone** as PDB clone type. + + Enter the information to configure the new PDB. + + * Enter **PDB Name**. + * Enter **Database TDE wallet password**. + +![Initiate Clone Pluggable Database Action](./images/clone-pdb-local.png "Initiate Clone Pluggable Database Action") + + Enable thin clone. + * You can select **Take a backup of the PDB immediately after cloning** + * ***Enable Thin Clone*** checkbox will be checked by default. Unchecking this box will create a thick clone instead of a thin clone of a pluggable database. + * Click ***Clone pluggable database*** to start the clone provisioning process. + +![Configure Clone options and check box to Enable Thin Clone](./images/enable-thin-clone.png "Configure Clone options and check box to Enable Thin Clone") + + > **Note:** The thin PDB clone will be created and presented as a new PDB. + +![New Thin Clone PDB Details page](./images/thin-clone-available.png " ") + +3. List all of the PDBs in the CDB. From the **Pluggable Database Details** page, click **Database Details** in the breadcrumb path. + +![New Thin Clone PDB Details page](./images/cdb-details-path.png " ") + + Under **Resources**, click **Pluggable databases**. + +![New Thin Clone PDB Details page](./images/list-of-pdb.png " ") + + > **Note:** This will cause a list of available pluggable databases to be displayed and that the thin clone PDB is listed, as just another PDB. + + +***Congratulations!!!*** You may now **proceed to the next lab**. + + +## Learn More + +* Click [here](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/exadata/doc/ecc-create-first-db.html) to learn more about Creating an Oracle Pluggable Database on Exadata Database Service on Exascale Infrastructure. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, April 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/cdb-details-path.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/cdb-details-path.png new file mode 100644 index 0000000..50a13e6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/cdb-details-path.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/click-clone-pdb.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/click-clone-pdb.png new file mode 100644 index 0000000..583239f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/click-clone-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/clone-pdb-local.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/clone-pdb-local.png new file mode 100644 index 0000000..1739f8a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/clone-pdb-local.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/enable-thin-clone.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/enable-thin-clone.png new file mode 100644 index 0000000..50e85ef Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/enable-thin-clone.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-of-pdb.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-of-pdb.png new file mode 100644 index 0000000..61e205b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-of-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-cdb-clone.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-cdb-clone.png new file mode 100644 index 0000000..2177e68 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-cdb-clone.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-pdb-clone.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-pdb-clone.png new file mode 100644 index 0000000..70ded7a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-pdb-clone.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/thin-clone-available.png b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/thin-clone-available.png new file mode 100644 index 0000000..11fcb6a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/create-thin-clone-pdb-on-exascale/images/thin-clone-available.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 new file mode 100644 index 0000000..9539ba6 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md @@ -0,0 +1,286 @@ +# Discover Environment Details using OCI API + + +## Introduction + +This lab walks you through the steps to discover how to navigate to the Exadata Database Service on Exascale Infrastructure and discover the environment details for the Exadata VM Cluster, Container Database, Pluggable Database, and the Exascale Storage Vault using the OCI API. + +**Estimated Time:** ***10 minutes*** + +### Objectives + +- After completing this lab, you should be able to discover Exadata Database Service on Exascale Infrastructure environment details using the OCI API. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab 1** +* Required IAM Policies to [**Access OCI Cloud Shell**](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cloudshellintro.htm#Required_IAM_Policy). + +## 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***. + + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + +2. Select your ***Compartment***, and Select your **VM Cluster**. + + ![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") + + >**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***. + + ![expand actions to show open code editor](./images/expand-code-editor.png "expand actions to show open code editor") + + 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***. + + +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. + + ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") + + + Paste the VM Cluster OCID value in your code or text editor. + + + +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)* + + ``` + + + oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state",CompartmentOCID:"compartment-id"}' + + + ``` + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***exadb-vm-cluster*** ***get*** ***--exadb-vm-cluster-id*** ***{VMClusterID}*** ***--query*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exadb-vm-cluster*** is the **resource type** for the Exadata VM Cluster on Exascale Infrastructure. + * ***get*** is the **action** to get information about the Exadata VM Cluster on Exascale Infrastructure. + * ***--exadb-vm-cluster-id*** is the **parameter** for the ***VM Cluster OCID***. + * ***--query*** is the query parameter used for structured query options to display the specific VM Cluster data fields and values for the ***Display Name***, ***Enabled ECPUs***, ***Lifecycle state***, and ***Compartment OCID*** + + After running the command, you will see similar output below. + + ![show vm cluster details with compartment id](./images/show-vm-cluster-details-comp-ocid.png "show vm cluster details with compartment id") + + Pay attention to the following VM Cluster details from the command output: + * ***CompartmentOCID*** + * **Display Name** + * **Enabled ECPUs** + * **Lifecycle State** + + Copy the ***CompartmentOCID*** value and paste it value and paste it in your code or text editor. + +## Task 2: List the available Database Homes in a compartment using REST API + +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*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10" + + + ``` + + **Description:** + + The REST API Request is: ***GET /20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10*** + + **Where:** + + * ***dbHomes*** is the **resource type** for the Oracle Database Home. + * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to list the available Database Homes. + * ***lifecycleState=AVAILABLE*** is the **query** to include a filter to return only Database Homes with the lifecycle state of Available. + * ***limit*** is the **query** to define the maximum number of items to return per page + + + +2. You will see a similar output as below. + + ![list database homes](./images/list-dbhome.png "list database homes") + + Copy the **DB Home OCID** value from the ***"id"*** field and paste it in your notepad or text editor. + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the database homes in the specified compartment. + + +## Task 3: List the available Container Databases in a specified compartment using OCI CLI + +1. Run the OCI CLI Command to list the available Container Databases in a specified compartment. + + >**Note:** Replace ***{CompartmentOCID}*** with the Compartment OCID obtained from ***Task 1 Step 5*** + + ``` + + + oci db database list --compartment-id {CompartmentOCID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table + + + ``` + + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***database*** ***list*** ***--compartment-id*** ***{CompartmentOCID}*** ***--query*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***database*** is the **resource type** for the Container Database (CDB). + * ***list*** is the **action** to lists all Container Databases (CDBs) in a specified Compartment. + * ***--compartment-id*** is the **parameter** for the ***Compartment OCID***. + * ***--query*** is the query parameter used for structured query options to display the specific Container Database data fields and values for the ***Container Database Name***, ***Container Database OCID***, and ***Lifecycle state*** + + After running the command, you will see similar output below. + + ![show list of container databases](./images/list-cdb.png "show list of container databases") + + Copy the ***ContainerDatabaseOCID*** value and paste it in your code or text editor. + +## Task 4: List the available Pluggable Databases (PDBs) in a Container Database (CDB) using REST API + +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*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" + + + ``` + + **Description:** + + The REST API Request is: ***GET /20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10*** + + **Where:** + + * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB). + * ***databaseId*** is the **Container Database OCID**. + * ***limit*** is the **query** to define the maximum number of items to return per page + + After running the command, you will see similar output below. + + ![show list of pluggable databases](./images/list-pdbs.png "show list of pluggable databases") + + Look for the field ***pdbName*** and copy the **PDB OCID** value from the ***"id"*** field and paste it in your notepad or text editor. + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the Pluggable Databases in the Container Database. + +## Task 5: Create Thin Clone of Pluggable Database (PDB) using REST API + +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"*** + * **pdbAdminPassword:** ***Enter your PDB admin password*** + * **tdeWalletPassword:** ***Enter your TDE wallet password*** + * **containerDatabaseId:** ***"{ContainerDatabaseOCID}"*** - Replace ***{ContainerDatabaseOCID}*** with **CDB OCID** obtained from ***Task 3*** + * **pdbCreationTypeDetails:** + * **creationType:** ***"LOCAL\_CLONE\_PDB"*** + * **sourcePluggableDatabaseId:** ***{PluggableDatabaseOCID}*** - Replace ***{PluggableDatabaseOCID}*** with **PDB OCID** obtained from ***Task 4*** + * **isThinClone:** ***"true"*** + + ![open MyThinClonePDB.json](./images/my-thin-clone-pdb-json.png "open MyThinClonePDB.json") + +2. Make an OCI REST API call to create thin clone of pluggable database and starts a pluggable database (PDB) in the specified container database (CDB) by running the **OCI RAW-REQUEST** command below: + + Open the **OCI Cloud Shell** tab and run the following command + + >**Note:** Replace the API endpoint region "***{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 + + + + ``` + + **Description:** + + The REST API Request is: ***POST /20160918/pluggableDatabases*** + + **Where:** + + * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB). + * ***--request-body*** contains the **Create Pluggable Database Details** resource stored in the JSON file ***MyThinClonePDB.json***. + + After running the command, you will see similar output below. + + ![create thin clone using REST API](./images/create-thin-clone-pdb.png "create thin clone using REST API") + + You will see that the Pluggable Database status ***"lifecycle-state"*** is ***PROVISIONING***. + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to start the provisioning of the thin clone of a pluggable database. + +## Task 6: List Exascale Storage Vault using REST API + +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*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/exascaleDbStorageVaults?compartmentId={CompartmentOCID}&limit=10" + + + + ``` + + **Description:** + + The REST API Request is: ***GET /20160918/exascaleDbStorageVaults*** + + **Where:** + + * ***exascaleDbStorageVaults*** is the **resource type** for the Exascale Storage Vault. + * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to get a list of the available Exascale Storage Vaults. + + After running the command, you will see similar output below. + + ![list exascale storage vault](./images/list-exascale-storage-vault-in-a-compartment.png "list exascale storage vault") + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of the available Exascale Storage Vaults in a specified comparment. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, March 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png new file mode 100644 index 0000000..fbc180d Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png new file mode 100644 index 0000000..f78c5d4 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png new file mode 100644 index 0000000..06ac712 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.png new file mode 100644 index 0000000..f9f4ff7 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.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 new file mode 100644 index 0000000..a4e97a1 Binary files /dev/null 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 new file mode 100644 index 0000000..cdf1766 Binary files /dev/null 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 new file mode 100644 index 0000000..f2d59b2 Binary files /dev/null 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/expand-code-editor.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/expand-code-editor.png new file mode 100644 index 0000000..e7eb43a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/expand-code-editor.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png new file mode 100644 index 0000000..7ec2baa Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png new file mode 100644 index 0000000..a069635 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png new file mode 100644 index 0000000..2607a0f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.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 new file mode 100644 index 0000000..cce8914 Binary files /dev/null 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 new file mode 100644 index 0000000..77755d7 Binary files /dev/null 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-dbhomes.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhomes.png new file mode 100644 index 0000000..bbf159f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhomes.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 new file mode 100644 index 0000000..13232b0 Binary files /dev/null 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 new file mode 100644 index 0000000..a3964a4 Binary files /dev/null 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 new file mode 100644 index 0000000..60eeb0f Binary files /dev/null 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/my-worksheet-sample.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-worksheet-sample.png new file mode 100644 index 0000000..5a448df Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/my-worksheet-sample.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png new file mode 100644 index 0000000..5bdca95 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png new file mode 100644 index 0000000..7010848 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png new file mode 100644 index 0000000..bcf3f50 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png new file mode 100644 index 0000000..714b5b1 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png new file mode 100644 index 0000000..a716027 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.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 new file mode 100644 index 0000000..e8c9d1b Binary files /dev/null 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/discover-env-details-on-exascale/discover-env-details-on-exascale.md b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/discover-env-details-on-exascale.md new file mode 100644 index 0000000..cdc4fb7 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/discover-env-details-on-exascale.md @@ -0,0 +1,168 @@ +# Discover Oracle Exadata Database Service on Exascale Infrastructure Environment Details using OCI Console + + +## Introduction + + This lab walks you through the steps to discover how to navigate to the Exadata Database Service on Exascale Infrastructure and discover the environment details for the Exadata VM Cluster, Container Database, Pluggable Database, and the Exascale Storage Vault using the OCI Console. + +**Estimated Time:** ***5 minutes*** + +### Objectives + +- After completing this lab, you should be able to discover Exadata Database Service on Exascale Infrastructure environment details using the OCI Console. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab 1** + +## Task 1: Discover Exadata VM Cluster Details + +1. **Navigate to the Exadata Database Service on Exascale Infrastructure:** + * Open the **Navigation Menu**. + * Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + + ![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ") + +2. **Navigate to the list of availbale cloud Exadata VM cluster in your assigned compartment:** + * In the left rail, **VM Clusters** is selected by default. + * Under **List Scope**, Select your assigned compartment. + * Then **click on your clusters highlighted name that has a State of Available** to view the **VM Cluster Details page**. + + ![Select Compartment and VM Cluster where Container Database will reside](./images/select-compartment-and-vm-cluster.png" ") + +1. On the **VM Cluster Details** page ***Discover the available VM Cluster information:*** + * In the **General Information** Section you can find the following key items: + * What Compartment the VM Cluster is in. + * The Availability Domain of the VM Cluster. + * The OCID of the VM Cluster. + * The License Type selected for the VM Cluster. + * In the **Maintenance** Section you can find: + * Information about scheduled Node Maintenance Reboots. + * The **Resource Allocation** Section contains the following Cluster Wide Metrics: + * The numer of Reserved ECPUs available to conduct online scale up operation. + * The number of Enabled ECPUs across the VM Cluster. + * The amount of Memory allocated to the VMs across the VM Cluster. + * The total VM File Ystem Storage allocated to the VMs across the VM Cluster + * In the **Exascale Database Storage** Section you will find the followign key items: + * The location of the Exascale Storage Vault servicing this VM Cluster. + * The amount of Exascale database storage that was allocated and how much is free. + * The **Network** Section contains the followign key pieces of networking information: + * The nameof the VCN being used for the subnets and routing rules. + * The name of the Client SUbnet and Backup Subnet selected for this VM Cluster. + * The SCAN IPs, SCAN DNS name, and SCAN listener port. + * In the **Version** Section of the page, you will find the followign key items: + * The Exadata Image Version. + * The Grid Infrastructure Version. + * A link to view any available Updates required to keep your system up to date. + + ![Review Information on VM Cluster Details page](./images/vm-cluster-details-page.png" ") + +4. On the left side of the page, under the **Resources** section: ***Discover the additional VM Cluster resources:*** + * You can click the **Container Database** link to see a list of available databases. + ![VM Cluster Details page Resources Section Container Databases](./images/vm-cluster-details-page-resource-section-cdb-list.png" ") + * You can click the **Database Homes** link to see a list of the existing database homes. + ![VM Cluster Details page Resources Section Database Homes](./images/vm-cluster-details-page-resource-section-dbhome-list.png" ") + * You can click the **Virtual Machines** link to see a list of the Virtual Machines that are allocated to your VM Cluster + ![VM Cluster Details page Resources Section Virtual Machines](./images/vm-cluster-details-page-resource-section-vm-list.png" ") + + + +## Task 2: Discover Container Database (CDB) & Pluggable Database (PDB) Details + +1. Navigate to the **Container Database Details** page. + * On the left side of the page, under the **Resources** section: Select **Container Database** link. + * From the List of existing Container Databases in your compartment, select the name of your **Container Database that has a State of** ***Available*** to view the **Container Database Details** page. + + ![Navigate to Container Database Details page](./images/vm-cluster-details-page-to-cdb.png" ") + +2. On the **Container Database Details** page ***Discover the following Container Database Information*** + + * On the **Container Database (CDB) Details** page, you can see a list of actions that can be performed, such as obtaining the connection string, and Restoring, Configuring Automatic Backups, Creating a Database from a Backup, and more actions. + * In the ***General Information*** Section you can find the following key items: + * The Lifecycle state of the Container Database. + * The OCID of the Container Database. + * The Database Unique Name and Oracle SID Prefix of the Container Database. + * In the ***Database Version*** Section of the page, you will find the followign key items: + * The name of the database software image if one was used to creade the Container Database. + * The name of the database home that has a link so that you can see what other databases share this home. + * The Database version for the Container Database. + * You will also find a link to view any available Updates required to keep your system up to date. + * In the ***Backup*** Section you can find: + * If your container database is configured for Automatic Backups. + * You can also see if your backups are healthy and know your exact Data Loss exposure. + * In this section, you can also see when your last backup was, when the next one is scheduled for, and how much storage you are using to backup this container database. + * The Backup section also includes information about the Backup Destination being used, and identifes the protection poicy being used and if realtime protection feature of the Recovery service is in use. + * The ***Data Guard*** Section of the page is pretty straight forward: + * Identifes if the Container Database has a peer Data Guard enabled for it or not. + * The ***Associated Services*** Section of the page: + * Informs you if the (optional) **Operations Insights** feature has been enabled for the container database. + * The ***Encryption*** Section of the page: + * Provides you with information about the type of encryption key management that is being used. + + ![Container Database Details page](./images/container-database-details-page.png " ") + + +3. On the left side of the page, under the **Resources** section: ***Discover the additional Container Database resources:*** + * You can click the **Backups** link to see a list of available database backups. + ![VM Cluster Details page Resources Section Backups](./images/container-database-details-page-resource-section-backup-list.png" ") + * You can click the **Data Guard Association** link to see if this database has a Data Guard Peer. + ![VM Cluster Details page Resources Section Data Guard Association ](./images/container-database-details-page-resource-section-dg-list.png" ") + * You can click the **Pluggable Database** link to see a list of the Pluggable Databases that have been created in this Container Database. + ![VM Cluster Details page Resources Section Pluggable Databases ](./images/container-database-details-page-resource-section-pdb-list.png" ") + + +4. Now lets ***Discover Details about our Pluggable Databases*** + * From the **Resources** Section of the **Container Database Details** page, Click on the **Pluggable Database** Link + * Select the ***name of your Pluggable Database*** link to navigate the **Pluggable Database Details** page. + + ![Navigate from CDB to PDB](./images/navigate-cdb-to-pdb.png " ") + +5. On the **Pluggable Database Details** page ***Discover the following Pluggable Database Information*** + * On the ***Pluggable Database (PDB) Details*** page, you can see a list of actions that can be performed, such as obtaining the connection string, and Cloning, Starting, Stopping, Relocating, and Restoring the PDB. + * In the ***General Information*** Section you can find the following key items: + * The Lifecycle state of the Pluggable Database. + * The OCID of the Pluggable Database. + * The linked Name of the Container Database where this PDB resides. + * In this section, you wil also see information indicating if the PDB is a Refreshable Clone and its Open Mode role. + * The ***Associated Services*** Section of the page: + *Informs you if the (optional) Operstions Insights feature has been enabled for the pluggable database. + + ![Pluggable Database Details page](./images/pluggable-database-details-page.png " ") + +## Task 3: Discover Exascale Storage Vault Details + +1. Navigate from the **Pluggable Database Details** page to the **VM Cluster Details** page. + + * On the **Pluggable Database Details** page, you will see the navigation bread crumb links. ***Click on the VM Cluster Details*** link. + + ![VM Cluster Details page - via breadcrumb link](./images/pdb-to-vmc-via-breadcrumb-link.png " ") + +2. On the **VM Clusters** page, click on the ***Exascale Storage Vault name*** for your VM Cluster. +
This will launch the **Exascale Storage Vault Details** page. + ![Navigate from VM Cluster Details page to Exascale Storage Vault](./images/navigate-vmc-details-to-exascale-storage-vault.png " ") + + +3. On the **Exascale Storage Vault Details** page ***Discover the following Exascale Storage Vault Information*** + * On the **Exascale Storage Vault Details** page, you can see a list of actions that can be performed, such as scaling the storage vault or moving the Vault to another compartment. + * In the **General Information** Section of the **VM Cluster Information** tab, you can find the following key items: + * The Lifecycle state of the Exascale Storage Vault. + * What Compartment the Exascale Storage Vault is in. + * The Availability Domain of the Exascale Storage Vault. + * The OCID of the Exascale Storage Vault. + * In the **Exascale Database Storage** Section you will find: + * The amount of Exascale database storage that was allocated and how much is free. + * On the left side of the page, under the **Resources** section: + * You can click on the **Associated VM Clusters** link to see a list of VM Clusters that are using this storage vault. + + ![Exascale Storage Vault Details page](./images/exascale-storage-vault-details-page.png " ") + +***!!! Congratulations:*** You may now **proceed to the next lab**. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, March 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png new file mode 100644 index 0000000..476211c Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png new file mode 100644 index 0000000..9476315 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png new file mode 100644 index 0000000..c2609d6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png new file mode 100644 index 0000000..11e3720 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png new file mode 100644 index 0000000..590cb48 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png new file mode 100644 index 0000000..30dd6d2 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png new file mode 100644 index 0000000..039d988 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png new file mode 100644 index 0000000..fe438a3 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png new file mode 100644 index 0000000..7000336 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png new file mode 100644 index 0000000..e71ceff Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png new file mode 100644 index 0000000..6cc6552 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png new file mode 100644 index 0000000..3eef07b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png new file mode 100644 index 0000000..cac5e82 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png new file mode 100644 index 0000000..7a49744 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png new file mode 100644 index 0000000..7f2bd98 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png new file mode 100644 index 0000000..c5096e6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png new file mode 100644 index 0000000..cd938ae Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png new file mode 100644 index 0000000..945c591 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png new file mode 100644 index 0000000..88a55c8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.png b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.png new file mode 100644 index 0000000..6f88e0e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.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 new file mode 100644 index 0000000..4d75104 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/get-started-gs/get-started-gs.md @@ -0,0 +1,75 @@ +# Get started - Connect to Oracle Cloud Tenancy + + +## **Introduction** + +Oracle Cloud is the industry's broadest and most integrated cloud provider, with deployment options ranging from the public cloud to your data center. Oracle Cloud offers best-in-class services across Software as a Service (SaaS), Platform as a Service (PaaS), Database as a Service (DBaaS), and Infrastructure as a Service (IaaS). + +**Estimated Time:** ***5 minutes*** + +**Types of Cloud Accounts that can be used for this workshop:** + + * ***Oracle Cloud Paid Account***: When your tenancy is provisioned, Oracle sends an email to the default administrator at your company with the sign-in credentials and URL. This administrator can then create a user for each person who needs access to the Oracle Cloud. Check your email or contact your administrator for your credentials and account name. + + * ***Oracle provided Cloud Workshop Account***: This type of environment can be obtained by engaging with your Sales Engineer to coordinate obtaining approval to obtain an Event Code which will provide temporary access to an Oracle provided environment. + + + + +### **Objectives** + +- For this workshop we will learn how to login to a tenancy using the **Oracle Cloud Paid Account**. + + +### **Prerequisites** + +- An existing Microsoft Azure subscription. + +- Oracle Cloud Infrastructure (OCI) Service Limits approved in the region you want to provision Oracle Exadata Database Service. + +* **Cloud Account Name** - Secure your Oracle Cloud tenancy name that will be used for this workshop. + +* **Username** - Secure your personal or assigned username for this workshop + +* **Password** - Secure your personal or assigned password for this workshop + +* **Required Service Limits** - If you are using a personal Oracle Cloud tenancy, you will need to ensure that you have service limits assigned for the following resources to run the workshop: + + | 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-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 + + +* **Required IAM Policy for Oracle Exadata Database Service on Exascale Infrastructure** - Configure the [**required Identity Access Management (IAM) Policy**](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/preparing-for-exadb-xs-deployment.html#GUID-EA03F7BC-7D8E-4177-AFF4-615F71C390CD) for provisioning Oracle Exadata Database Service on Exascale Infrastructure systems + + +## Task 1: Log in to Oracle Cloud Tenancy + +1. Go to [**cloud.oracle.com**](https://cloud.oracle.com/?region=us-sanjose-1&tenant=livelabs4exadb) and enter your **Cloud Account Name** *(**Cloud Tenancy**)*. + + ![select cloud tenancy](./images/select-cloud-tenancy.png " ") + + +2. Enter your assigned **username** and **password** and click **Sign In** + + ![cloud tenancy sign-in](./images/cloud-tenancy-sign-in.png " ") + +3. You are now signed in to Oracle Cloud! + + ![oci login landing page](./images/oci-login-landing-page.png " ") + + + +You may now **proceed to lab 1**. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, March 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png new file mode 100644 index 0000000..4d9a2b5 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/oci-login-landing-page.png b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/oci-login-landing-page.png new file mode 100644 index 0000000..4fa7340 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/oci-login-landing-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/select-cloud-tenancy.png b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/select-cloud-tenancy.png new file mode 100644 index 0000000..53bae60 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/get-started-gs/images/select-cloud-tenancy.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png new file mode 100644 index 0000000..fdff4f7 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png new file mode 100644 index 0000000..9f2aa0c Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/introduction.png b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/introduction.png new file mode 100644 index 0000000..f8249c3 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/introduction.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png new file mode 100644 index 0000000..d345a1e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png differ 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 new file mode 100644 index 0000000..d6e4357 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/introduction-gs/introduction-gs.md @@ -0,0 +1,51 @@ +# Introduction + +## 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. + +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. + +The workshop exercises are designed to provide you with operational experience creating & managing the Exascale Storage Vault, the Exadata VM Cluster, Container Databases, Pluggable Databases, and thin clones that leverage the Exascale technology stack. + +You will also learn how to configure alerts and notifications for events that we will trigger during some of the workshop lab tasks. + +Don’t miss your chance to be one of the first to gain hand-on experience with Exadata & the Exascale technology stack. + + +**Estimated Workshop Time:** ***3 hours 15 Minutes*** + + +### **Oracle Exadata Exascale: World’s Only Intelligent Data Architecture for Cloud** + +Users can now provision Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure. Exascale is a multitenant, hyper-elastic intelligent data architecture that delivers all the advantages of Exadata with all the benefits of modern clouds. The Exascale intelligent storage cloud and a pool of Exascale database-optimized compute provide scalable shared resources in the cloud while still meeting even the most demanding workload requirements. You can start with a small VM cluster and small amount of storage and easily scale as needs grow. With the introduction of Exascale infrastructure, the benefits of Oracle Exadata Database Service are now available for workloads at any scale. + +Exadata Exascale is Oracle’s revolutionary multitenant architecture that combines the intelligence of Exadata with all the benefits of modern clouds. This loosely-coupled architecture incorporates the Exascale intelligent storage cloud and a pool of Exascale database-optimized compute to provide hyper-elasticity while meeting even the most demanding workload requirements. + +![introduction](./images/introduction.png " ") + +When running Exadata Database Service on Exascale Infrastructure, you have access to its intelligent capabilities across your application portfolio. Database-optimized intelligent infrastructure runs AI, analytics, mission-critical OLTP, and developer workloads faster and more efficiently, reducing overall IT costs. Some of these capabilities include: + +* Intelligent AI: The combination of AI Smart Scan with Exadata System Software 24ai offloads key AI Vector Search operations to the Exascale intelligent storage cloud, enabling massive amounts of vector data to be searched up to 30X faster. + +* Intelligent analytics: The combination of intelligent columnarization and Smart Scan make hundreds or thousands of processing cores in the Exascale intelligent storage cloud available to process any SQL query. + +* Intelligent OLTP: Exascale’s intelligent architecture automatically tiers data between DRAM, flash, and disk enabling low-latency, high-throughput Remote Direct Memory Access (RDMA) to frequently accessed data and delivers the performance of DRAM, the IOPS of flash, and the capacity of disk. + +* Database-aware intelligent clones:The Exascale intelligent storage cloud uses redirect-on-write snapshot technology to instantly create space-efficient database clones from read-write sources. + +Starting today, you can enjoy Exadata Database Service benefits at a lower entry cost for smaller, but no less critical, databases. Exadata Database Service on Exascale Infrastructure bridges the gap between dedicated Exadata infrastructure and virtual machines on shared commodity infrastructure. It extends Exadata’s advantages to every organization in every industry, regardless of size or workload. + +You can start small using virtual machine (VM) cluster configurations with as little as 8 ECPUs and 22 GB of memory per VM, and 300 GB of intelligent database storage. You can easily scale up the number of ECPUs and number of VMs in the cluster, and then shrink them when you don’t need them. To ensure ECPU capacity is available when you need it, you can reserve ECPUs at a nominal cost. + +You may now **proceed to the next lab** + +## Learn More + +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/index.html) to learn more about the Exadata Database Service on Exascale Infrastructure. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, Mar 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/azure-vm-cluster-go-to-oci-link.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/azure-vm-cluster-go-to-oci-link.png new file mode 100644 index 0000000..9a0ce13 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/azure-vm-cluster-go-to-oci-link.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-create-container-db.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-create-container-db.png new file mode 100644 index 0000000..bf637d7 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-create-container-db.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb-details.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb-details.png new file mode 100644 index 0000000..2302739 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb.png new file mode 100644 index 0000000..b421cd8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/click-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/configure-db-backup.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/configure-db-backup.png new file mode 100644 index 0000000..1e3f3fd Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/configure-db-backup.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb-details.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb-details.png new file mode 100644 index 0000000..6e03796 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb.png new file mode 100644 index 0000000..648071f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/create-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/created-cdb.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/created-cdb.png new file mode 100644 index 0000000..fd2de0e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/created-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-administrator-credentials.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-administrator-credentials.png new file mode 100644 index 0000000..b2aed00 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-administrator-credentials.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-container-db-tag.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-container-db-tag.png new file mode 100644 index 0000000..766378a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-container-db-tag.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-database-home.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-database-home.png new file mode 100644 index 0000000..2c1facf Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/enter-database-home.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/oci-vm-cluster-details-page.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/oci-vm-cluster-details-page.png new file mode 100644 index 0000000..1ab4538 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/oci-vm-cluster-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/provision-database.md b/exadata-database-service-at-azure-xs-get-started/provision-database/images/provision-database.md new file mode 100644 index 0000000..d316514 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/provision-database/images/provision-database.md @@ -0,0 +1,104 @@ +# Create Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure + + +## Introduction + +This lab walks you through how to create an Oracle Database on the Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Portal. +  + +**Estimated Time:** ***30 minutes*** + +### Objectives + +- After completing this lab, you should be able to create an Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Console. + +### Prerequisites + +* A provisioned Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure Instance. + +## Task 1: Provision an Oracle Database + +1. Go to the Oracle Exascale VM cluster, click **Overview** and **Go to OCI**. + + ![Image showing the option to login to OCI](./images/azure-vm-cluster-go-to-oci-link.png "Image showing the option to login to OCI") + +2. Log in to the OCI Console and navigate to **VM Cluster Details**. + + ![Image showing VM Cluster details page](./images/oci-vm-cluster-details-page.png "Image showing VM Cluster details page") + +3. Under **Resources**, select **Container databases** and click **Create container database**. + + ![Image showing create CDB](./images/create-cdb.png "Image showing create CDB") + +4. In the **Create container database** page, enter the following information. + + - **Basic information for container database:** + + - **Provide the database name:** Enter a name for the database. + - **Provide a unique name for the database (Optional):** Enter a unique name for the database. + - **Select a database version:** Select the database version available. + - **Provide a PDB name (Optional):** Enter the name of the first PDB to be created. + + ![Image showing the basic container database information to enter](./images/create-cdb-details.png "Image showing the basic container database information to enter") + + - **Specify a database Home:** + + - **Database Home source:** Select to use an **existing Database Home** or **Create a new Database Home**. + - **Database Home display name:** Use the default database home name or enter a database home name. + - **Change Database Image (Optional):** Determines what Oracle Database version is used for the database. By default, the latest Oracle-published database software image is selected. Select to use an older Oracle-published image or a custom database software image that you have created in advance. + + ![Image showing Database Home selection](./images/enter-database-home.png "Image showing Database Home selection") + + - **Create administrator credentials:** + + - **Password:** Password must be 9 to 30 characters and contain at least 2 uppercase, 2 lowercase, 2 special, and 2 numeric characters. The special characters must be `\`, `_`, `#`, or `-`. + - **Confirm Password:** Enter the same password. + + ![Image showing Administrator credentials to enter](./images/enter-administrator-credentials.png "Image showing Administrator credentials to enter") + +5. In the **Configure Database backups** page, if you accept the defaults setting, the database will be backed up using the Oracle Database Autonomous Recovery Service. You have the option to use OCI Object Storage by changing the **Backup destination**. The database will not be backed up if you deselect **Enable automatic backups**. Automatic backups can be enabled after the container database is created. + + ![Image showing database backup configuration options](./images/configure-db-backup.png "Image showing database backup configuration options") + +6. Click **Show advanced options** and enter the following information. + + - **Management:** You can add **Oracle SID prefix (_Optional_)** and select the **Character set** and **National Character set**. + + ![Image showing Oracle SID and Character set selection](./images/select-sid-character-set.png "Image showing Oracle SID and Character set selection") + + - **Encryption:** Configure key management, you have options to manage database keys. Select **Use Oracle-managed keys** to manage database keys using the wallet or select **Use customer-managed keys** to manage database keys using OCI Vaults. + + ![Image showing console connection copy SSH string options](./images/select-encryption-option.png "Image showing console connection copy SSH string options") + + - **Tags:** Apply free-form or defined tags to this resource. + + ![Image showing the option to add container database tags](./images/enter-container-db-tag.png "Image showing the option to add container database tags") + +7. Click **Create container database**. + + ![Image showing the option confirm creation of container database](./images/click-create-container-db.png "Image showing the option confirm creation of container database") + + Once the provisioning process of the container database is completed, the state of the container database will show as **Available**. + + ![Image showing created container database](./images/created-cdb.png "Image showing created container database") + +8. In the **Container Database details** page, under **Resources**, select **Pluggable Databases**. + + ![Image showing created pdb](./images/click-pdb.png "Image showing created pdb") + + Click **Pluggable Database** to view the details of the pluggable database. + + ![Image showing created pdb](./images/click-pdb-details.png "Image showing created pdb") + +***!!! Congratulations:*** You may now **proceed to the next lab**. + + +## Learn More + +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/index.html) to learn more about the Exadata Database Service on Exascale Infrastructure. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, Mar 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-encryption-option.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-encryption-option.png new file mode 100644 index 0000000..3b12a4c Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-encryption-option.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-sid-character-set.png b/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-sid-character-set.png new file mode 100644 index 0000000..b43659b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-database/images/select-sid-character-set.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-database/provision-database.md b/exadata-database-service-at-azure-xs-get-started/provision-database/provision-database.md new file mode 100644 index 0000000..89b564d --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/provision-database/provision-database.md @@ -0,0 +1,102 @@ +# Create Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure + + +## Introduction + +This lab walks you through how to create an Oracle Database on the Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Portal. +  + +**Estimated Time:** ***30 minutes*** + +### Objectives + +- After completing this lab, you should be able to create an Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the OCI Console. + +### Prerequisites + +* A provisioned Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure Instance. + +## Task 1: Provision an Oracle Database + +1. Go to the Oracle Exascale VM cluster Overview page, In the OCI Database URL, click the ***Go to OCI*** link. + +![Image showing the option to login to OCI](./images/azure-vm-cluster-go-to-oci-link.png "Image showing the option to login to OCI") + +2. Log in to the OCI Console and navigate to **VM Cluster Details**. + +![Image showing VM Cluster details page](./images/oci-vm-cluster-details-page.png "Image showing VM Cluster details page") + +3. Under **Resources**, select **Container databases** and click ***Create container database***. + +![Image showing create CDB](./images/create-cdb.png "Image showing create CDB") + +4. In the **Create container database** page, enter the following information. + +* **Basic information for container database:** + * **Provide the database name:** Enter a name for the database. + * **Provide a unique name for the database ***(Optional)***:** Enter a unique name for the database + * **Select a database version:** Select the database version available. + * **Provide a PDB name ***(Optional)***:** Enter the name of the first PDB to be created. + +![Image showing the basic container database information to enter](./images/create-cdb-details.png "Image showing the basic container database information to enter") + +* **Specify a database Home:** + * **Database Home source:** Select to use an ***existing Database Home*** or ***Create a new Database Home***. + * **Database Home display name:** Use the default database home name or enter a database home name. + * **Change Database Image ***(Optional)***:** Determines what Oracle Database version is used for the database. By default, the latest Oracle-published database software image is selected. Select to use an older Oracle-published image or a custom database software image that you have created in advance. + +![Image showing Database Home selection](./images/enter-database-home.png "Image showing Database Home selection") + +* **Create administrator credentials:** + * **Password:** Password must be 9 to 30 characters and contain at least 2 uppercase, 2 lowercase, 2 special, and 2 numeric characters. The special characters must be `\`, `_`, `#`, or `-`. + * **Confirm Password:** Enter the same password. + +![Image showing Administrator credentials to enter](./images/enter-administrator-credentials.png "Image showing Administrator credentials to enter") + + +5. In the **Configure Database backups** page, if you accept the defaults setting, the database will be backed up using the Oracle Database Autonomous Recovery Service. You have the option to use OCI Object Storage by changing the **Backup destination**. The database will not be backed up if you deselect **Enable automatic backups**. Automatic backups can be enabled after the container database is created. + +![Image showing database backup configuration options](./images/configure-db-backup.png "Image showing database backup configuration options") + +6. Click **Show advanced options** and enter the following information. + + - **Management:** You can add **Oracle SID prefix (_Optional_)** and select the **Character set** and **National Character set**. + +![Image showing Oracle SID and Character set selection](./images/select-sid-character-set.png "Image showing Oracle SID and Character set selection") + + - **Encryption:** Configure key management, you have options to manage database keys. Select **Use Oracle-managed keys** to manage database keys using the wallet or select **Use customer-managed keys** to manage database keys using OCI Vaults. + +![Image showing console connection copy SSH string options](./images/select-encryption-option.png "Image showing console connection copy SSH string options") + + - **Tags:** Apply free-form or defined tags to this resource. + +![Image showing the option to add container database tags](./images/enter-container-db-tag.png "Image showing the option to add container database tags") + +7. Click **Create container database**. + +![Image showing the option confirm creation of container database](./images/click-create-container-db.png "Image showing the option confirm creation of container database") + + Once the provisioning process of the container database is completed, the state of the container database will show as **Available**. + +![Image showing created container database](./images/created-cdb.png "Image showing created container database") + +8. In the **Container Database details** page, under **Resources**, select **Pluggable Databases**. + +![Image showing created pdb](./images/click-pdb.png "Image showing created pdb") + + Click **Pluggable Database** to view the details of the pluggable database. + +![Image showing created pdb](./images/click-pdb-details.png "Image showing created pdb") + +***!!! Congratulations:*** You may now **proceed to the next lab**. + + +## Learn More + +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/index.html) to learn more about the Exadata Database Service on Exascale Infrastructure. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, April 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-click-on-vm-cluster.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-click-on-vm-cluster.png new file mode 100644 index 0000000..b7063e2 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-click-on-vm-cluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-configure-storage-vault.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-configure-storage-vault.png new file mode 100644 index 0000000..4e4392a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-configure-storage-vault.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-basic-info.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-basic-info.png new file mode 100644 index 0000000..035ab86 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-basic-info.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-deployment-status.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-deployment-status.png new file mode 100644 index 0000000..192ae78 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-deployment-status.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review-part2.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review-part2.png new file mode 100644 index 0000000..62bca35 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review-part2.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review.png new file mode 100644 index 0000000..87bca84 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-create-vm-cluster-review.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-exadb-xs-portal.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-exadb-xs-portal.png new file mode 100644 index 0000000..7226ded Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-exadb-xs-portal.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-create-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-create-exadb-xs.png new file mode 100644 index 0000000..ebe6aed Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-create-exadb-xs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-exadb-xs-blade.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-exadb-xs-blade.png new file mode 100644 index 0000000..9077ed4 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-portal-exadb-xs-blade.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-storage-vault-details.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-storage-vault-details.png new file mode 100644 index 0000000..8bedf26 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-storage-vault-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-allocation.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-allocation.png new file mode 100644 index 0000000..7357239 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-allocation.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-consent.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-consent.png new file mode 100644 index 0000000..27f3eec Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-consent.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-2.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-2.png new file mode 100644 index 0000000..8136968 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-2.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-3.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-3.png new file mode 100644 index 0000000..473e854 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-3.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-storage-vault.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-storage-vault.png new file mode 100644 index 0000000..20a4313 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page-storage-vault.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page.png new file mode 100644 index 0000000..d1410a6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-diagnostics.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-diagnostics.png new file mode 100644 index 0000000..d4edff8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-diagnostics.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-go-to-oci-link.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-go-to-oci-link.png new file mode 100644 index 0000000..9a0ce13 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-go-to-oci-link.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-network-settings.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-network-settings.png new file mode 100644 index 0000000..ce0198d Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-network-settings.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-storage.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-storage.png new file mode 100644 index 0000000..4377966 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-storage.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-tags.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-tags.png new file mode 100644 index 0000000..ce1c30b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vm-cluster-tags.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vmcluster-available-list.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vmcluster-available-list.png new file mode 100644 index 0000000..706c73f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/azure-vmcluster-available-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-database.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-database.png new file mode 100644 index 0000000..77f9af4 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-database.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-db.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-db.png new file mode 100644 index 0000000..bf637d7 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-container-db.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vm-cluster.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vm-cluster.png new file mode 100644 index 0000000..fd05694 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vm-cluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vmcluster.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vmcluster.png new file mode 100644 index 0000000..d74a9e6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-create-vmcluster.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb-details.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb-details.png new file mode 100644 index 0000000..2302739 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb.png new file mode 100644 index 0000000..b421cd8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/click-pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/configure-db-backup.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/configure-db-backup.png new file mode 100644 index 0000000..1e3f3fd Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/configure-db-backup.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb-details.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb-details.png new file mode 100644 index 0000000..6e03796 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb.png new file mode 100644 index 0000000..648071f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-tags.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-tags.png new file mode 100644 index 0000000..41ad63c Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/create-tags.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/created-cdb.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/created-cdb.png new file mode 100644 index 0000000..fd2de0e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/created-cdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-administrator-credentials.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-administrator-credentials.png new file mode 100644 index 0000000..b2aed00 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-administrator-credentials.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-container-db-info.pdb.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-container-db-info.pdb.png new file mode 100644 index 0000000..4f57892 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-container-db-info.pdb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-vmcluster-info.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-vmcluster-info.png new file mode 100644 index 0000000..a93f7cf Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-basic-vmcluster-info.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-container-db-tag.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-container-db-tag.png new file mode 100644 index 0000000..766378a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-container-db-tag.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-database-home.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-database-home.png new file mode 100644 index 0000000..2c1facf Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-database-home.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-exascale-db-storage-vault.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-exascale-db-storage-vault.png new file mode 100644 index 0000000..7805ee0 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-exascale-db-storage-vault.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-grid-ssh-key.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-grid-ssh-key.png new file mode 100644 index 0000000..f656345 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-grid-ssh-key.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-scan-listener-port.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-scan-listener-port.png new file mode 100644 index 0000000..5917f42 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-scan-listener-port.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-configuration.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-configuration.png new file mode 100644 index 0000000..bd1b961 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-configuration.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-network-settings.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-network-settings.png new file mode 100644 index 0000000..aa14bf5 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/enter-vmcluster-network-settings.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-exadb-xs.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-exadb-xs.png new file mode 100644 index 0000000..1a2b003 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-exadb-xs.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-menu-exadb.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-menu-exadb.png new file mode 100644 index 0000000..783ef59 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/navigate-oci-menu-exadb.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/oci-vm-cluster-details-page.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/oci-vm-cluster-details-page.png new file mode 100644 index 0000000..2d1396d Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/oci-vm-cluster-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-encryption-option.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-encryption-option.png new file mode 100644 index 0000000..3b12a4c Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-encryption-option.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-sid-character-set.png b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-sid-character-set.png new file mode 100644 index 0000000..b43659b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/images/select-sid-character-set.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/provision-exadb-xs-on-azure.md b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/provision-exadb-xs-on-azure.md new file mode 100644 index 0000000..32c8ea0 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/provision-exadb-xs-on-azure/provision-exadb-xs-on-azure.md @@ -0,0 +1,221 @@ +# Provision Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure + + +## Introduction + +This lab walks you through how to create an instance of the Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure using the Azure Portal. +  + +**Estimated Time:** ***2 Hours 10 minutes*** + + +### Objectives + +- After completing this lab, you should be able to create an Exadata VM cluster and an Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure using the OCI Console. + + +### Prerequisites + +* An existing Microsoft Azure subscription. + +* A Microsoft Azure Resorce Group created. + +* A Microsoft Azure Virtual Network (VNet) with a subnet delegated to the Oracle Database@Azure service. + +* Permissions in Microsoft Azure to create resources in the region. + +* Oracle Cloud Infrastructure (OCI) Service Limits approved in the region you want to provision Oracle Exadata Database Service. + +## Task 1: Create an Exadata VM Cluster Resource on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure + +1. Log in to the Microsoft Azure portal, navigate to the left pane to display a list of services and click **Oracle Database@Azure**. + + ![Image showing Azure services Console Navigation](./images/azure-exadb-xs-portal.png "Image showing Azure services Console Navigation") + +2. Provision the Oracle Exadata Database Service on Exascale Infrastructure resources from Oracle Database@Azure. + + Click **Oracle Database@Azure** drop-down menu and then **Oracle Exadata Database Service on Exascale Infrastructure**. + + ![Image showing Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure](./images/azure-portal-exadb-xs-blade.png "Image showing Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure") + +3. Click **Vm Clusters** and select **+ Create** to begin the provisioning flow. + + ![Image showing option to create Exadata VM Cluster](./images/azure-portal-create-exadb-xs.png "Image showing option to create Exadata VM Cluster") + +4. In the **Basics** section, enter the following information and click **Next**. + + * **Project details:** + * **Subscription:** Select the Microsoft Azure subscription for the Exascale VM cluster. + * **Resource group:** Select an existing resource group or click **Create new** to create and use a new resource group for this resource. + * **Exascale VM Cluster details:** + * **Name:** Enter the name for the Exascale VM cluster. + * **Region:** Select the region where the Exascale VM cluster will be provisioned. + * **Availability zone:** Select an availability zone. + * **Cluster name:** Enter a cluster name. + * **License type:** The type of license you want to use for the VM cluster. The license type is either ***License included*** or ***Bring your own license (BYOL)***. Your selection will affect your billing. + * **Time zone:** The default time zone is UTC. There is also an option to select another time zone. + * **Oracle grid infrastructure release:** Select the Oracle Grid Infrastructure release. + * **Oracle grid infrastructure version:** Select the Oracle Grid Infrastructure version. + + ![Image showing basic info to create Exadata VM Cluster](./images/azure-create-vm-cluster-basic-info.png "Image showing basic info to create Exadata VM Cluster") + + * **Exascale Database Storage Vault:** + * **Choose:** Select either ***Create new vault*** or ***Select existing vault***. If you select an existing vault, then select the database storage vault from the drop-down menu. + * **Vault name:** Enter the vault name for the new Exascale vault. + * **Storage capacity for Databases:** The amount of usable disk storage capacity that will be available for storing databases that is desired. Specify the size in gigabytes (GB). + * ***(Optional)*** **Add smart flash and memory cache options:** Enter the amount of smart flash cache. It is based on a percentage of storage capacity. + * **Security:** The SSH public key source can be selected to ***Generate new key pair***, ***Use existing key stored in Azure***, or ***Use existing public key***. + * If you select ***Generate new key pair***, you must give your newly generated key a unique name. + * If you select ***Use existing key stored in Azure***, you must select that key from a drop-down menu of defined key for your subscription. + * If you select ***Use existing public key***, you must provide an RSA public key in single-line format (starting with `ssh-rsa`) or the multi-line PEM format. You can generate SSH keys using `ssh-keygen` or Linux and OS X, or PuTTYGen on Windows. + + ![Image showing Exascale database storage configuration options](./images/azure-configure-storage-vault.png "Image showing Exascale database storage configuration options") + +5. In the **Configuration** section, enter the following information and click **Next**. + * In **VM Cluster allocation**, select resources for the VM cluster. + * **Number of VMs in the cluster:** Specify the number of the VMs that you want to configure for the cluster, between 2 and 10. + * **ECPUs enabled per VM:** Specify the number of ECPU cores that you want to enable for the VM cluster. The minimum is 8 ECPU. The value you select must be a multiple of 4. + * ***(Optional)*** Add reserve additional ECPU** + * **ECPUs additional reserved per VM:** _(read-only)_ Indicates the additional reserved ECPUs + * **Total additional ECPUs reserved across VM Cluster:** _(read-only)_. + * **Total ECPUs per VM:** Enter the total number of ECPUs to allocate per VM. The total must be between 8 and 200. + * **Total ECPUs enabled across VM Cluster:** _(read-only)_. + * **Memory per VM (GB):** _(read-only)_ Displays the amount of memory allocated to each VM. Memory is calculated based on 2.75 GB per ECPU. + * **Total memory across VM cluster (GB):** _(read-only)_ The total memory across VM cluster (GB) field is automatically updated to provide you with the total amount of memory allocated across the VM cluster. + + ![Image showing to configure VM Cluster allocation configuration options](./images/azure-vm-cluster-allocation.png "Image showing to configure VM Cluster allocation configuration options") + * **VM file system storage capacity per VM (GB):** Specify storage capacity per VM in gigabytes (GB). + > **Note:** Enter how much storage you want for the VM filesystem. The VM filesystem storage includes `/u02` capacity, where your database homes will be created, along with all the other VM file systems. The extra capacity selected beyond system minimum will expand `/u02` file system. + + ![Image showing virtual machine configuration options](./images/azure-vm-cluster-storage.png "Image showing virtual machine configuration options") + +6. In the **Networking** section, enter the following information to configure the network settings and click **Next**. + * **Virtual network:** Select the virtual network (VNet) in which you want to create the VM cluster. + + > **Note:** The drop-down menu will only list virtual networks that are located within the subscription and resource group that you have selected in the **Basics** section. If the drop-down menu is empty, you may need to specify a different subscription or resource group, or create a virtual network within the selected resource group. + + * **Client subnet:** Select the client subnet. + + > **Note:** The drop-down menu will only list delegated subnets that are contained within the virtual network that you have selected above. If the drop-down menu is empty, you may need to specify a different virtual network, or create a delegated subnet within the selected virtual network. + + * **Backup subnet:** Leave this field blank as Oracle will automatically assign it. This is the subnet to use for the backup network, which is typically used to transport backup information to and from the backup destination, and for Oracle Data Guard replication. + + * **Hostname prefix:** Enter a hostname. The prefix forms the first portion of the Exadata VM cluster host name. Recommended maximum: 12 characters. + + * **Host Domain Name:** _(read only)_ Displays the host domain name for the VM cluster. + + * **Host and domain URL:** _(read only)_ This read-only field combines the host and domain names to display the fully qualified domain name (FQDN) for the database. + + > **Note:** If custom DNS is selected, this field is composed of the entered hostname and selected private zone. If custom DNS is not selected, this field is composed of the entered hostname, selected subnet, and selected virtual network. + + * **SCAN Listener Port (TCP/IP):** Assign a SCAN listener port (TCP/IP) in the range between `1024` and `8999`. The default is `1521`. If you do not assign the port, then the Exadata VM cluster is created with the default port. + + * **Add additional network ingress rules:** Add additional network CIDR ranges (such as application or hub subnet ranges) to the Network Security Group (NSG) ingress rules for this VM cluster. The selected virtual network's CIDR is added by default. + + ![Image showing network configuration options](./images/azure-vm-cluster-network-settings.png "Image showing network configuration options") + +7. In the **Diagnostics Collection** section, select all to enable diagnostics collection and click **Next**. + + ![Image showing diagnostics collection](./images/azure-vm-cluster-diagnostics.png "Image showing diagnostics collection") + + > **Note:** Enabling diagnostics collection and notifications allow you and OCI operations to identify, investigate, track, and resolve guest VM issues quickly and effectively. + +8. In the **Consent** section, you must agree to the **terms of service**, **privacy policy**, and agree to **access permissions**. Select **Next** to continue. + + ![Image showing consent page](./images/azure-vm-cluster-consent.png "Image showing license type options") + +9. In the **Tags** section, you can define Microsoft Azure tags and click **Next**. + + ![Image showing tags page](./images/azure-vm-cluster-tags.png "Image showing tags page") + +10. In the **Review + create** section, 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. + + ![Image showing review page](./images/azure-create-vm-cluster-review.png "Image showing review page") + +11. Click **Create** to start the provisioning flow. + + ![Image showing review page](./images/azure-create-vm-cluster-review-part2.png "Image showing review page") + + Once the provisioning process is completed. Deployment status of both Oracle Exascale VM Cluster and Oracle Exascale DB Storage Vault will show as **OK**. + + ![Image showing deployment status](./images/azure-create-vm-cluster-deployment-status.png "Image showing deployment status") + +## Task 2: Discover the Oracle Exascale VM Cluster Details + +1. In the **Oracle Exadata Database Service on Exascale Infrastructure** page, select the **Vm Clusters** tab. + + Once the provisioning process of the **Oracle Exascale VM Cluster** is completed, the state of the VM cluster will show as ***Available***. + + ![Image showing review page](./images/azure-vmcluster-available-list.png "Image showing review page") + +2. Click the created VM cluster to view the details of the Oracle Exascale VM cluster. + + ![Image showing created vm cluster](./images/azure-click-on-vm-cluster.png "Image showing created vm cluster") + + On the **Oracle Exascale VM Cluster** **Overview** page ***Discover the available VM Cluster information:*** + + * In the **Essentials** Section you can find the following key items: + * What Resource group the Oracle Exascale VM Cluster is in. + * The Location of the Oracle Exascale VM Cluster. + * The Subscription where the Oracle Exascale VM Cluster is deployed. + * The Subscription ID. + * Assigned tags for the VM Cluster + * The State of the VM Cluster + * A link to view the OCI Database URL + * A link to view the Storage Vault + + ![Image showing VM Cluster details page](./images/azure-vm-cluster-details-page.png "Image showing VM Cluster details page") + + * The **Resource Allocation** Section contains the following Cluster Wide Metrics: + * The number of Reserved ECPUs available to conduct online scale up operation. + * The number of Enabled ECPUs across the VM Cluster. + * The amount of Memory allocated to the VMs across the VM Cluster. + * The total VM File System Storage allocated to the VMs across the VM Cluster. + * In the **Version** Section of the page, you will find the following key items: + * The Exadata Image Version. + * The Grid Infrastructure Version. + + ![Image showing VM Cluster details page](./images/azure-vm-cluster-details-page-2.png "Image showing VM Cluster details page") + + * The **Networking** Section contains the following key pieces of networking information: + * The name of the Virtual network being used for the subnets and routing rules. + * The Client Subnet ***(delegated)*** selected for this VM Cluster. + * The Hostname domain name of the VM Cluster. + * The SCAN DNS name, SCAN IPs, and SCAN listener port. + * A link to view the OCI network security group. + + ![Image showing VM Cluster details page](./images/azure-vm-cluster-details-page-3.png "Image showing VM Cluster details page") + +## Task 3: Discover the Oracle Exascale Database Storage Vault Details + +1. In the Oracle Exascale VM Cluster **Overview** section, under the **Essentials**, click the name of the created **Storage Vault**. + + On the **Oracle Exascale DB Storage Vault** **Overview** page ***Discover the available Exascale DB Storage Vault information:*** + + ![Image showing VM Cluster details page](./images/azure-vm-cluster-details-page-storage-vault.png "Image showing VM Cluster details page") + + * In the **Essentials** Section you can find the following key items: + * What Resource group the Oracle Exascale DB Storage Vault is in. + * The Location of the Oracle Exascale DB Storage Vault. + * The Subscription where the Oracle Exascale DB Storage Vault is deployed. + * The Subscription ID. + * Assigned tags for the Oracle Exascale DB Storage Vault + * The State of the Oracle Exascale DB Storage Vault + * A link to view the OCI Storage vault URL + * In the **Exascale Database Storage** Section you will find the following key items: + * The amount of Exascale database storage that was allocated and how much capacity is free. + + ![Image showing Exascale database storage details page](./images/azure-storage-vault-details.png "Image showing Exascale database storage details page") + +***!!! Congratulations:*** You may now **proceed to the next lab**. + + +## Learn More + +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/manage-vm-clusters.html) to learn more about managing the VM clusters on the Exadata Database Service on Exascale Infrastructure. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, April 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-cloud-shell.png new file mode 100644 index 0000000..9fe08f8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-storage-vault-go-to-oci.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-storage-vault-go-to-oci.png new file mode 100644 index 0000000..2a3bb6b Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/azure-storage-vault-go-to-oci.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png new file mode 100644 index 0000000..e8e4cfc Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png new file mode 100644 index 0000000..d5b5bf0 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png new file mode 100644 index 0000000..dfefc84 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png new file mode 100644 index 0000000..c8b0928 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png new file mode 100644 index 0000000..a53ee3e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png new file mode 100644 index 0000000..96c3b0e Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png new file mode 100644 index 0000000..b30b28f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png new file mode 100644 index 0000000..7154802 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png new file mode 100644 index 0000000..4e3b20a Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page-before.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page-before.png new file mode 100644 index 0000000..0e46d74 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page-before.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page.png new file mode 100644 index 0000000..f4c8b29 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault.png new file mode 100644 index 0000000..27903b6 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-storage-vault.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-available.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-available.png new file mode 100644 index 0000000..ae622b2 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-available.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-updating.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-updating.png new file mode 100644 index 0000000..025b1a8 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vault-updating.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png new file mode 100644 index 0000000..f305533 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-copy-ocid.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-copy-ocid.png new file mode 100644 index 0000000..f5c67ee Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-copy-ocid.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-resources.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-resources.png new file mode 100644 index 0000000..32aa26f Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/storage-vault-resources.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png new file mode 100644 index 0000000..c4bc910 Binary files /dev/null and b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png differ diff --git a/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md new file mode 100644 index 0000000..ecfae99 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md @@ -0,0 +1,111 @@ + + + +# Scale Exascale Storage Vault Resources + + +## Introduction + +This lab walks you through the steps to Scale the Exascale Storage Vault Resources using the OCI Console. + +**Estimated Time:** ***10 minutes*** + + +### Objectives + +- After completing this lab, you should be able to scale the Exascale Storage Vault Resources using the OCI Console. +- List Exascale Storage Vault configuration using **OCI CLI** + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + + +## Task 1: Scale an Existing Exascale Storage Vault + +1. Go to the **Oracle Exascale DB Storage Vault** **Overview** page. In the OCI Storage vault URL, click the ***Go to OCI*** link. + + ![Image showing Exascale database storage details page](./images/azure-storage-vault-go-to-oci.png "Image showing Exascale database storage details page") + +2. In the **Exascale Storage Vault details** page, select **Scale Storage Vault**. + + ![Image showing scale Exascale storage vault](./images/scale-storage-vault.png "Image showing scale storage vault") + +3. In **Scale Storage Vault**, enter a value for the desired storage capacity for databases. This number should be the value for the total storage that you want to have provisioned after the scaling operation completes. + + ![Image showing scale Exascale storage vault](./images/scale-storage-vault-page-before.png "Image showing scale storage vault") + + Click **Save Changes**. + + ![Image showing scale Exascale storage vault](./images/scale-storage-vault-page.png "Image showing scale storage vault") + + The **Exascale Storage Vault details** page is now displayed. While the scale storage vault process is running, the lifecycle state of the Exascale storage vault shows ***UPDATING***. + + ![Image showing scale Exascale storage vault](./images/scale-vault-updating.png "Image showing scale storage vault") + + When the scale storage vault process completes, the state of the Exascale storage vault changes to ***AVAILABLE***. + + ![Image showing scale Exascale storage vault](./images/scale-vault-available.png "Image showing scale storage vault") + + The **Exascale Storage Vault details** page displays information about the new allocated Exascale database storage. + + In the Exascale Storage Vault Details page, Copy the Storage Vault OCID by clicking the ***copy*** button in the ***OCID*** field under the **General Information** section. + Paste the copied ***Exascale Storage Vault OCID*** to a text editor. + + ![copy storage vault ocid](./images/storage-vault-copy-ocid.png "copy storage vault ocid") + +## Task 2: List Exascale Storage Vault Configuration using CLI + + >**Note:** For this lab, we will be using the ***Azure Cloud Shell tool*** with an **OCI CLI** configured. + +1. Click the **Azure Cloud Shell** icon in the console header. + + ![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. + +2. Run the OCI CLI Command to get the Exascale Storage Vault Configuration. + + >**Note:** Replace ***{ExascaleVaultID}*** with the Exascale Storage Vault OCID copied from *(Task 1 Step 4)* + + ``` + + + oci db exascale-db-storage-vault get --exascale-db-storage-vault-id {ExascaleVaultID} + + + ``` + + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***exascale-db-storage-vault*** ***get*** ***--exascale-db-storage-vault-id*** ***{ExascaleVaultID}*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exascale-db-storage-vault*** is the **resource type** for the Exascale Storage Vault. + * ***get*** is the **action** to get information about the Exascale Storage Vault Configuration. + * ***--exascale-db-storage-vault-id*** is the **parameter** for the Exascale Storage Vault OCID. + + After running the command, you will see similar output below. + + ![show storage vault details](./images/get-storage-vault-details.png "show storage vault details") + + The output of the command displays information about the configuration of the selected ***Exascale Storage Vault***, such as: + + * ***Storage Vault Display Name*** + * ***Exascale Database Storage Capacity Available size in gbs*** + * ***Exascale Database Storage Capacity Total size in gbs*** + * ***Lifecycle state*** + * ***Exascale Storage Vault Associated VM Cluster Count and OCID*** + +***Congratulations!!!*** You may now **proceed to the next lab**. + +## Acknowledgements + +* **Author** - Leo Alvarado, Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, March 2025. diff --git a/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/index.html b/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/index.html new file mode 100644 index 0000000..e295c94 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/index.html @@ -0,0 +1,70 @@ + + + + + + + + + Oracle LiveLabs + + + + + + + + + + + + + +
+
+
+
+
+
+
+
+ + + + + diff --git a/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/manifest.json b/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/manifest.json new file mode 100644 index 0000000..30457f3 --- /dev/null +++ b/exadata-database-service-at-azure-xs-get-started/workshops/get-started-with-exadb-at-az-xs/manifest.json @@ -0,0 +1,54 @@ +{ + "workshoptitle": "Get Started with Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure", + + "help": "livelabs-help-exadata_us@oracle.com", + + "tutorials": [ + { + "title": "Introduction", + "description": "Introduction", + "filename": "../../introduction-gs/introduction-gs.md" + }, + { + "title": "Get Started", + "description": "Login to Oracle Cloud", + "filename": "../../get-started-gs/get-started-gs.md" + }, + { + "title": "Lab 1: Create Instance of Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure", + "description": "Learn how to Create Instance of Exadata Database Service on Exscale Infrastructure using OCI Console", + "filename": "../../provision-exadb-xs-on-azure/provision-exadb-xs-on-azure.md" + }, + { + "title": "Lab 2: Create Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure", + "description": "Learn how to create Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure on Oracle Database@Azure", + "filename": "../../provision-database/provision-database.md" + }, + { + "title": "Lab 3: Create Thin Clone of PDB", + "description": "Learn how to Create PDB Thin Clone on Exadata Exascale using OCI Console", + "filename": "../../create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md" + }, + { + "title": "Lab 4: Scale Exascale Storage Vault Resources", + "description": "Learn how to Scale Exascale Storage Vault Resources using OCI Console", + "filename": "../../scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md" + }, + { + "title": "Lab 5: Configure & Validate Notifications for Monitoring ECPU Scaling Changes", + "description": "Learn how to Configure & Validate Notifications for Monitoring ECPU Scaling Changes", + "filename": "../../configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md" + }, + { + "title": "Lab 6: Discover Exadata Database Service on Exascale Infrastructure Environment Details using APIs", + "description": "Learn how to Discover Environment Details using APIs", + "filename": "../../discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md" + }, + + { + "title": "Need Help?", + "description": "Solutions to Common Problems and Directions for Receiving Live Help", + "filename":"https://oracle-livelabs.github.io/common/labs/need-help/need-help-freetier.md" + } + ] +} \ No newline at end of file diff --git a/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json index 72bbd59..fa91716 100644 --- a/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json +++ b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json @@ -1,7 +1,7 @@ { "workshoptitle": "Get Started with Oracle Exadata Database Service on Exascale Infrastructure", - "help": "livelabs-help-db_us@oracle.com", + "help": "livelabs-help-exadata_us@oracle.com", "tutorials": [ {