WMS ID: 11853 -- Get Started with Exadata Database Service on Exascale Infrastructure

exadata-database-service-xs-get-started/.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "liveServer.settings.port": 5501
+}

exadata-database-service-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 [<u>**Managing Topics and Notifications**</u>](https://docs.oracle.com/en-us/iaas/Content/Security/Reference/notifications_security.htm#iam-policies) and [<u>**Managing Events**</u>](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)*
+
+    ```
+    <copy>
+
+      oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state"}'
+
+    </copy>
+    ```
+
+   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.

exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md

@@ -0,0 +1,100 @@
+# Create Thin Clone of an Oracle Pluggable Database (PDB) leveraging Exadata Exascale Technology
+
+
+## Introduction
+
+This lab walks you through how to create a thin cloned Oracle Pluggable Database of a Pluggable Database that is created on Exadata Exascale Infrastructure.
+
+  * For Pluggable Databases created on the Exadata Database Service on Exascale Infrastructure (**ExaDB-XS**), you can clone an Oracle Pluggable Database as a standard **clone** or as a **thin clone** (***unique to ExaDB-XS***). 
+  * A PDB **clone** is an independent and complete copy of the given database as it existed at the time of the cloning operation. 
+  * A PDB **thin clone** is a special type of the Local Clone, that leverages the Exascale redirect-on-write technology, that allows the thin clone PDB to share unchanged storage blocks with the parent PDB. This results in the fast creation of the thin cloned PDB with reduced space consumption.
+
+ * ***The following types of clones are supported:*** 
+    * ***Local Clone***: A full copy of the PDB that is created within the same CDB. 
+    * ***Thin Clone***: A thin clone copy of the PDB that is created within the same CDB (***Option Only avaiable for Local Clones***). 
+    * ***Remote Clone***: A full copy of the PDB that is created in a different CDB. 
+    * ***Refreshable Clone***: A refreshable clone enables you to keep your remote clone updated with the source PDB. The only open mode you can have is read-only and refresh cannot be done while it is in read-only mode. 
+
+
+**Estimated Time:** ***10 minutes***
+
+### **Objectives**
+
+-   After completing this lab, you should be able to navigate to your VM Cluster, locate your desired Container Database, and create a thin cloned Oracle Pluggable Database on the Exadata Database Service on Exascale Infrastructure 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.
+
+## Task 1: Create a Thin Clone PDB using OCI Console
+
+1. Open the **navigation menu** and click ***Oracle Database***. Under **Oracle Database**, click ***Oracle Database Service on Exascale Infrastructure***.
+
+  ![Navigate from OCI Console to ExaDB-XS](./images/console-to-exadb-xs.png " ") 
+    * **Note:** This will cause the **VM Clusters** page to be displayed.
+
+2. On the left rail, ensure that **VM Clusters** is selected (default selection). For the **List Scope**, select your compartment. 
+
+   In the list of displayed VM clusters, click on the name of your VM Cluster.
+
+  ![Navigate to Compartment and VM Cluster](./images/select-compartment-and-mydemo-vm-cluster.png " ")
+    * **Note:** This will cause the **VM Cluster Details** page to be displayed.
+
+3. Navigate from the VM Cluster to the Container Database (CDB). On the left rail under the **Resources** section, click on ***Container Databases***. 
+
+   In the list of Container Databases diplayed, click on the ***name of the Container Database*** whose PDB we will create a thin clone of.  
+
+  ![Navigate from VM Cluster to Container Database (CDB)](./images/mydemo-vm-cluster-details-page-to-cdb.png " ")
+    * **Note:** This will cause the **Container Database Details** page to be displayed.
+
+1. Navigate from CDB to Pluggable Database (PDB). On the left rail under the **Resources** section, click on ***Pluggable Databases***. From the list of available Pluggable Databases displayed, click on the ***name of the Pluggable Database*** we will create a thin clone of.  
+
+  ![Navigate from CDB to Pluggable Database (PDB)](./images/navigate-cdb-to-pdb.png " ")
+    * **Note:** This will cause the **Pluggable Database Details** page to be displayed.
+
+5. Initiate the **Clone** Pluggable Database action. 
+
+   On the **Pluggable Database Details** page, initiate the Clone PDB action by clicking on the ***Clone*** action button.
+
+  ![Initiate Clone Pluggable Database Action](./images/pdb-details-clone-pdb.png " ")
+    * **Note:** This will cause the **Clone Pluggable Database** configuration page to be displayed.
+
+6. Configure Clone PDB options and check the box to **Enable Thin Clone**
+
+   In the **Clone Pluggable Database** configuration page, select the PDB Clone type. Select ***Local Clone***.
+    * Provide the information to configure the new PDB. 
+        * Enter the **PDB Name** 
+        * Enter the **Database TDE wallet password** 
+        * For this lab we will defer the initial PDB backup by ***unchecking the box*** to **Take a backup of the PDB immediately after cloning**
+        * Next, ensure to ***check the box*** to **Enable Thin Clone**
+        * Click on the ***Create Pluggable Database*** button to start the clone provisioning process.
+  ![Configure Clone options and check box to Enable Thin Clone](./images/configure-pdb-thin-clone.png " ")
+    * **Note:** that the thin PDB clone will be created and presented as a new PDB.
+  ![New Thin Clone PDB Details page](./images/available-pdb-thin-clone-details-page.png " ")
+
+1. List all of the PDBs in the Container Database (CDB). From the **Pluggable Database Details** page, select the ***Container Database Details*** link in the breadcrumb path at the top of the page.
+
+    * **Note:** that this will cause the **Container Database Details** page to be displayed.
+  ![List Thin Clone PDB from CDB](./images/list-pdb-thin-clone-from-cdb.png " ")
+
+  On the left rail under the **Resources** section, click on ***Pluggable Databases***. 
+    * **Note:** that 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, Eddie Ambler, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.