diff --git a/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md b/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md index 287ae00..fcc5b98 100644 --- a/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md +++ b/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md @@ -8,14 +8,15 @@ This lab walks you through the steps to Change License Type using OCI Console. -Estimated Lab Time: 15 minutes +**Estimated Lab Time:** ***15 minutes*** + ### Objectives -- After completing this lab, you should be able to Change License Type using OCI Console +- After completing this lab, you should be able to Change License Type of the Exadata VM Cluster by using the OCI Console. ### Prerequisites @@ -23,21 +24,40 @@ This lab requires completion of the following: * Completion of **Lab1** -## Task 1: Change License Type using OCI Console +## Task 1: Change License Type of Exadata VM Cluster using OCI Console + +1. Navigate to the Exadata Database Service on Exascale Infrastructure using OCI Console + + * 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 Image](./images/console-to-exadb-xs.png " ") + * **Note:** This will cause the **VM Clusters** page to be displayed. + +2. Navigate to your Compartment and VM Cluster -1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + * On the left rail, ensure that **VM Clusters** is selected (default selection). + * For the **List Scope**, select your assigned compartment named ***MyCompartmentXX***. + * In the list of displayed VM clusters, click on the name of your **Assigned VM Cluster** named ***MyDemoVMClusterXX***. + ![Navigate to Compartment and VM Cluster Image](./images/select-compartment-and-mydemo-vm-cluster.png " ") + * **Note:** This will cause the **VM Cluster Details** page to be displayed. -2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. +3. On the VM Cluster Details page, take note of the current **License Type** selection -3. In the VM Cluster Details page, Click **Update License Type** + ![Note current VM Cluster License Type Image](./images/vmc-current-license-type.png " ") + +4. On the VM Cluster Details page, Click **Update License Type** - ![Update License Type](./images/update-license-type-button.png " ") + ![Update License Type Image](./images/update-license-type-button.png " ") -4. Change the license type from **Bring Your Own License (BYOL)** to ***License Included*** +5. Change the license type from **Bring Your Own License (BYOL)** to ***License Included*** + + ![Update License Type Image](./images/change-license-included.png " ") - ![Update License Type](./images/change-license-included.png " ") +6. Click **Save Changes** + +7. On the VM Cluster Details page, validate that the **License Type** selection has been changed to ***License Included*** -5. Click **Save Changes** + ![Note updated VM Cluster License Type Image](./images/vmc-updated-license-type.png " ") You may now **proceed to the next lab** @@ -45,8 +65,8 @@ You may now **proceed to the next lab** ## Acknowledgements -* **Author** - Leo Alvarado, Eddie Ambler, Product Management +* **Authors** - Eddie Ambler, Leo Alvarado, Product Management * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Leo Alvarado, Product Management, September 2023. +* **Last Updated By** - Eddie Ambler, Product Management, August 2024. diff --git a/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png b/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png new file mode 100644 index 0000000..476211c Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png differ diff --git a/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png b/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png new file mode 100644 index 0000000..59c2cc4 Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png differ diff --git a/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png b/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png new file mode 100644 index 0000000..546fbaa Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png differ diff --git a/exadata-database-service-xs/create-standby-vmcluster-on-exascale/create-standby-vmcluster-and-dbhome-on-exascale.md b/exadata-database-service-xs/create-standby-vmcluster-on-exascale/create-standby-vmcluster-and-dbhome-on-exascale.md index 66b0672..32cb8fb 100644 --- a/exadata-database-service-xs/create-standby-vmcluster-on-exascale/create-standby-vmcluster-and-dbhome-on-exascale.md +++ b/exadata-database-service-xs/create-standby-vmcluster-on-exascale/create-standby-vmcluster-and-dbhome-on-exascale.md @@ -1,9 +1,9 @@ -# Create Instance of Exadata Database Service on Exascale Infrasturcture using OCI Console +# Create Standby Exadata VM Cluster & Database Home using OCI Console ## Introduction -This lab walks you through how to create an instance of the Exadata Database Service on Exascale Infrastructure using the OCI Console. +This lab walks you through how to create an Exadata VM Cluster & Database Home deployed on the Exadata Database Service on Exascale Infrastructure using the OCI Console. This Exadata VM Cluster will be used as a standby target inour upcoming labs.   Estimated Time: 2 Hours 10 minutes @@ -13,7 +13,7 @@ Watch the video below for a quick walk-through of the lab. ### Objectives -- After completing this lab, you should be able to create an Exadata VM cluster and an Oracle Database on Exascale technology using the OCI Console. +- After completing this lab, you should be able to create an Exadata VM cluster and an Oracle Database Home on the Exadata Database Service on Exascale Infrastructure using the OCI Console. ### Prerequisites @@ -22,15 +22,15 @@ This lab requires completion of the following: * Successful Login to a Tenancy with a service limit assigned for the **Exadata Database Service on Exascale Infrastructure** -## Task 1: (***Pre-Created for OCW Session***) --> Create an Exadata VM Cluster Resource with Exadata on Exascale Cloud Infrastructure +## Task 1: Create an Exadata VM Cluster Resource with Exadata on Exascale Cloud Infrastructure 1. 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. In the left rail, **VM Clusters** is selected by default. Under **List Scope**, Select your assigned compartment named ***MyCompartmentXX***. +2. In the left rail, **VM Clusters** is selected by default. Under **List Scope**, Select your assigned standby compartment named ***MyStandbyCompartmentXX***. - ![Select Compartment where VM Cluster will reside](./images/select-compartment.png" ") + ![Select Compartment where Standby Exadata VM Cluster will reside](./images/select-standby-compartment.png" ") 3. Click **Create VM Cluster** button @@ -39,23 +39,17 @@ This lab requires completion of the following: 4. **Provide the basic information to configure the Exadata VM cluster**. * For Compartment: Ensure that the compartment that you want the VM Cluster to be created in is displayed. It should display **your assigned compartment**. - * For Display Name: Enter ***MyDemoVMClusterXX*** + * For Display Name: Enter ***MyStandbyVMClusterXX*** * For Cluster Name: Enter ***MyDemoClus*** * For Availability Domain: Select the availability domain from the displayed options available. - ![Provide Basic VM Cluster Info](./images/provide-basic-vm-cluster-info-exascale.png" ") + ![Provide Basic Standby VM Cluster Info Image](./images/provide-basic-standby-vm-cluster-info-exascale.png" ") 5. **To Configure the VM cluster, provide the following information:** * For the number of VMs in the cluster: ***Enter 2*** - * For ECPUs enabled per VM: ***Enter 8*** - - * ***Reserve 4 additonal ECPUs*** by clicking on **Reserve additional ECPU to increase link** and entering the following: - * For **Total ECPUs per VM:** Provide a total number of ECPUs to allocate per VM. ***Enter 12***. - * The **ECPUs additional reserved per VM** field which is (read only) will now indicate that there are now **4 reserved ECPUs**. - * The **Memory per VM (GB)** field which is (read only) will display the amount of memory allocated to each VM.
- ***Memory is calculated based on 2.75 GB per total ECPU***. + * For ECPUs enabled per VM: ***Enter 8*** **Size the VM file system storage**: * For system storage capacity per VM (GG): ***Enter 280*** @@ -68,10 +62,10 @@ This lab requires completion of the following: * Select **Create new vault**. **For a new vault, specify the following:** - * For the **Exascale Vault name:** enter ***MyDemoStorageVaultXX*** . + * For the **Exascale Vault name:** enter ***MyStandbyStorageVaultXX*** . * For the **Storage Capacity for Databases (GB):** ***enter 300***. - **Note:** The minimum size configuration for an Exascale Database Storage Vault is 300 GB. 200 GB of the space that you allocate in your Vault is reserved for a 200 GB ACFS file system. This ACFS file system resides within your Exascale Database Storage Vault, but is reserved for system use. Thus, if you provisioned the minimum of 300 GB in your Exascale Database Storage Vault, then 100 GB of that 300 GB capacity will be available storage for your databases. + **Note:** The minimum size configuration for an Exascale Database Storage Vault is 300 GB. 50 GB of the space that you allocate in your Vault is reserved for an internal ACFS file system. This ACFS file system resides within your Exascale Database Storage Vault, but is reserved for system use. Thus, if you provisioned the minimum of 300 GB in your Exascale Database Storage Vault, then 250 GB of that 300 GB capacity will be available storage for your databases. When you create a new vault, the Provisioning status window opens to provide you with the status of vault creation, and the name of the vault that is being created in the format Vault-YYYYMMDDHHMM indicating the creation date, where YYYY is the year, MM is the month, DD is the day, HH is the hour, and Mm is the minute. @@ -94,7 +88,7 @@ This lab requires completion of the following: * **For the Virtual Cloud Network (VCN):** Click Change Compartment and select compartment named ***MyDemo***.
Then select the Virtual Cloud Network named ***MyDemoVCN***. - * **For the Client subnet:** Select the client subnet in the assigned compartment named ***MyClient-PrivateSubnetAXX***.
+ * **For the Client subnet:** Select the client subnet in the **assigned standby compartment** named ***MyClient-PrivateSubnetBXX***.
* **For the Backup Subnet:** Click Change Compartment and select compartment named ***MyDemo***.
Then select the Backup Subnet named ***MyBackup-PrivateSubnet***. @@ -121,7 +115,7 @@ In the Edit Diagnostics Collection Settings dialog, you can enable or disable an -## Task 2: Create an Oracle Database on Exadata Database Service on Exascale Infrastructure using OCI Console +## Task 2: Create an Oracle Database Home using OCI Console 1. **Navigate to the Exadata Database Service on Exascale Infrastructure:** * Open the navigation menu. @@ -129,45 +123,18 @@ In the Edit Diagnostics Collection Settings dialog, you can enable or disable an ![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ") -2. **Navigate to the cloud VM cluster you want to create the database in:** +2. **Navigate to the cloud VM cluster you want to create the database home in:** * In the left rail, ensure ***VM Clusters*** is selected. - * Under **List Scope**, Select your assigned compartment named ***MyCompartmentXX***. + * Under **List Scope**, Select your assigned compartment named ***MyStandbyCompartmentXX***. * Then **click on your VM Clusters** ***assigned name*** to view the **VM Cluster Details page**. ![Select Compartment and VM Cluster where Container Database will reside](./images/select-compartment-and-vm-cluster.png" ") -3. On the **VM Cluster Details page** Click on **Create Container Database**. +3. On the **VM Cluster Details page** under **Resources** Click on **Database Homes** and then click on the ***Create Database Home** button. ![Create Container Database button](./images/vmc-details-pg-create-cdb-on-exascale.png " ") -4. In the **Create Container Database** page enter the **basic information for creating the container database:** - * For the **Database Name:** Enter ***DemoDBXX*** - * For the **Database Unique Name Suffix:** Enter ***DemoDBXX_23aiExascale01*** - * For the **Database Version:** Select ***23ai*** - * For the **Pluggable Database Name:** Enter ***MyPDBXX*** - - ![Create Container Database Basic Info](./images/create-cdb-basic-info.png " ") - -5. Specify the **Database Home Source and Administrator Credentials:** - * For the **Database Home source** choose: **Select an Existing Database Home** - * Select Database Home with display name of ***MyDemo23aiDBhome01*** - * Next configure your **Administrator Credentials:** by entering ***Pass4StudentOCW24-#*** as the **password** for the **sys** username. - - ![Define DBhome and Admin Password Image](./images/define-dbhome-and-admin-pwd.png " ") - -6. For this lab, we will not be enabling **Automatic Backups** for the database during the create database workflow. - * **Uncheck the box for:** ***Enable Automatic Backups*** - - ![Uncheck Enable Automatic Backups Image](./images/uncheck-enable-automatic-backups.png " ") - -7. **Review & Configure Advanced Options** for the Container Database by clicking on the **Show Advanced Options** link. - * Under the **Management tab** set the Oracle_SID to ***ExascaleDemo*** - ![Configure Adv Options - Mgmt Tab Image](./images/configure-adv-options-mgmt-tab.png " ") - * Under the **Encryption tab** you can select the desired key management method. Select ***Use Oracle-managed keys***. - ![Configure Adv Options - Encryption Tab Image](./images/configure-adv-options-encrypt-tab.png " ") - - * Under the **Tags tab:** you can add free-form tags to your resource. If you want to apply a defined tag, you must have permissions to use the tag namespace. Remember that you can also apply tags to your resources after they are provisioned. - ![Configure Adv Options - Tags Tab Image](./images/configure-adv-options-tags-tab.png " ") +4. 8. Click on the **Create Container Database** button to proceed with creating the Container Database. diff --git a/exadata-database-service-xs/enable-data-guard/enable-data-guard-using-oci-console.md b/exadata-database-service-xs/enable-data-guard/enable-data-guard-using-oci-console.md index 2cb5bf6..137e4bf 100644 --- a/exadata-database-service-xs/enable-data-guard/enable-data-guard-using-oci-console.md +++ b/exadata-database-service-xs/enable-data-guard/enable-data-guard-using-oci-console.md @@ -26,78 +26,81 @@ This lab requires completion of the following: ## Task 1: Enable Data Guard using OCI Console -1. In the Breadcrumb link, Click on **Oracle Exadata Database Service on Cloud@Customer**. - - ![Navigate to Exadata VM Cluster](./images/navigate-exadbcc-vmcluster.png " ") - -2. In the left rail, **Exadata VM Clusters** is selected by default. Select your assigned Compartment ***MyCompartmentXX*** then Click on the name of your assigned VM Cluster ***MyVMClusterXX***. - - ![Select assigned Compartment and assigned VM Cluster](./images/select-compartment.png " ") +1. **Navigate to the Exadata Database Service on Exascale Infrastructure:** + * Open the **Navigation Menu**. + * Under **Oracle Database**, click ***Exadata Database Service on Exascale Infrastructure***. -3. On the left rail, under **Resources** of the VM Cluster details page, select **Databases** and from the list of the displayed databases click the container database named ***MyCDB01***. - - ![Select CDB](./images/select-cdb.png " ") + ![Navigate to Exadata Database Service on Exascale Infrastructure Image](./images/console-to-exadb-xs.png" ") -4. In the Container Database details page, under **Resources**, click **Data Guard Associations**. +2. **Navigate to the Exadata VM cluster** in your assigned compartment: + * In the left rail, select ***VM Clusters***. + * Under **List Scope**, Select your assigned compartment named ***MyCompartmentXX***. + * Then click on the name of ***your VM Cluster*** to view the **VM Cluster Details page**. - ![Click on Dataguard Associations](./images/navigate-dg-association.png " ") + ![Select Compartment and VM Cluster where Container Database will reside Image](./images/select-compartment-and-vm-cluster.png" ") -5. Click **Enable Data Guard**. +3. **Navigate to the Continer Database** we want to configure a Data Guard Association for. + * On the left rail of the **VM Cluster details page**, under **Resources** , select ***Container Databases*** + * From the list of the displayed databases **click on the container database named** ***DemoDBXX***. + + ![Select CDB Image](./images/select-cdb.png " ") - ![Click Enable Data Guard](./images/enable-dataguard.png " ") +4. Start the **Data Guard Association process** + * In the Container Database details page, under **Resources**, click on ***Data Guard Associations***. + * Then click on the ***Enable Data Guard*** button. + + ![Start Enable Dataguard Associations Image](./images/start-dg-association.png " ") - In the Enable Data Guard page, configure your Data Guard association. +5. In the Enable Data Guard page, **provide the information to configure your Data Guard association.** - **Select Peer VM Cluster**: + **In the Select Peer VM Cluster Section of the page:** - * **Peer Region**: Select your **assigned peer region** ***"US East (Ashburn) OR US West (San Jose)"***. - - >**Note:** The primary and standby databases could be running on two different VM clusters on a shared ExaDB-C@C system or on two geographically separated ExaDB-C@C systems managed from the same or different Oracle Cloud Infrastructure regions. For this lab, the primary and standby database will be running on a shared ExaDB-C@C system on the same region. - - * **Exadata Cloud@Customer Infrastructure**: Select the Exadata Database Service on Cloud@Customer infrastructure where the standby database is located. Click the **Change Compartment** hyperlink and select ***OCW23ExaDBCC*** for the compartment. - - Select your **assigned Exadata Cloud@Customer Infrastructure**. - - * **Peer VM Cluster**: Select the Exadata VM Cluster that contains the standby database. Click the **Change Compartment**, select ***MyStandByCompartment_{Region}*** then select ***MyStandbyVMCluster*** for the Peer VM Cluster + * For the **Peer Region**: Select your ***assigned peer region*** + * For the **Availability Domain**: Select your ***assigned availabilty domain*** + * Then select the **Compartment** named ***MyDemoStandby*** and Select the **peer VM Cluster** named ***MyDemoStandbyVMCluster*** - ![Select Peer VM Cluster](./images/select-peer-vmcluster.png " ") + >**Note:** The peer Region selected will determine if you are configuring a local standby or a DR standby. - **Data Guard Assocation Details:** + **In the DataGuard Association Details section of the page:** - * **Select the Data Guard type**: Select Active Data Guard or Data Guard. For this lab, select ***Active Data Guard*** + * For the **Data Guard type**: you can choose between Active Data Guard or Data Guard. For this lab, select ***Active Data Guard*** - * **Protection mode**: Select a protection mode the Data Guard association. For this lab, select ***Maximum Performance*** + * For the **Protection mode**: you can choose between Maximum Performance and Maximum Availability. For this lab, select ***Maximum Performance*** - ![Select Data Guard Association](./images/dg-association-details.png " ") + ![Select Peer VMC and Data Guard Association Details Image](./images/choose-peer-vmc-and-dg-association-details.png " ") - **Choose Database Home**: Choose ***Select an existing Database Home*** then select ***MyStandbyDBHome*** for the Database Home. - - - ![Choose Database Home](./images/choose-database-home.png " ") +6. **Choose the Database Home and name the standby database:** + * For the **Database Home** choose ***Select an existing Database Home*** then select ***MyDemoStandby23aiDBHome02***. - **Configure standby database**: Provide the unique name for the standby database. + * For the **Database unique name** for the standby database: enter ***MyDemoDB_23aiStandbyXX*** +
( Where ***XX*** is your assigned student # for the workshop). - * Provide the **Database password**. For this lab, use the assigned password ***Pass4Stud3nt-#*** + * For the **Database password**. For this lab, use ***Pass4OCW24-#*** -6. Click **Enable Data Guard**. + **Under Advanced Options on the Management Tab:** - ![Click Enable Data Guard](./images/click-enable-dataguard.png " ") + * For the **Oracle SID Prefix** enter: **ExaStandby*****XX*** +
( Where ***XX*** is your assigned student # for the workshop). + + * Then Click on the **Enable Data Guard** button to start the cloud automation workflow. + + ![Choose DB Home and Name Standby Image](./images/choose-dbhome-and-name-standby.png " ") - The Data Guard Association process will run in the background. When the association is created, the details for a database and its peer display their respective roles as ***Primary*** or ***Standby***. + >*The Data Guard Association process will run in the background. When the association is created, the details for a database and its peer display their respective roles as ***Primary*** or ***Standby***. - + ![Data Guard Association Completed Image](./images/dataguard-association-completed.png " ") You may now **proceed to the next lab** ## Learn More -* Click [here](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-using-data-guard.html#GUID-6EBC4D6A-C58B-4721-B756-F22FC6819A45) to learn more about using Oracle Data Guard with Exadata Database Service on Cloud@Customer. +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/using-data-guard-with-exadb-xs.html) to learn more about using Oracle Data Guard with Exadata Database Service on Exascale Infrastructure. ## Acknowledgements -* **Author** - Leo Alvarado, Eddie Ambler, Product Management +* **Author** - Eddie Ambler, Leo Alvarado, Product Management * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Leo Alvarado, Product Management, September 2023. +* **Last Updated By** - Eddie Ambler, Product Management, August 2024. diff --git a/exadata-database-service-xs/enable-data-guard/images/choose-dbhome-and-name-standby.png b/exadata-database-service-xs/enable-data-guard/images/choose-dbhome-and-name-standby.png new file mode 100644 index 0000000..b119961 Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/choose-dbhome-and-name-standby.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/choose-peer-vmc-and-dg-association-details.png b/exadata-database-service-xs/enable-data-guard/images/choose-peer-vmc-and-dg-association-details.png new file mode 100644 index 0000000..4e161fd Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/choose-peer-vmc-and-dg-association-details.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/console-to-exadb-xs.png b/exadata-database-service-xs/enable-data-guard/images/console-to-exadb-xs.png new file mode 100644 index 0000000..9476315 Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/console-to-exadb-xs.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/dataguard-association-completed.png b/exadata-database-service-xs/enable-data-guard/images/dataguard-association-completed.png new file mode 100644 index 0000000..9620029 Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/dataguard-association-completed.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/peer-vmc-and-dg-association-details.png b/exadata-database-service-xs/enable-data-guard/images/peer-vmc-and-dg-association-details.png new file mode 100644 index 0000000..4e161fd Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/peer-vmc-and-dg-association-details.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/select-cdb.png b/exadata-database-service-xs/enable-data-guard/images/select-cdb.png index be412cb..fe9d5b1 100644 Binary files a/exadata-database-service-xs/enable-data-guard/images/select-cdb.png and b/exadata-database-service-xs/enable-data-guard/images/select-cdb.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/select-compartment-and-vm-cluster.png b/exadata-database-service-xs/enable-data-guard/images/select-compartment-and-vm-cluster.png new file mode 100644 index 0000000..cac5e82 Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/select-compartment-and-vm-cluster.png differ diff --git a/exadata-database-service-xs/enable-data-guard/images/start-dg-association.png b/exadata-database-service-xs/enable-data-guard/images/start-dg-association.png new file mode 100644 index 0000000..9ace2d7 Binary files /dev/null and b/exadata-database-service-xs/enable-data-guard/images/start-dg-association.png differ diff --git a/exadata-database-service-xs/introduction-ocw24-mc/introduction-ocw24-mc.md b/exadata-database-service-xs/introduction-ocw24-mc/introduction-ocw24-mc.md index 8dacdc1..265b3ca 100644 --- a/exadata-database-service-xs/introduction-ocw24-mc/introduction-ocw24-mc.md +++ b/exadata-database-service-xs/introduction-ocw24-mc/introduction-ocw24-mc.md @@ -6,14 +6,15 @@ This workshop is designed to provide you with hands on experience using the Exad 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. +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 PDB 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. +During this workshop, you will learn how to use cloud automation to configure Maximum Availability constructs for your databases by enabling high availability and disaster recovery with Data Guard and Active Data Guard and cloud-based automatic backup and recovery. +
You will also learn how to capture and deploy infrastructure as code with terraform and 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:** ***90 minutes*** +**Estimated Workshop Time:** ***8 Hours*** ### **What is an Oracle Exadata Database Service?**