diff --git a/exadata-database-service-dedicated/automatic-infrastructure-maintenance/automatic-infrastructure-maintenance.md b/exadata-database-service-dedicated/automatic-infrastructure-maintenance/automatic-infrastructure-maintenance.md new file mode 100644 index 0000000..2da4813 --- /dev/null +++ b/exadata-database-service-dedicated/automatic-infrastructure-maintenance/automatic-infrastructure-maintenance.md @@ -0,0 +1,71 @@ + + + +# Review Option to configure Automatic Infrastructure Maintenance + + +## Introduction + +This lab walks you through the steps to configure Automatic Infrastructure Maintenance for your Exadata Cloud@Customer Infrastructure. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to configure Automatic Infrastructure Maintenance for your Exadata Cloud@Customer Infrastructure. + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Review Option to configure Automatic Infrastructure Maintenance + +*(For this lab, Informational Instructions for Configuring Automatic Infrastructure Maintenance for the Exadata Database Service on Cloud@Customer environment will be presented by the speakers)* + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Select your ***Assigned Region*** and ***Assigned Compartment*** + +3. Click your ***Assigned Exadata Infrastructure*** + +4. Click **Edit Maintenance Preferences**. + +5. On the Edit Maintenance Preferences page, configure the following: + + **Choose a maintenance method**: + + * **Rolling**: By default, Exadata Infrastructure is updated in a rolling fashion, one server at a time with no downtime. + * **Non-rolling**: Update database and storage servers at the same time. The non-rolling maintenance method minimizes maintenance time but incurs full system downtime. + + **Enable custom action before performing maintenance on DB servers**: Enable custom action only if you want to perform additional actions outside of Oracle’s purview + + * **Configure Custom action timeout (in minutes)**: Timeout available to perform custom action before starting maintenance on the DB Servers. + + **Maintenance schedule**: + + * **Under Maintenance months**, specify at least one month for each quarter during which Exadata infrastructure maintenance will take place. + * **Under Week of the month**, specify which week of the month, maintenance will take place. + * **Under Day of the week**, specify the day of the week on which the maintenance will occur. + * **Under Start hour**, specify the hour during which the maintenance run will begin. + * **Under Lead Time**, specify the minimum number of weeks ahead of the maintenance event you would like to receive a notification message. + +6. Click **Save Changes**. + +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-vw-maint-hist.html#GUID-94A6038F-6329-46BC-AEBD-E5491D67B72F) to learn more about Configuring Oracle-Managed Infrastructure Maintenance for Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/change-license-type/change-license-type.md b/exadata-database-service-dedicated/change-license-type/change-license-type.md new file mode 100644 index 0000000..8b77e29 --- /dev/null +++ b/exadata-database-service-dedicated/change-license-type/change-license-type.md @@ -0,0 +1,52 @@ + + + +# Change License Type using OCI Console + + +## Introduction + +This lab walks you through the steps to Change License Type using OCI Console. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Change License Type using OCI Console + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Change License Type using OCI Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + +3. In the VM Cluster Details page, Click **Update License Type** + + ![Update License Type](./images/update-license-type-button.png " ") + +4. Change the license type from **Bring Your Own License (BYOL)** to ***License Included*** + + ![Update License Type](./images/change-license-included.png " ") + +5. Click **Save Changes** + + +You may now **proceed to the next lab** + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/change-license-type/images/change-license-included.png b/exadata-database-service-dedicated/change-license-type/images/change-license-included.png new file mode 100644 index 0000000..449f3c3 Binary files /dev/null and b/exadata-database-service-dedicated/change-license-type/images/change-license-included.png differ diff --git a/exadata-database-service-dedicated/change-license-type/images/update-license-type-button.png b/exadata-database-service-dedicated/change-license-type/images/update-license-type-button.png new file mode 100644 index 0000000..9ba5ff3 Binary files /dev/null and b/exadata-database-service-dedicated/change-license-type/images/update-license-type-button.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/configure-notifications.md b/exadata-database-service-dedicated/configure-notifications/configure-notifications.md new file mode 100644 index 0000000..58362ac --- /dev/null +++ b/exadata-database-service-dedicated/configure-notifications/configure-notifications.md @@ -0,0 +1,127 @@ + + + +# Configure Notifications for Enabled OCPU or License Type change + + +## Introduction + +This lab walks you through the steps to configure notifications to get notified for VM Cluster Event Types such as Enabled OCPU or License Type change. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to configure notifications and events rules for Exadata Database Service on Cloud@Customer + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Configure Notification Topic and Subscription for Enabled OCPU or License Type change + +1. Open the navigation menu and click **Developer Services**. Under **Application Integration**, click **Notifications**. + + ![Navigate to Notifications](./images/navigate-notifications.png " ") + +2. **Topics** page is selected by default, select your ***Assigned Compartment*** and Click **Create Topic**. + + ![Click Create Topic](./images/create-topic.png " ") + +3. Provide the Topic name. For this lab, use ***MyExaDBCCTopic*** 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 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 ***assigned 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 on the ***Confirm subscription*** link + + ![Confirm Subscription](./images/confirm-subscription.png " ") + + By clicking the confirmation link, it will launch a browser displaying subscription has been confirmed and that you have subscribed your assigned Email to the Topic you have selected. + + ![Subscription Confirmation Display](./images/subscription-confirmation-page.png " ") + + You can now see the subscription is now ***Active*** + + ![Subscription Active](./images/subscription-active.png " ") + + +## Task 2: Create Events Rule to create notification automation based on Enabled OCPU or License Type 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 ***Assigned 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 ***MyExaDBCCEventsRule***. + + ![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 ***VM Cluster - Update Begin*** and ***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 ***Assigned Compartment*** + * For **Topic**, Select ***MyExaDBCCTopic*** + + ![Configure Actions](./images/configure-actions.png " ") + +6. Click **Create Rule** + + ![Create Rule](./images/create-rule.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-customer-events.html#GUID-1BDBB213-B153-48F9-BE06-D85CAD6386B8) to learn more about Exadata Database Service on Cloud@Customer Events. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/configure-notifications/images/click-create-rule.png b/exadata-database-service-dedicated/configure-notifications/images/click-create-rule.png new file mode 100644 index 0000000..ee2bb0a Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/click-create-rule.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/click-create-subscription.png b/exadata-database-service-dedicated/configure-notifications/images/click-create-subscription.png new file mode 100644 index 0000000..46bcff4 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/click-create-subscription.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/click-create-topic.png b/exadata-database-service-dedicated/configure-notifications/images/click-create-topic.png new file mode 100644 index 0000000..71e0509 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/click-create-topic.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/click-on-created-topic.png b/exadata-database-service-dedicated/configure-notifications/images/click-on-created-topic.png new file mode 100644 index 0000000..b2de86d Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/click-on-created-topic.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/configure-actions.png b/exadata-database-service-dedicated/configure-notifications/images/configure-actions.png new file mode 100644 index 0000000..099cf7e Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/configure-actions.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/configure-rule-conditions.png b/exadata-database-service-dedicated/configure-notifications/images/configure-rule-conditions.png new file mode 100644 index 0000000..623c617 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/configure-rule-conditions.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/confirm-subscription.png b/exadata-database-service-dedicated/configure-notifications/images/confirm-subscription.png new file mode 100644 index 0000000..b76d67d Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/confirm-subscription.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-events-rule.png b/exadata-database-service-dedicated/configure-notifications/images/create-events-rule.png new file mode 100644 index 0000000..e34a16f Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-events-rule.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-rule.png b/exadata-database-service-dedicated/configure-notifications/images/create-rule.png new file mode 100644 index 0000000..0d60b35 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-rule.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-subscriptions.png b/exadata-database-service-dedicated/configure-notifications/images/create-subscriptions.png new file mode 100644 index 0000000..f496fd0 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-subscriptions.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-topic-active.png b/exadata-database-service-dedicated/configure-notifications/images/create-topic-active.png new file mode 100644 index 0000000..dad7582 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-topic-active.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-topic-name.png b/exadata-database-service-dedicated/configure-notifications/images/create-topic-name.png new file mode 100644 index 0000000..ef6825e Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-topic-name.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/create-topic.png b/exadata-database-service-dedicated/configure-notifications/images/create-topic.png new file mode 100644 index 0000000..f6385dd Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/create-topic.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/navigate-notifications.png b/exadata-database-service-dedicated/configure-notifications/images/navigate-notifications.png new file mode 100644 index 0000000..0f32146 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/navigate-notifications.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/navigate-rules.png b/exadata-database-service-dedicated/configure-notifications/images/navigate-rules.png new file mode 100644 index 0000000..48120ee Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/navigate-rules.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/provide-topic-name.png b/exadata-database-service-dedicated/configure-notifications/images/provide-topic-name.png new file mode 100644 index 0000000..eb55e58 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/provide-topic-name.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/subscription-active.png b/exadata-database-service-dedicated/configure-notifications/images/subscription-active.png new file mode 100644 index 0000000..cb68e09 Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/subscription-active.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/subscription-confirmation-page.png b/exadata-database-service-dedicated/configure-notifications/images/subscription-confirmation-page.png new file mode 100644 index 0000000..27b8a0c Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/subscription-confirmation-page.png differ diff --git a/exadata-database-service-dedicated/configure-notifications/images/subscription-pending-status.png b/exadata-database-service-dedicated/configure-notifications/images/subscription-pending-status.png new file mode 100644 index 0000000..cbd156a Binary files /dev/null and b/exadata-database-service-dedicated/configure-notifications/images/subscription-pending-status.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/create-database-custom-image.md b/exadata-database-service-dedicated/create-database-custom-image/create-database-custom-image.md new file mode 100644 index 0000000..4aa36be --- /dev/null +++ b/exadata-database-service-dedicated/create-database-custom-image/create-database-custom-image.md @@ -0,0 +1,92 @@ +# Create Application and Database Custom Image using OCI Console + + +## Introduction + +This lab walks you through creating Application and Database Custom Image using the OCI Console. +  + * **Database software images** are resources containing Oracle Database software used to provision and patch Oracle Databases and Oracle Database Homes. + * **Database software images** are either **Oracle-published software releases** or **custom software images you create**. + * **Custom Database Software Images** include specified patches and updates that meet your organization's standards. + +Estimated Time: 10 minutes + +Watch the video below for a quick walk-through of the lab. + [Create a Custom Database Software Image](youtube:jwxxIih3brQ) + +### Objectives + +- After completing this lab, you should be able to create application and database custom image using the OCI Console. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + +## Task 1: Create Application Custom Image using OCI Console + +1. Open the navigation menu and click **Compute**. Under Compute, click **Instances**. + + ![Naviage OCI Compute](./images/navigate-compute-instance.png" ") + +2. In the left rail, **Instances** is selected by default. Select your assigned compartment named ***MyCompartmentXX***. + + Click on the name of your **Assigned Custom Application Server** named ***MyCustomAppServer***. + + ![Click MyCustomAppServer Instance](./images/click-create-instance.png" ") + +3. Click **More Actions**, and then click **Create custom image**. + + ![Create Custom App Server More Actions](./images/click-instance-more-actions.png " ") + +4. In the **Create in compartment** list, Select your assigned compartment ***MyCompartmentXX*** + + Enter a **Name** for the image. For this lab, use the name ***MyCustomAppServerImage*** + + ![Create Custom App Server Image](./images/create-custom-app-image.png " ") + +5. Click **Create custom image**. + + +## Task 2: Create Custom Database Software Image using OCI Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Under **Resources**, click **Database Software Images**. + +3. Click **Create Database Software Image**. + + ![Create Custom Database Software Image](./images/create-custom-dbsw.png " ") + +4. In the **Display name** field, provide a name for your database software image. For this lab, use the name ***MyCustomDBimage*** + +5. Choose your **assigned compartment** ***MyCompartmentXX***. + + ![Create Custom Database Software Image](./images/create-dbsw-page.png " ") + +6. Choose the **Database version** for your image. For this workshop, select the ***19c*** version. + +7. Choose the **patch set update, proactive bundle patch, or release update**. For this workshop, choose ***19.18.0.0*** + +8. Click **Create Database Software Image**. + + ![Create Custom Database Software Image Dialog Page](./images/create-dbsw-version-page.png " ") + +You may now **proceed to the next lab**. + + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/click-create-instance.png b/exadata-database-service-dedicated/create-database-custom-image/images/click-create-instance.png new file mode 100644 index 0000000..3b8731e Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/click-create-instance.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/click-instance-more-actions.png b/exadata-database-service-dedicated/create-database-custom-image/images/click-instance-more-actions.png new file mode 100644 index 0000000..6282112 Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/click-instance-more-actions.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-app-image.png b/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-app-image.png new file mode 100644 index 0000000..330217f Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-app-image.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-dbsw.png b/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-dbsw.png new file mode 100644 index 0000000..62a1a2e Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/create-custom-dbsw.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-page.png b/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-page.png new file mode 100644 index 0000000..c3aa5e0 Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-page.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-version-page.png b/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-version-page.png new file mode 100644 index 0000000..08f503d Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/create-dbsw-version-page.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/navigate-compute-instance.png b/exadata-database-service-dedicated/create-database-custom-image/images/navigate-compute-instance.png new file mode 100644 index 0000000..51ecdcc Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/navigate-compute-instance.png differ diff --git a/exadata-database-service-dedicated/create-database-custom-image/images/oci-mngmt-interfaces.png b/exadata-database-service-dedicated/create-database-custom-image/images/oci-mngmt-interfaces.png new file mode 100644 index 0000000..61b2bdf Binary files /dev/null and b/exadata-database-service-dedicated/create-database-custom-image/images/oci-mngmt-interfaces.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/discover-env-details-api.md b/exadata-database-service-dedicated/discover-env-details-api/discover-env-details-api.md new file mode 100644 index 0000000..68edaa8 --- /dev/null +++ b/exadata-database-service-dedicated/discover-env-details-api/discover-env-details-api.md @@ -0,0 +1,225 @@ +# Discover Environment Details using REST API + + +## Introduction + +Any operation that you can do with the web console, you can also do with a corresponding REST API. Like the web console, the REST APIs transit the Internet via HTTPS, requiring no special software to be installed on the local system. The Oracle Cloud Infrastructure APIs are typical REST APIs that use HTTPS requests and responses. + +This lab walks you through the steps to discover Exadata Database Service on Cloud@Customer environment details using REST API. + +Estimated Time: 10 minutes + +### Objectives + +- After completing this lab, you should be able to discover Exadata Database Service on Cloud@Customer environment details using REST API. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab6** + +## Task 1: List the available Database Homes in a compartment using REST API + +1. Open the Cloud Shell. This displays the Cloud Shell at the bottom of the console: + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + + +2. Make an OCI REST API call to get a list of 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 ***Lab6***. + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10" + + + ``` +3. You will see a similar output as below. Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all available DB Homes in the specified compartment. + + ![list available dbhomes](./images/list-dbhome.png " ") + + Look for the Database Home with the **displayName** named ***MyCustomDBHome***. + + Observe the following objects and values from the API response such as: + + * ***databaseSoftwareImageId*** - If this field is populated then this is the **Custom Database Software Image** used for the Database Home + * ***dbVersion*** - The **Database Version** of the Database Home + + +## Task 2: List all the Container Databases in a Compartment + +1. From the Cloud Shell terminal, run the **OCI CLI command** below to get a list of the Container Databases in a Compartment. + + > **Note:** Replace the ***"{CompartmentID}"*** with the **Compartment OCID** used in ***Task 1*** + + ``` + + + oci db database list --compartment-id {CompartmentID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table + + + ``` + +2. You will see a similar output as below. Copy the **Container Database OCID** value and paste it in your notepad or text editor. + + ![list pluggable database](./images/list-all-cdb-in-compartment.png " ") + +## Task 3: List all the Pluggable Databases in a Container Database using REST API + +1. From the Cloud Shell terminal, make an OCI REST API call to get a list of the Pluggable Databases in a Container Database by running the **OCI RAW-REQUEST** command below: + + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{ContainerDatabaseOCID}"*** with the **Container Database OCID** obtained from ***Task 2*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" + + + ``` + +2. You will see a similar output as below. 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 specified container database. + +3. Copy the **PDB OCID** value from the **"id"** field and paste it in your notepad or text editor. + + ![list pluggable database](./images/getpdb.png " ") + + +## Task 4: Clone and start a pluggable database (PDB) in the same database (CDB) using REST API + +1. From the Cloud Shell terminal, create the JSON file for the REST API request body that contains the local clone pluggable database details resource. + + For this lab, the JSON file is pre-created; you can view the local clone pluggable database details by reading the JSON file. + + ``` + + + cat MyClonePDB.json + + + ``` + + +2. Make an OCI REST API call to clone and start a pluggable database (PDB) in the same container database (CDB) by running the **OCI RAW-REQUEST** command below: + + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{pluggableDatabaseID}"*** with the **Pluggable Database OCID** copied from ***Task3 Step 3*** + + ``` + + + oci raw-request --http-method POST --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/pluggableDatabases/{pluggableDatabaseID}/actions/localClone" --request-body file://MyClonePDB.json + + + + ``` + + + +3. You will see a similar output as below; you will see that the local clone pluggable database is on a lifecycle state of ***PROVISIONING*** + + ![local clone pluggable database](./images/clonepdb.png " ") + + +## Task 5: Discover Exadata VM Cluster Details using REST API + +1. Open the Cloud Shell. This displays the Cloud Shell at the bottom of the console. + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + +2. Make an OCI REST API call to get Exadata VM Cluster details by running the **OCI RAW-REQUEST** command below. + + > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***Lab 6 (Task 1 step 2)*** + + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}" + + + ``` + + + You will see a similar output below; pay attention to the **cpusEnabled** field. + + ``` + + { + "data": { + "availabilityDomain": "cuGa:US-SANJOSE-1-AD-1", + "compartmentId": "ocid1.compartment.oc1.....", + "cpusEnabled": 4, + "dataCollectionOptions": { + "isDiagnosticsEventsEnabled": true, + "isHealthMonitoringEnabled": true, + "isIncidentLogsEnabled": true + }, + + "status": "200 OK" +} + + ``` + + +## Task 6: List the Maintenance Updates that can be applied to the specified VM Cluster using REST API + +1. Make OCI REST API call to list maintenance updates that can be applied to the specified VM Cluster by running the **OCI RAW-REQUEST** Command below. + + > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***(Lab 6 Task 1 step 2)*** + + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}/updates" + + + ``` + + + ![list VM Cluster updates](./images/get-vmcluster-updates.png " ") + + You will see a similar output as below. Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the maintenance updates that can be applied to the specified VM Cluster using REST API + + ``` + + + { + "data": [ + { + "availableActions": [ + "ROLLING_APPLY", + "PRECHECK" + ], + "description": "Virtual Machine OS Update 22.1.11.0.0.230516", + "id": "ocid1.dbupdate.oc1.us-sanjose-1....", + "lastAction":, + "lifecycleDetails":, + "lifecycleState": "AVAILABLE", + "timeReleased": "2023-06-06T19:15:24.842Z", + "updateType": "OS_UPDATE", + "version": "22.1.11.0.0.230516" + } + ], + "headers": { + + }, + "status": "200 OK" +} + + ``` + + +You may now **proceed to the next lab**. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/clonepdb.png b/exadata-database-service-dedicated/discover-env-details-api/images/clonepdb.png new file mode 100644 index 0000000..fbc180d Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/clonepdb.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/cloudshell.png b/exadata-database-service-dedicated/discover-env-details-api/images/cloudshell.png new file mode 100644 index 0000000..f78c5d4 Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/cloudshell.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/cloudshelllaunch.png b/exadata-database-service-dedicated/discover-env-details-api/images/cloudshelllaunch.png new file mode 100644 index 0000000..ee78be0 Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/get-vmcluster-updates.png b/exadata-database-service-dedicated/discover-env-details-api/images/get-vmcluster-updates.png new file mode 100644 index 0000000..7ec2baa Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/get-vmcluster-updates.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/getpdb.png b/exadata-database-service-dedicated/discover-env-details-api/images/getpdb.png new file mode 100644 index 0000000..a069635 Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/getpdb.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/list-all-cdb-in-compartment.png b/exadata-database-service-dedicated/discover-env-details-api/images/list-all-cdb-in-compartment.png new file mode 100644 index 0000000..2607a0f Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/list-all-cdb-in-compartment.png differ diff --git a/exadata-database-service-dedicated/discover-env-details-api/images/list-dbhome.png b/exadata-database-service-dedicated/discover-env-details-api/images/list-dbhome.png new file mode 100644 index 0000000..8528e80 Binary files /dev/null and b/exadata-database-service-dedicated/discover-env-details-api/images/list-dbhome.png differ diff --git a/exadata-database-service-dedicated/enable-automatic-backups/enable-automatic-backups.md b/exadata-database-service-dedicated/enable-automatic-backups/enable-automatic-backups.md new file mode 100644 index 0000000..0992b36 --- /dev/null +++ b/exadata-database-service-dedicated/enable-automatic-backups/enable-automatic-backups.md @@ -0,0 +1,70 @@ + + + +# Review Enable Automatic Backups + + +## Introduction + +This lab walks you through the steps to Enable Automatic Backups. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Enable Automatic Backups + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Enable Automatic Backups + +*(For this lab, Informational Instructions for Enabling Automatic Backups for the Exadata Database Service on Cloud@Customer environment will be presented by the speakers)* + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + +3. In the Resources list of the VM Cluster Details page, click Databases. + +4. Click the name of the database for which you want to edit backup settings. + +5. Click Edit Backup Settings. + + Your current backup configuration determines the changes that you can make in the Backup Settings dialog, as follows: + + If automatic backups are not configured (Backup Destination Type is set to None), then you can use the following settings to define the backup configuration for the database: + + **Backup Destination Type**: From the list, choose an option. + + * **None** Select if you do not define a backup configuration for the database. + * **Local** Select to store backups locally in the Exadata Storage Servers on your Exadata Database Service on Cloud@Customer system. + * **Object Storage** Select to store backups in an object storage container managed by Oracle on Oracle Cloud Infrastructure. + * **NFS** Select to store backups in one of your previously defined backup destinations that uses Network File System (NFS) storage. + * **Recovery Appliance** Select to store backups in one of your previously defined backup destinations that uses Oracle Zero Data Loss Recovery Appliance. + + **Enable automatic backups**: Select this option to enable daily backups using the policy for automatic backups. + + **Backup retention period**: Select this option to choose one of the options for the length of time that automatic backups are retained. +6. Click **Save Changes**. + + +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-manage-db-backup-and-recovery.html#GUID-07D1B1D6-4A06-4859-B7DF-4C3A681A6B40) to learn more about Managing Database Backup and Recovery on Oracle Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/enable-dataguard/enable-dataguard.md b/exadata-database-service-dedicated/enable-dataguard/enable-dataguard.md new file mode 100644 index 0000000..2cb5bf6 --- /dev/null +++ b/exadata-database-service-dedicated/enable-dataguard/enable-dataguard.md @@ -0,0 +1,103 @@ + + + +# Enable Data Guard for local HA using OCI Console + + +## Introduction + +This lab walks you through the steps to Enable Data Guard using OCI Console. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Enable Data Guard using OCI Console + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + + +## 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 " ") + +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 " ") + +4. In the Container Database details page, under **Resources**, click **Data Guard Associations**. + + ![Click on Dataguard Associations](./images/navigate-dg-association.png " ") + +5. Click **Enable Data Guard**. + + ![Click Enable Data Guard](./images/enable-dataguard.png " ") + + In the Enable Data Guard page, configure your Data Guard association. + + **Select Peer VM Cluster**: + + * **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 + + ![Select Peer VM Cluster](./images/select-peer-vmcluster.png " ") + + **Data Guard Assocation Details:** + + * **Select the Data Guard type**: Select 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*** + + ![Select Data Guard Association](./images/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 " ") + + **Configure standby database**: Provide the unique name for the standby database. + + * Provide the **Database password**. For this lab, use the assigned password ***Pass4Stud3nt-#*** + +6. Click **Enable Data Guard**. + + ![Click Enable Data Guard](./images/click-enable-dataguard.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***. + + + + +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. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/enable-dataguard/images/choose-database-home.png b/exadata-database-service-dedicated/enable-dataguard/images/choose-database-home.png new file mode 100644 index 0000000..b5ea5bd Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/choose-database-home.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/click-enable-dataguard.png b/exadata-database-service-dedicated/enable-dataguard/images/click-enable-dataguard.png new file mode 100644 index 0000000..96595e0 Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/click-enable-dataguard.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/dg-association-details.png b/exadata-database-service-dedicated/enable-dataguard/images/dg-association-details.png new file mode 100644 index 0000000..9ae04c8 Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/dg-association-details.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/enable-dataguard.png b/exadata-database-service-dedicated/enable-dataguard/images/enable-dataguard.png new file mode 100644 index 0000000..35064b2 Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/enable-dataguard.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/navigate-dg-association.png b/exadata-database-service-dedicated/enable-dataguard/images/navigate-dg-association.png new file mode 100644 index 0000000..d2f569b Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/navigate-dg-association.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/navigate-exadbcc-vmcluster.png b/exadata-database-service-dedicated/enable-dataguard/images/navigate-exadbcc-vmcluster.png new file mode 100644 index 0000000..fdc1056 Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/navigate-exadbcc-vmcluster.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/select-cdb.png b/exadata-database-service-dedicated/enable-dataguard/images/select-cdb.png new file mode 100644 index 0000000..be412cb Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/select-cdb.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/select-compartment.png b/exadata-database-service-dedicated/enable-dataguard/images/select-compartment.png new file mode 100644 index 0000000..dea4e7f Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/select-compartment.png differ diff --git a/exadata-database-service-dedicated/enable-dataguard/images/select-peer-vmcluster.png b/exadata-database-service-dedicated/enable-dataguard/images/select-peer-vmcluster.png new file mode 100644 index 0000000..a6c0ee2 Binary files /dev/null and b/exadata-database-service-dedicated/enable-dataguard/images/select-peer-vmcluster.png differ diff --git a/exadata-database-service-dedicated/get-started/get-started.md b/exadata-database-service-dedicated/get-started/get-started.md new file mode 100644 index 0000000..eccc1f8 --- /dev/null +++ b/exadata-database-service-dedicated/get-started/get-started.md @@ -0,0 +1,66 @@ +# 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), and Infrastructure as a Service (IaaS). + +Estimated Time: 5 minutes + +**Types of Cloud Accounts that can be used for this workshop:** + +**Oracle Cloud Paid Accounts**: 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. + +**Global Oracle Solutions Center (OSC) provided 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 access to an OSC provided environment. + + + + +### Objectives + +- For this workshop we will learn how to login to a tenancy provided by the **Global Oracle Solutions Center**. + + +### Prerequisites + +* **Cloud Account Name** - The name of your assigned OSC's Oracle Cloud tenancy + +* **Username** - Your assigned username for this workshop + +* **Password** - Your assigned password for this workshop + + +## Task 1: Log in to Oracle Cloud Tenancy provided by Global Oracle Solutions Center + +1. Go to [**cloud.oracle.com**](https://cloud.oracle.com/?region=us-sanjose-1&tenant=oscnas001) and enter your **Cloud Account Name** *(**Assigned Tenancy**)*. + + For this workshop, make sure your assigned tenancy named ***oscnas001*** is selected. + + + ![osc login](./images/osc-login.png) + + +2. Go to **Oracle Cloud Infrastructure Direct Sign-in** at the bottom of the page and enter your assigned **username** and **password** and click **Sign In** + + ![osc oci direct sign-in](./images/osc-direct-login.png " ") + +3. You are now signed in to Oracle Cloud! + + ![oci login](./images/oci-login-page.png " ") + +## Task 2: Review Exadata Database Service, Exadata Cloud Infrastructure, Custom Database & Application Images, and Oracle Database Cloud MAA + + *(For this lab, The Exadata Database Service on Cloud@Customer Resource Model is pre-provisioned - Informational Instructions for navigating the Exadata Database Service on Cloud@Customer environment will be presented by the speakers)* + +You may now **proceed to the next lab**. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/get-started/images/oci-login-page.png b/exadata-database-service-dedicated/get-started/images/oci-login-page.png new file mode 100644 index 0000000..52160a8 Binary files /dev/null and b/exadata-database-service-dedicated/get-started/images/oci-login-page.png differ diff --git a/exadata-database-service-dedicated/get-started/images/osc-direct-login.png b/exadata-database-service-dedicated/get-started/images/osc-direct-login.png new file mode 100644 index 0000000..49c228b Binary files /dev/null and b/exadata-database-service-dedicated/get-started/images/osc-direct-login.png differ diff --git a/exadata-database-service-dedicated/get-started/images/osc-login.png b/exadata-database-service-dedicated/get-started/images/osc-login.png new file mode 100644 index 0000000..1f5f1dc Binary files /dev/null and b/exadata-database-service-dedicated/get-started/images/osc-login.png differ diff --git a/exadata-database-service-dedicated/introduction/introduction.md b/exadata-database-service-dedicated/introduction/introduction.md new file mode 100644 index 0000000..637cce1 --- /dev/null +++ b/exadata-database-service-dedicated/introduction/introduction.md @@ -0,0 +1,48 @@ +# Introduction + +## About this Workshop + +In this hands-on class, you’ll deploy and configure Oracle databases using the Exadata Database Service in our lab environment, leveraging the user interface web console and Terraform. + +In one of the most real-world classes you’ll ever attend, you’ll learn the latest techniques designed to simplify operational tasks and automate standards-based deployments of the database for your applications. You will use cloud automation functions to create database environments leveraging VM Cluster Node Subsetting consolidation feature. . You’ll learn how the Exadata platform embraces cloud economics to control costs with the ability to scale CPUs up and down and to scale out compute and storage nodes. + +To meet your desired SLA levels, you’ll 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. + +Don’t miss your chance to learn how to use cloud automation functions to standardize your database cloud environments, all while realizing the performance and scale of the Oracle Database on the Exadata Cloud Platform that is available to all types of workloads. + +Estimated Workshop Time: 160 minutes + +**What is an Oracle Exadata Database Service?** + +Oracle Exadata Database Service is a high-performance co-managed Oracle Cloud Database service that allows organizations to run databases with extreme performance, availability, and security cost-effectively. Databases run faster and with fewer resources on scale-out Exadata infrastructure that includes unique optimizations for transaction processing, analytics, and mixed workloads. Online scaling of computing resources enables customers to quickly adjust consumption to match workload demands without interrupting operations, while efficient database consolidation further lowers total costs. Full compatibility with on-premises Oracle Database and Exadata environments makes it easy for customers to migrate workloads to the cloud. + +Exadata Database Service allows you to leverage the power of Exadata in the cloud. +Exadata Database Service’s scale-out architecture allows customers to provision more compute and storage independently, to be able to +easily right-size their service to meet their growing workload demand. +Exadata Database Service offer RDMA over Converged Ethernet (RoCE) networking for high bandwidth and low latency, Exadata RDMA Memory (XRMEM) Cache, and intelligent Exadata software. + +Exadata Database Service reduces downtime and simplifies operational management with zero downtime maintenance, online scaling, and one-click provisioning of Oracle Real Application Clusters (Oracle RAC) and Oracle Active Data Guard using built-in cloud automation. Exadata Database Service has built-in Oracle Maximum Availability Architecture (Oracle MAA) best practices that help it to increase database availability out of the box. + + + +**What is an Oracle Exadata Database Service on Cloud@Customer?** + +Oracle Exadata Database Service on Cloud@Customer enables you to apply the combined power of Oracle Exadata and Oracle Cloud Infrastructure inside your own data center. You have full access to the features and capabilities of Oracle Database along with the intelligent performance and scalability of Oracle Exadata, but with Oracle owning and managing the Exadata infrastructure. You can use the Oracle Cloud Infrastructure console and APIs to manage Oracle Exadata Database Service on Cloud@Customer just as with any other cloud resource, while maintaining absolute sovereignty over your data. + +Oracle Exadata Database Service on Cloud@Customer is the simplest way to move an organization’s business-critical Oracle Database workloads to the cloud. It simultaneously runs Oracle Exadata Database Service and the fully managed Oracle Autonomous Database Service inside customers’ data centers and behind their firewalls to help meet strict data residency and security requirements. + +Oracle Exadata Database Service on Cloud@Customer provides the same user experience as Exadata Database Service on Dedicated Infrastructure with Oracle-owning and managing the infrastructure that is located in your data center. + +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-whats-new-in-exadata-cloud-at-customer-gen2.html#GUID-2F27E5A9-67A8-459E-9453-81E1F68043DE) to learn about What's New in Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/node-subsetting/node-subsetting.md b/exadata-database-service-dedicated/node-subsetting/node-subsetting.md new file mode 100644 index 0000000..87bfac8 --- /dev/null +++ b/exadata-database-service-dedicated/node-subsetting/node-subsetting.md @@ -0,0 +1,51 @@ + + + +# Scale Exadata VM Cluster to run on a Subset of the available compute nodes + + +## Introduction + +This lab walks you through the steps to Scale Exadata VM Cluster to run on a Subset of the available compute nodes. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Scale Exadata VM Cluster to run on a Subset of the available compute nodes + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Scale Exadata VM Cluster to run on a Subset of the available compute nodes + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + +3. In the VM Cluster Details page, under **Resources**, click **Virtual Machines**, and then click Add **Virtual Machines**. + +4. On the **Add Virtual Machines** page, select additional DB servers on which to add the VM. + + * Select the DB servers with the **Available to add** status and then click **Save Changes**. + +5. Note that the expansion of the VM Cluster will show the additional VM Capacity on the **VM Cluster Details page** and that the status of the VM Cluster will remain in the ***Updating*** state until the VMs are fully added. + + +## Learn More + +* Click [here](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-manage-vm-clusters.html#GUID-53A7D800-C948-4160-BA46-C9D7907E247A) to learn more about VM Cluster Node Subsetting for Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/review-ocw-env/images/create-database.png b/exadata-database-service-dedicated/review-ocw-env/images/create-database.png new file mode 100644 index 0000000..cc1c740 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/create-database.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster-network.png b/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster-network.png new file mode 100644 index 0000000..97aaf4d Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster-network.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster.png b/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster.png new file mode 100644 index 0000000..634ecd1 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/create-vm-cluster.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/createexainfra.png b/exadata-database-service-dedicated/review-ocw-env/images/createexainfra.png new file mode 100644 index 0000000..000d594 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/createexainfra.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/discover-app-server.png b/exadata-database-service-dedicated/review-ocw-env/images/discover-app-server.png new file mode 100644 index 0000000..a181754 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/discover-app-server.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/myexadb-details-page.png b/exadata-database-service-dedicated/review-ocw-env/images/myexadb-details-page.png new file mode 100644 index 0000000..5579f1b Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/myexadb-details-page.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/mypdb-list.png b/exadata-database-service-dedicated/review-ocw-env/images/mypdb-list.png new file mode 100644 index 0000000..23dc1cf Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/mypdb-list.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/mypdb-page.png b/exadata-database-service-dedicated/review-ocw-env/images/mypdb-page.png new file mode 100644 index 0000000..198741b Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/mypdb-page.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/navigate-cdb.png b/exadata-database-service-dedicated/review-ocw-env/images/navigate-cdb.png new file mode 100644 index 0000000..8e728d7 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/navigate-cdb.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/navigate-compute.png b/exadata-database-service-dedicated/review-ocw-env/images/navigate-compute.png new file mode 100644 index 0000000..1555dfb Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/navigate-compute.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/navigate-vmcluster.png b/exadata-database-service-dedicated/review-ocw-env/images/navigate-vmcluster.png new file mode 100644 index 0000000..e4c8972 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/navigate-vmcluster.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/navigateocimenu.png b/exadata-database-service-dedicated/review-ocw-env/images/navigateocimenu.png new file mode 100644 index 0000000..ad2d999 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/navigateocimenu.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/pdb-connection-string.png b/exadata-database-service-dedicated/review-ocw-env/images/pdb-connection-string.png new file mode 100644 index 0000000..404e7a3 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/pdb-connection-string.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/run-sqldeveloper.png b/exadata-database-service-dedicated/review-ocw-env/images/run-sqldeveloper.png new file mode 100644 index 0000000..670a627 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/run-sqldeveloper.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/sgd-linux-desktop.png b/exadata-database-service-dedicated/review-ocw-env/images/sgd-linux-desktop.png new file mode 100644 index 0000000..9419a73 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/sgd-linux-desktop.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/sgd-login.png b/exadata-database-service-dedicated/review-ocw-env/images/sgd-login.png new file mode 100644 index 0000000..cf3401e Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/sgd-login.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/sqldev.png b/exadata-database-service-dedicated/review-ocw-env/images/sqldev.png new file mode 100644 index 0000000..3213291 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/sqldev.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/ssh-app-tool.png b/exadata-database-service-dedicated/review-ocw-env/images/ssh-app-tool.png new file mode 100644 index 0000000..86db83d Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/ssh-app-tool.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion-login.png b/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion-login.png new file mode 100644 index 0000000..ff30ad0 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion-login.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion.png b/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion.png new file mode 100644 index 0000000..3723828 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/ssh-oscbastion.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/vm-client-ip.png b/exadata-database-service-dedicated/review-ocw-env/images/vm-client-ip.png new file mode 100644 index 0000000..4c0f210 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/vm-client-ip.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/images/vmcluster-details-page.png b/exadata-database-service-dedicated/review-ocw-env/images/vmcluster-details-page.png new file mode 100644 index 0000000..6e96627 Binary files /dev/null and b/exadata-database-service-dedicated/review-ocw-env/images/vmcluster-details-page.png differ diff --git a/exadata-database-service-dedicated/review-ocw-env/review-ocw-env.md b/exadata-database-service-dedicated/review-ocw-env/review-ocw-env.md new file mode 100644 index 0000000..d85947e --- /dev/null +++ b/exadata-database-service-dedicated/review-ocw-env/review-ocw-env.md @@ -0,0 +1,164 @@ + + + +# Discover and Connect to Oracle CloudWorld Lab Resources + + +## Introduction + +This lab walks you through on how to discover and connect to the Oracle Cloud World lab resources. + +Estimated Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to learn how to navigate, discover and connect to the Oracle Cloud World lab resources. + +### Prerequisites + +This lab requires completion of the following: + +* Login to **Oracle Cloud** using **OSC's tenancy** with your assigned workshop credentials + + + + + +## Task 1: Discover and Connect to the Application Server (Oracle Cloud Developer Image) + +1. Open the navigation menu. Under **Compute**, click **Instances**. + + ![navigage compute](./images/navigate-compute.png " ") + +2. Under Compute, Click on **Instances** + +3. Select your assigned **Compartment**. + + From the list of Instances displays. Find the Compute named ***MyCustomAppServer***, and document the ***Private IP address*** for later use. + + ![discover compute networking details](./images/discover-app-server.png " ") + + +4. Open your local terminal and run the command to connect to the local OSC Bastion Server + + ``` + + + ssh -i ~/sshkey_student_xx.key -l {login name} ocw23oscbastion + + + ``` + + >**Note:** Replace the **{login name}** with your assigned username login ***student_XX*** for the local OSC Bastion Server + +5. From the local OSC Bastion Server, Run the command to connect to the Application Server with SSH. + + ``` + + + ssh -i ~/sshkey_student_xx.key -l opc {App Server IP Address} + + + ``` + + >**Note:** Replace the **{App Server IP Address}** with the ***Private IP address of the Application Server*** you obtained from *Step 3* + +## Task 2: Discover and Connect to an Exadata Database Service Virtual Machine with SSH + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + + ![navigage oci console](./images/navigateocimenu.png " ") + +2. Select your assigned **Compartment**, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + + ![navigate to exadata vmcluster](./images/navigate-vmcluster.png " ") + + The VM Cluster Details page displays information about the selected VM cluster. + + ![exadata vmcluster details page](./images/vmcluster-details-page.png " ") + + +3. Under the **Resources** section on the left banner, click on **Virtual Machines**. + + The list of virtual machines displays. The **name**, **state**, and **client IP address** are displayed for each virtual machine in the VM cluster. + +4. Find and document the **Client IP Address** of the first virtual machine for later use. + + ![VM Client IP](./images/vm-client-ip.png" ") + +5. From the Application Server, Run the command to connect to the Exadata Database Service Virtual Machine with SSH. + + ``` + + + ssh -i ~/sshkey_student_xx.key -l opc {Exadata VM IP Address} + + + ``` + + >**Note:** Replace **{Exadata VM IP Address}** with the Exadata Virtual Machine ***Client IP Address*** obtained from *step 4* + +## Task 3: Discover and Connect to the Oracle Database on Exadata Database Service with Oracle Sqldeveloper + +1. From the Virtual Machines list page, Under the **Resources** section on the left banner, Click on **Databases**, then Click on the **Container Database** named **MyCDB01**. + + ![Navigate CDB](./images/navigate-cdb.png" ") + +2. Under the **Resources** section on the left banner, Click on **Pluggable Databases**. Then Click on the **Pluggable Database** named **MyPDB**. + + ![PDB list menu](./images/mypdb-list.png" ") + +3. In the **Pluggable Databases section** of the page, Near the top, Click on the **PDB Connection** button. + + ![PDB list menu](./images/mypdb-page.png" ") + +4. This will render the **Pluggable Database Connection** Screen. **Click** the **Copy Link** and paste the **Connection String** to your notepad or text editor. + + ![PDB Connection](./images/pdb-connection-string.png" ") + +1. From the Application Server, Open the terminal and Run ***sqldeveloper*** to launch Oracle SQL Developer. + + + + ![launch sqldeveloper](./images/run-sqldeveloper.png " ") + + + + + From the Oracle SQL Developer page provide the following information to connect to Oracle Database on Exadata Database Service. + + ![connecting using sqldev](./images/sqldev.png" ") + + * Click **Create New Connection** Icon + * Enter a **Name** for the Connection + * For the **Database Type**, select **Oracle** + * For the **Username**, enter **Sys** + * Enter the Sys **password** + * For the Role, select **SYSDBA** + * For the **Hostname**, enter the **Hostname** *(from the PDB connection string - obtained from Step 4)* + * For the **Port** enter **1521** + * Enter the Database **Service Name**, enter the **Service Name** *(from the PDB connection string - obtained from Step 4)* + * **Test** & **Save** the connection + * Click on **Connect** + + + + +You may now **proceed to the next lab**. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshell.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshell.png new file mode 100644 index 0000000..c420124 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshell.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshelllaunch.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshelllaunch.png new file mode 100644 index 0000000..ee78be0 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/copy-compartment-ocid.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/copy-compartment-ocid.png new file mode 100644 index 0000000..dfefc84 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/copy-compartment-ocid.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/navigateocimenu.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/navigateocimenu.png new file mode 100644 index 0000000..ad2d999 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/navigateocimenu.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-ocpu.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-ocpu.png new file mode 100644 index 0000000..4e3b20a Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-ocpu.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png new file mode 100644 index 0000000..f305533 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/vmcluster-details-page.png b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/vmcluster-details-page.png new file mode 100644 index 0000000..c4bc910 Binary files /dev/null and b/exadata-database-service-dedicated/scale-resources-using-oci-cli/images/vmcluster-details-page.png differ diff --git a/exadata-database-service-dedicated/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md b/exadata-database-service-dedicated/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md new file mode 100644 index 0000000..e0266df --- /dev/null +++ b/exadata-database-service-dedicated/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md @@ -0,0 +1,94 @@ + + + +# Scale Exadata VM Cluster Resources using OCI CLI + + +## Introduction + +The OCI CLI is a small footprint tool that you can use on its own or with the Console to perform Database Cloud Services resource tasks and other OCI tasks. The CLI provides the same core functionality as the Console, plus additional commands. Some of these, such as the ability to run scripts, extend the Console's functionality. + +**Cloud Shell**: The CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell. + +**Oracle Linux Cloud Developer image**: The CLI is pre-installed on the Oracle Linux Cloud Developer platform image. For more information. + +The CLI is built on the Oracle Cloud Infrastructure SDK for Python and runs on Mac, Windows, or Linux. The Python code makes calls to Oracle Cloud Infrastructure APIs to provide the functionality implemented for the various services. These are REST APIs that use HTTPS requests and responses. + +This lab walks you through the steps to Scale the Exadata VM Cluster OCPU resource using OCI CLI. + +Estimated Time: 10 minutes + + +### Objectives + +- After completing this lab, you should be able to scale Exadata VM Cluster OCPU resource using OCI CLI + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + + +## Task 1: Scale Exadata VM Cluster OCPU using OCI CLI + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + + ![navigage oci console](./images/navigateocimenu.png " ") + +2. In the left rail, **Exadata VM Clusters** is selected by default. Select your assigned Compartment ***MyCompartmentXX***. + + Click on the name of your assigned VM Cluster ***MyVMClusterXX***. The VM Cluster Details page displays information about the selected VM cluster. + + Under the **General Information**, In the OCID Field. Click on **Show** to display the VM Cluster OCID, and Click on **Copy** and paste the **VM Cluster OCID** to your notepad or text editor. + + Under the **Resource allocation**, pay attention to the number of ***OCPUs:*** which has the value of ***6*** + + ![vm cluster details page](./images/vmcluster-details-page.png " ") + +3. To use OCI CLI for this lab, we will be using the ***Cloud OCI Shell tool***, where CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell in the OCI Web Console. + + Click the Cloud Shell/Code Editor icon in the Console header and select Cloud Shell from the drop-down menu. + + ![oci cloudshell](./images/cloudshell.png " ") + + This displays the Cloud Shell in a "drawer" at the bottom of the console: + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + +4. Run the OCI CLI Command to Scale down the **VM Cluster OCPU Resources** from **6 OCPUs** to **4 OCPUs** + + >**Note:** Replace ***{vmClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 2)* + + ``` + + + oci db vm-cluster update --vm-cluster-id {vmClusterId} --cpu-core-count 4 --query 'data.{VMClusterOCID:id, DisplayName:"display-name", LifecycleState:"lifecycle-state", CompartmentOCID:"compartment-id"}' + + + ``` + + ![scale number of ocpus](./images/scale-ocpu.png " ") + + After running the command, you will see similar output below. + + ![LifecycleState of updating is displayed for scale number of ocpus](./images/scale-vm-cluster-updating.png " ") + + While the scale up process is running, you can see the LifecycleState of the VM cluster is changed to ***Updating***. Copy the ***Compartment OCID*** from the extracted values of the OCI CLI command results and paste it in your notepad or text editor for later use. + +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-manage-vm-clusters.html#GUID-B9529795-C3D0-423A-B83F-BDD96AB29E32) to learn more about Scaling Up or Scaling Down the VM Cluster Resources for Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/oci-menu-orm.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/oci-menu-orm.png new file mode 100644 index 0000000..8481b5d Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/oci-menu-orm.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-stack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-stack.png new file mode 100644 index 0000000..b9a8eec Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-stack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png new file mode 100644 index 0000000..422b6e9 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-click-plan.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-click-plan.png new file mode 100644 index 0000000..e788b2c Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-click-plan.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png new file mode 100644 index 0000000..04b03e1 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png new file mode 100644 index 0000000..991de1d Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png new file mode 100644 index 0000000..cfcf1c9 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack.png new file mode 100644 index 0000000..39b0c44 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-create-stack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png new file mode 100644 index 0000000..aa74815 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png new file mode 100644 index 0000000..df2643b Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png new file mode 100644 index 0000000..120d1f0 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png new file mode 100644 index 0000000..4fca335 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png new file mode 100644 index 0000000..be22129 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png new file mode 100644 index 0000000..73c1292 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png new file mode 100644 index 0000000..7701c6b Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png new file mode 100644 index 0000000..540f898 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png new file mode 100644 index 0000000..404e212 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-job.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-job.png new file mode 100644 index 0000000..ac0cc19 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-job.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png new file mode 100644 index 0000000..e7032e3 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-success.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-success.png new file mode 100644 index 0000000..958768d Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-plan-success.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png new file mode 100644 index 0000000..bb9e736 Binary files /dev/null and b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png differ diff --git a/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md new file mode 100644 index 0000000..53a2d2c --- /dev/null +++ b/exadata-database-service-dedicated/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md @@ -0,0 +1,327 @@ +# Use OCI Resource Manager to generate and deploy Terraform for Application and Database Stack + + +## Introduction + +This lab walks you through the steps to generate and deploy Terraform for Application and Database stack using OCI Resource Manage. + +Estimated Time: 20 minutes + + +### Objectives + +- After completing this lab, you should be able to generate and deploy Terraform for Application and Database stack using OCI Resource Manager. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab7** + +## Task 1: Generate Terraform baseline configuration for Database development environment using OCI Resource Manager + +1. Open the navigation menu and click **Developer Services**. Under **Resource Manager**, click **Stacks**. + + ![Launch ORM Stacks](./images/oci-menu-orm.png " ") + +2. On the **Stacks** page, select your assigned compartment. + +3. Click **Create stack**. + +4. On the **Create stack** page, under **Choose the origin of the Terraform configuration**, select **Existing compartment**. + +5. Select your assigned **compartment** and assigned **region** containing the Exadata Database Service on Cloud@Customer Resource Model. + + ![select compartment for resource discovery](./images/orm-create-stack-from-compartment.png " ") + + This will create a stack that captures resources from the selected assigned compartment using **OCI Resource Manager (resource discovery)** + +6. Select the service types that you want to be discovered for your terraform script by: Selecting **Selected** for the Terraform provider services and then selecting **database** for the services value. + + ![Select compartment to create stack](./images/orm-discover-dbstack.png " ") + +7. Provide the **Name** for your stack and Select the **compartment** where you want to create the stack. + + >**Note:** For this lab, use **MyTFBaseline-Database** for the name of your discovered database stack and use your assigned compartment for the **Create in compartment** + + ![Create your discovered database stack](./images/orm-create-stack.png " ") + + + +8. Click **Next** twice. No variables are listed for the Existing compartment stack origin because no Terraform configuration exists yet. + +9. In the Review panel, verify the stack configuration. Take note of the Terraform version for future use on your stack deployment. + + ![Create database stack](./images/orm-create-stack-database.png " ") + +10. Click **Create**. + + + +11. Once the newly created stack is available, Download a copy of the generated Terraform script by clicking on the **Download** link next to **Terraform configuration**. + + ![Download database stack](./images/orm-download-dbstack.png " ") + + After downloading the zip file, you can unzip the file and view the generated Terraform configuration file in your text or code editor. + + View the *database.tf* file. + + >**Note:** Your database's generated baseline terraform code is similar to the output below. *Resources discovered in the Baseline Terraform configuration will be presented and discussed by the speakers*. Notes are added on each section of the discovered Exadata Database Service Resource Model + + This is the discovered resource for the **Custom Database Software image** + + ``` + + + ## This configuration was generated by terraform-provider-oci + + + ## This is the discovered resource for the Custom Database Software image + + resource oci_database_database_software_image export_MyCustomDBSW { + compartment_id = var.compartment_ocid + database_software_image_one_off_patches = [ + "29780459", + "30310195", + ] + database_version = "19.0.0.0" + defined_tags = { + } + display_name = "MyCustomDBSW" + freeform_tags = { + } + image_shape_family = "EXACC_SHAPE" + image_type = "DATABASE_IMAGE" + patch_set = "19.11.0.0" + } + + + ``` + + This is the discovered resource for the **Exadata VM Cluster Resource** + + + ``` + + + + ## This is the discovered resource for the Exadata VM Cluster Resource + + resource oci_database_vm_cluster export_MyVMClusterXX { + compartment_id = var.compartment_ocid + cpu_core_count = "0" + data_collection_options { + is_diagnostics_events_enabled = "true" + is_health_monitoring_enabled = "true" + is_incident_logs_enabled = "true" + } + data_storage_size_in_tbs = "30" + db_node_storage_size_in_gbs = "120" + db_servers = [ + "ocid1.dbserver.oc1.us-sanjose-1.aaaaaaaaaaaaa", + "ocid1.dbserver.oc1.us-sanjose-1.aaaaaaaaaaaaa", + ] + defined_tags = { + } + display_name = "MyVMClusterXX" + exadata_infrastructure_id = "ocid1.exadatainfrastructure.oc1.us-sanjose-1.a" + freeform_tags = { + } + gi_version = "19.19.0.0.0" + is_local_backup_enabled = "false" + is_sparse_diskgroup_enabled = "true" + license_model = "BRING_YOUR_OWN_LICENSE" + memory_size_in_gbs = "60" + ssh_public_keys = [ + ] + time_zone = "UTC" + vm_cluster_network_id = "ocid1.vmclusternetwork.oc1.us-sanjose-1.aaaaaaaa" + } + + + ``` + + This is the discovered resource for the **Database Home** + + ``` + + + ## This is the discovered resource for the Database Home + + resource oci_database_db_home export_MyCustomDBHome { + db_version = "19.18.0.0.0" + defined_tags = { + } + display_name = "MyCustomDBHome" + freeform_tags = { + } + source = "NONE" + vm_cluster_id = oci_database_vm_cluster.export_MyVMClusterXX.id + } + + + ``` + This is the discovered resource for the **Container Database** + + ``` + + + + ## This is the discovered resource for the Container Database + + resource oci_database_database export_MyCustomDBHome_database { + database { + admin_password = "" + character_set = "AL32UTF8" + db_name = "MyCDB01" + db_unique_name = "cdb01" + db_workload = "OLTP" + defined_tags = { + } + freeform_tags = { + } + ncharacter_set = "AL16UTF16" + pdb_name = "mypdb1" + sid_prefix = "myexadbcc" + } + db_home_id = oci_database_db_home.export_MyCustomDBHome.id + source = "NONE" #Required attribute + lifecycle { + ignore_changes = [source, database[0].admin_password] + } + } + + + ``` + + This is the discovered resource for the **Pluggable Databases** + + ``` + + + + ## This is the discovered resource for the Pluggable Databases + + resource oci_database_pluggable_database export_pluggable_database { + container_database_id = oci_database_database.export_MyDBHome_database.id + defined_tags = { + } + freeform_tags = { + } + #pdb_admin_password = + pdb_name = "MYPDB" + } + + resource oci_database_pluggable_database export_pluggable_database_1 { + container_database_id = oci_database_database.export_MyDBHome_database.id + defined_tags = { + } + freeform_tags = { + } + #pdb_admin_password = + pdb_name = "MYCLONEPDB" + } + + + ``` + +## Task 2: Deploy Gold Image Stack (Database and MyDesktop Application) using OCI Resource Manager and Terraform + +1. In the Breadcrumb link, Click on **Stacks** then select your assigned **compartment** and Click **Create stack**. + + ![Deploy App and DB Stack](./images/orm-deploy-app-dbstack.png " ") + +2. On the **Create stack** page, under Choose the origin of the Terraform configuration, select **My configuration**. + + Select **.Zip file** for the Terraform configuration source. then browse your desktop for a file called ***SampleTF.zip***. + + + ![Upload zip file to deploy App and DB Stack](./images/orm-deploy-app-dbstack-from-zip.png " ") + + +3. Provide the **Name** for your stack and select the **compartment** where you want to create the stack. + + >**Note:** For this lab, use ***MyAppDBStack*** for the name of your discovered database stack and use your assigned compartment for the **Create in compartment** + +4. For Terraform version, select the *version 1.2.x*. + + ![Upload zip file to deploy App and DB Stack](./images/orm-create-name-stack.png " ") + +5. Click **Next**. In the **Configure variables panel**, review and provide the required variables listed from the Terraform configuration. + + Provide required variable details for the **Application Server Stack**. + + ![Deploy Application Stack](./images/orm-deploy-application-stack.png " ") + + * Choose your **Assigned compartment** + * Provide the **Application Server display name**. For this lab, use the name ***MyAppServer2*** + * Provide the **Custom Instance Image Source ID**. For DatabaseWorld, accept the default value + + Provide required variable details for the **Exadata Database Server Stack**. + + ![Deploy Database PDB Stack](./images/orm-deploy-exadata-database-pdb.png " ") + + * Provide the **Developer Container Database OCID**. For this lab, use the value for the ***MyCDB01*** obtained from ***Lab7 (Task 2 Step 2)*** + * Provide the **Pluggable Database display name**. For this lab, use the name ***MyPDB2*** + * Provide the **Pluggable Database administrator password** + + Click on **Next** + +6. In the **Review** panel, verify the stack configuration and Click **Create** to establish your customized stack. + + ![Review App and Database Stack](./images/orm-deploy-app-db-review.png " ") + + >**Note:** Now that we have a defined stack, let's prepare to use the stack to deploy a new developer environment consisting of an Application Server and 1 Exadata Container Database and 3 Pluggable Databases. + + ![App and Database Available Stack](./images/orm-myappdbstack-available.png " ") + +7. Create Stack Deployment Plan by: Clicking on **Plan** on the Stack details page. + + ![Create Stack Deployment Plan](./images/orm-plan-job.png " ") + + In the Plan panel, use ***MyAppDBStackPlan*** for the Plan name and then Click on **Plan** to proceed. + + ![Confirm Create Stack Deployment Plan](./images/orm-click-plan.png " ") + + >**Note:** The plan job is created and is listed under Jobs. + + When the Stack Deployment Plan process is completed, the state of the plan job changes to **Succeeded**. + + ![Stack Deployment Plan Succeeded](./images/orm-plan-success.png " ") + + +8. In the **Breadcrumb** link, Click on **Stack details**. + + ![View Stack Details Page ](./images/orm-plan-stackdetails.png " ") + + Process Stack Deployment Plan by clicking on **Apply**. + + ![Create Stack Deployment Apply ](./images/orm-stackdetails-apply.png " ") + + In the Apply panel, edit the default name for the job. For this lab, we will use ***MyAppDBStackApply*** for the Apply name. + + Select **Automatically Approve** for the Apply job plan resolution and then Click on **Apply**. + + ![Click Stack Deployment Apply ](./images/orm-apply-stack.png " ") + + >**Note:** This will cause the apply job to be created and our new Application and Database stack to be deployed once the job is completed. + + ![Stack Deployment Apply Succeeded ](./images/orm-apply-succeeded.png " ") + +You may now **proceed to the next lab** + + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-on-cc/workshops/tenancy/index.html b/exadata-database-service-dedicated/workshops/ocw23-tenancy/index.html similarity index 100% rename from exadata-database-service-on-cc/workshops/tenancy/index.html rename to exadata-database-service-dedicated/workshops/ocw23-tenancy/index.html diff --git a/exadata-database-service-dedicated/workshops/ocw23-tenancy/manifest.json b/exadata-database-service-dedicated/workshops/ocw23-tenancy/manifest.json new file mode 100644 index 0000000..70700ae --- /dev/null +++ b/exadata-database-service-dedicated/workshops/ocw23-tenancy/manifest.json @@ -0,0 +1,84 @@ +{ + "workshoptitle": "Deliver Exadata Database Performance and Scale with Oracle Cloud Master Class", + + "help": "livelabs-help-db_us@oracle.com", + + "tutorials": [ + { + "title": "Introduction", + "description": "Introduction", + "filename": "../../introduction/introduction.md" + }, + { + "title": "Get started - Connect to Oracle Cloud Tenancy", + "description": "Learn how to connect to Oracle Cloud Tenancy", + "filename": "../../get-started/get-started.md" + }, + { + "title": "Lab 1: Discover and Connect to Cloud World Lab Resources", + "description": "Learn how to discover and connect to OCW Lab Resources", + "filename": "../../review-ocw-env/review-ocw-env.md" + + }, + { + "title": "Lab 2: Create Application and Database Custom Image using OCI Console", + "description": "Learn how to Create Database Custom Image using OCI Console", + "filename": "../../create-database-custom-image/create-database-custom-image.md" + }, + { + "title": "Lab 3: Enable Data Guard for local HA using OCI Console", + "description": "Learn how to enable Data Guard for local HA using OCI Console", + "filename": "../../enable-dataguard/enable-dataguard.md" + }, + { + "title": "Lab 4: Configure Notifications for Enabled OCPU or License Type change", + "description": "Learn how to configure Notifications for enabled OCPU or license type change", + "filename": "../../configure-notifications/configure-notifications.md" + }, + { + "title": "Lab 5: Change License Type using OCI Console", + "description": "Learn how to change license type using OCI Console", + "filename": "../../change-license-type/change-license-type.md" + }, + { + "title": "Lab 6: Scale Exadata VM Cluster Resources using OCI CLI", + "description": "Learn how to scale Exadata VM Cluster resources using OCI CLI", + "filename": "../../scale-resources-using-oci-cli/scale-resources-using-oci-cli.md" + }, + { + "title": "Lab 7: Discover Environment Details using REST API", + "description": "Learn how to discover environment details using REST API", + "filename": "../../discover-env-details-api/discover-env-details-api.md" + }, + { + "title": "Lab 8: Use OCI Resource Manager to generate and deploy Terraform for Application and Database Stack", + "description": "Learn how to Use OCI Resource Manager to generate Terraform for Application and Database Stack", + "filename": "../../use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md" + }, + { + "title": "Lab 9: Review Enable Automatic Backups", + "description": "Learn how to Enable Automatic Backups", + "filename": "../../enable-automatic-backups/enable-automatic-backups.md" + }, + { + "title": "Lab 10: Review Option to configure Automatic Infrastructure Maintenance", + "description": "Learn how to configure Automatic Infrastructure Maintenance", + "filename": "../../automatic-infrastructure-maintenance/automatic-infrastructure-maintenance.md" + }, + { + "title": "Lab 11: Scale Exadata VM Cluster to run on a Subset of the available compute nodes", + "description": "Learn how to scale Exadata VM Cluster to run on a Subset of the available compute nodes", + "filename": "../../node-subsetting/node-subsetting.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" + }, + { + "title": "Oracle CloudWorld 2023 - Support", + "description": "Solutions to Common Problems and Directions for Receiving Live Help", + "filename":"https://oracle-livelabs.github.io/common/support/ocwsupportlab/ocwsupportlab.md" + } + ] +} diff --git a/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/index.html b/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/index.html new file mode 100644 index 0000000..aaac634 --- /dev/null +++ b/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/index.html @@ -0,0 +1,62 @@ + + + + + + + + + Oracle LiveLabs + + + + + + + + + + + + +
+
+
+
+
+
+
+
+ + + + + diff --git a/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/manifest.json b/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/manifest.json new file mode 100644 index 0000000..70700ae --- /dev/null +++ b/exadata-database-service-dedicated/workshops/ocw24-exascale-masterclass-sandbox/manifest.json @@ -0,0 +1,84 @@ +{ + "workshoptitle": "Deliver Exadata Database Performance and Scale with Oracle Cloud Master Class", + + "help": "livelabs-help-db_us@oracle.com", + + "tutorials": [ + { + "title": "Introduction", + "description": "Introduction", + "filename": "../../introduction/introduction.md" + }, + { + "title": "Get started - Connect to Oracle Cloud Tenancy", + "description": "Learn how to connect to Oracle Cloud Tenancy", + "filename": "../../get-started/get-started.md" + }, + { + "title": "Lab 1: Discover and Connect to Cloud World Lab Resources", + "description": "Learn how to discover and connect to OCW Lab Resources", + "filename": "../../review-ocw-env/review-ocw-env.md" + + }, + { + "title": "Lab 2: Create Application and Database Custom Image using OCI Console", + "description": "Learn how to Create Database Custom Image using OCI Console", + "filename": "../../create-database-custom-image/create-database-custom-image.md" + }, + { + "title": "Lab 3: Enable Data Guard for local HA using OCI Console", + "description": "Learn how to enable Data Guard for local HA using OCI Console", + "filename": "../../enable-dataguard/enable-dataguard.md" + }, + { + "title": "Lab 4: Configure Notifications for Enabled OCPU or License Type change", + "description": "Learn how to configure Notifications for enabled OCPU or license type change", + "filename": "../../configure-notifications/configure-notifications.md" + }, + { + "title": "Lab 5: Change License Type using OCI Console", + "description": "Learn how to change license type using OCI Console", + "filename": "../../change-license-type/change-license-type.md" + }, + { + "title": "Lab 6: Scale Exadata VM Cluster Resources using OCI CLI", + "description": "Learn how to scale Exadata VM Cluster resources using OCI CLI", + "filename": "../../scale-resources-using-oci-cli/scale-resources-using-oci-cli.md" + }, + { + "title": "Lab 7: Discover Environment Details using REST API", + "description": "Learn how to discover environment details using REST API", + "filename": "../../discover-env-details-api/discover-env-details-api.md" + }, + { + "title": "Lab 8: Use OCI Resource Manager to generate and deploy Terraform for Application and Database Stack", + "description": "Learn how to Use OCI Resource Manager to generate Terraform for Application and Database Stack", + "filename": "../../use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md" + }, + { + "title": "Lab 9: Review Enable Automatic Backups", + "description": "Learn how to Enable Automatic Backups", + "filename": "../../enable-automatic-backups/enable-automatic-backups.md" + }, + { + "title": "Lab 10: Review Option to configure Automatic Infrastructure Maintenance", + "description": "Learn how to configure Automatic Infrastructure Maintenance", + "filename": "../../automatic-infrastructure-maintenance/automatic-infrastructure-maintenance.md" + }, + { + "title": "Lab 11: Scale Exadata VM Cluster to run on a Subset of the available compute nodes", + "description": "Learn how to scale Exadata VM Cluster to run on a Subset of the available compute nodes", + "filename": "../../node-subsetting/node-subsetting.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" + }, + { + "title": "Oracle CloudWorld 2023 - Support", + "description": "Solutions to Common Problems and Directions for Receiving Live Help", + "filename":"https://oracle-livelabs.github.io/common/support/ocwsupportlab/ocwsupportlab.md" + } + ] +} diff --git a/exadata-database-service-dedicated/workshops/tenancy/index.html b/exadata-database-service-dedicated/workshops/tenancy/index.html new file mode 100644 index 0000000..aaac634 --- /dev/null +++ b/exadata-database-service-dedicated/workshops/tenancy/index.html @@ -0,0 +1,62 @@ + + + + + + + + + Oracle LiveLabs + + + + + + + + + + + + +
+
+
+
+
+
+
+
+ + + + + diff --git a/exadata-database-service-dedicated/workshops/tenancy/manifest.json b/exadata-database-service-dedicated/workshops/tenancy/manifest.json new file mode 100644 index 0000000..760e0a6 --- /dev/null +++ b/exadata-database-service-dedicated/workshops/tenancy/manifest.json @@ -0,0 +1,50 @@ +{ + "workshoptitle": "Hands-on: Learn how to automate database, application and stack deployments", + + "help": "livelabs-help-db_us@oracle.com", + + "tutorials": [ + { + "title": "Introduction", + "description": "Introduction", + "filename": "../../introduction/introduction.md" + }, + { + "title": "Get Started", + "description": "Login to Oracle Cloud", + "filename": "https://oracle-livelabs.github.io/common/labs/cloud-login/cloud-login.md" + }, + { + "title": "Lab 1: Review and Connect to Cloud World Lab Environment", + "description": "Review OCW Lab Environment", + "filename": "../../review-ocw-env/review-ocw-env.md" + + }, + { + "title": "Lab 2: Create Database Custom Image using OCI Console", + "description": "Learn how to Create Database Custom Image using OCI Console", + "filename": "../../create-database-custom-image/create-database-custom-image.md" + }, + { + "title": "Lab 3: Scale Exadata VM Cluster OCPU using API", + "description": "Learn how to Scale Exadata VM Cluster OCPU using API", + "filename": "../../scale-vmcluster-ocpu-api/scale-vmcluster-ocpu-api.md" + }, + { + "title": "Lab 4: Discover Environment Details using SDK", + "description": "Learn how to Discover Environment Details using SDK", + "filename": "../../discover-env-details-sdk/discover-env-details-sdk.md" + }, + { + "title": "Lab 5: Use OCI Resource Manager to generate Terraform for Database Stack", + "description": "Learn how to Use OCI Resource Manager to generate Terraform for Database Stack", + "filename": "../../use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.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" + } + ] +} diff --git a/exadata-database-service-on-cc/create-database/create-database.md b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-database/create-database.md similarity index 100% rename from exadata-database-service-on-cc/create-database/create-database.md rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-database/create-database.md diff --git a/exadata-database-service-on-cc/create-exacc-infra/create-exacc-infra.md b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-exacc-infra/create-exacc-infra.md similarity index 100% rename from exadata-database-service-on-cc/create-exacc-infra/create-exacc-infra.md rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-exacc-infra/create-exacc-infra.md diff --git a/exadata-database-service-on-cc/create-vmcluster-network/create-vmcluster-network.md b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-vmcluster-network/create-vmcluster-network.md similarity index 100% rename from exadata-database-service-on-cc/create-vmcluster-network/create-vmcluster-network.md rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-vmcluster-network/create-vmcluster-network.md diff --git a/exadata-database-service-on-cc/create-vmcluster/create-vmcluster.md b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-vmcluster/create-vmcluster.md similarity index 100% rename from exadata-database-service-on-cc/create-vmcluster/create-vmcluster.md rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/create-vmcluster/create-vmcluster.md diff --git a/exadata-database-service-on-cc/introduction/images/exadbcc.png b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/introduction/images/exadbcc.png similarity index 100% rename from exadata-database-service-on-cc/introduction/images/exadbcc.png rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/introduction/images/exadbcc.png diff --git a/exadata-database-service-on-cc/introduction/introduction.md b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/introduction/introduction.md similarity index 100% rename from exadata-database-service-on-cc/introduction/introduction.md rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/introduction/introduction.md diff --git a/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/workshops/tenancy/index.html b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/workshops/tenancy/index.html new file mode 100644 index 0000000..aaac634 --- /dev/null +++ b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/workshops/tenancy/index.html @@ -0,0 +1,62 @@ + + + + + + + + + Oracle LiveLabs + + + + + + + + + + + + +
+
+
+
+
+
+
+
+ + + + + diff --git a/exadata-database-service-on-cc/workshops/tenancy/manifest.json b/exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/workshops/tenancy/manifest.json similarity index 100% rename from exadata-database-service-on-cc/workshops/tenancy/manifest.json rename to exadata-database-service-on-cc/get-started-with-exadb-c@c-workshop/workshops/tenancy/manifest.json diff --git a/exadata-database-service-xs/change-license-type/change-license-type.md b/exadata-database-service-xs/change-license-type/change-license-type.md new file mode 100644 index 0000000..287ae00 --- /dev/null +++ b/exadata-database-service-xs/change-license-type/change-license-type.md @@ -0,0 +1,52 @@ + + + +# Change License Type using OCI Console + + +## Introduction + +This lab walks you through the steps to Change License Type using OCI Console. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Change License Type using OCI Console + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Change License Type using OCI Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + +3. In the VM Cluster Details page, Click **Update License Type** + + ![Update License Type](./images/update-license-type-button.png " ") + +4. Change the license type from **Bring Your Own License (BYOL)** to ***License Included*** + + ![Update License Type](./images/change-license-included.png " ") + +5. Click **Save Changes** + + +You may now **proceed to the next lab** + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/change-license-type/images/change-license-included.png b/exadata-database-service-xs/change-license-type/images/change-license-included.png new file mode 100644 index 0000000..449f3c3 Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/change-license-included.png differ diff --git a/exadata-database-service-xs/change-license-type/images/update-license-type-button.png b/exadata-database-service-xs/change-license-type/images/update-license-type-button.png new file mode 100644 index 0000000..9ba5ff3 Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/update-license-type-button.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md new file mode 100644 index 0000000..58362ac --- /dev/null +++ b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md @@ -0,0 +1,127 @@ + + + +# Configure Notifications for Enabled OCPU or License Type change + + +## Introduction + +This lab walks you through the steps to configure notifications to get notified for VM Cluster Event Types such as Enabled OCPU or License Type change. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to configure notifications and events rules for Exadata Database Service on Cloud@Customer + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Configure Notification Topic and Subscription for Enabled OCPU or License Type change + +1. Open the navigation menu and click **Developer Services**. Under **Application Integration**, click **Notifications**. + + ![Navigate to Notifications](./images/navigate-notifications.png " ") + +2. **Topics** page is selected by default, select your ***Assigned Compartment*** and Click **Create Topic**. + + ![Click Create Topic](./images/create-topic.png " ") + +3. Provide the Topic name. For this lab, use ***MyExaDBCCTopic*** 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 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 ***assigned 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 on the ***Confirm subscription*** link + + ![Confirm Subscription](./images/confirm-subscription.png " ") + + By clicking the confirmation link, it will launch a browser displaying subscription has been confirmed and that you have subscribed your assigned Email to the Topic you have selected. + + ![Subscription Confirmation Display](./images/subscription-confirmation-page.png " ") + + You can now see the subscription is now ***Active*** + + ![Subscription Active](./images/subscription-active.png " ") + + +## Task 2: Create Events Rule to create notification automation based on Enabled OCPU or License Type 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 ***Assigned 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 ***MyExaDBCCEventsRule***. + + ![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 ***VM Cluster - Update Begin*** and ***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 ***Assigned Compartment*** + * For **Topic**, Select ***MyExaDBCCTopic*** + + ![Configure Actions](./images/configure-actions.png " ") + +6. Click **Create Rule** + + ![Create Rule](./images/create-rule.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-customer-events.html#GUID-1BDBB213-B153-48F9-BE06-D85CAD6386B8) to learn more about Exadata Database Service on Cloud@Customer Events. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-rule.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/click-create-rule.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png new file mode 100644 index 0000000..71e0509 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png new file mode 100644 index 0000000..b2de86d Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png new file mode 100644 index 0000000..099cf7e Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png new file mode 100644 index 0000000..623c617 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png new file mode 100644 index 0000000..b76d67d Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png new file mode 100644 index 0000000..e34a16f Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png new file mode 100644 index 0000000..0d60b35 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png new file mode 100644 index 0000000..f496fd0 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png new file mode 100644 index 0000000..dad7582 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png new file mode 100644 index 0000000..ef6825e Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/create-topic.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/navigate-rules.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/navigate-rules.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png b/exadata-database-service-xs/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-xs/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png new file mode 100644 index 0000000..cb68e09 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png new file mode 100644 index 0000000..27b8a0c Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png new file mode 100644 index 0000000..cbd156a Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/create-database-custom-image.md b/exadata-database-service-xs/create-database-custom-image/create-database-custom-image.md new file mode 100644 index 0000000..4aa36be --- /dev/null +++ b/exadata-database-service-xs/create-database-custom-image/create-database-custom-image.md @@ -0,0 +1,92 @@ +# Create Application and Database Custom Image using OCI Console + + +## Introduction + +This lab walks you through creating Application and Database Custom Image using the OCI Console. +  + * **Database software images** are resources containing Oracle Database software used to provision and patch Oracle Databases and Oracle Database Homes. + * **Database software images** are either **Oracle-published software releases** or **custom software images you create**. + * **Custom Database Software Images** include specified patches and updates that meet your organization's standards. + +Estimated Time: 10 minutes + +Watch the video below for a quick walk-through of the lab. + [Create a Custom Database Software Image](youtube:jwxxIih3brQ) + +### Objectives + +- After completing this lab, you should be able to create application and database custom image using the OCI Console. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + +## Task 1: Create Application Custom Image using OCI Console + +1. Open the navigation menu and click **Compute**. Under Compute, click **Instances**. + + ![Naviage OCI Compute](./images/navigate-compute-instance.png" ") + +2. In the left rail, **Instances** is selected by default. Select your assigned compartment named ***MyCompartmentXX***. + + Click on the name of your **Assigned Custom Application Server** named ***MyCustomAppServer***. + + ![Click MyCustomAppServer Instance](./images/click-create-instance.png" ") + +3. Click **More Actions**, and then click **Create custom image**. + + ![Create Custom App Server More Actions](./images/click-instance-more-actions.png " ") + +4. In the **Create in compartment** list, Select your assigned compartment ***MyCompartmentXX*** + + Enter a **Name** for the image. For this lab, use the name ***MyCustomAppServerImage*** + + ![Create Custom App Server Image](./images/create-custom-app-image.png " ") + +5. Click **Create custom image**. + + +## Task 2: Create Custom Database Software Image using OCI Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Under **Resources**, click **Database Software Images**. + +3. Click **Create Database Software Image**. + + ![Create Custom Database Software Image](./images/create-custom-dbsw.png " ") + +4. In the **Display name** field, provide a name for your database software image. For this lab, use the name ***MyCustomDBimage*** + +5. Choose your **assigned compartment** ***MyCompartmentXX***. + + ![Create Custom Database Software Image](./images/create-dbsw-page.png " ") + +6. Choose the **Database version** for your image. For this workshop, select the ***19c*** version. + +7. Choose the **patch set update, proactive bundle patch, or release update**. For this workshop, choose ***19.18.0.0*** + +8. Click **Create Database Software Image**. + + ![Create Custom Database Software Image Dialog Page](./images/create-dbsw-version-page.png " ") + +You may now **proceed to the next lab**. + + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/create-database-custom-image/images/click-create-instance.png b/exadata-database-service-xs/create-database-custom-image/images/click-create-instance.png new file mode 100644 index 0000000..3b8731e Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/click-create-instance.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/click-instance-more-actions.png b/exadata-database-service-xs/create-database-custom-image/images/click-instance-more-actions.png new file mode 100644 index 0000000..6282112 Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/click-instance-more-actions.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/create-custom-app-image.png b/exadata-database-service-xs/create-database-custom-image/images/create-custom-app-image.png new file mode 100644 index 0000000..330217f Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/create-custom-app-image.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/create-custom-dbsw.png b/exadata-database-service-xs/create-database-custom-image/images/create-custom-dbsw.png new file mode 100644 index 0000000..62a1a2e Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/create-custom-dbsw.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-page.png b/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-page.png new file mode 100644 index 0000000..c3aa5e0 Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-page.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-version-page.png b/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-version-page.png new file mode 100644 index 0000000..08f503d Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/create-dbsw-version-page.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/navigate-compute-instance.png b/exadata-database-service-xs/create-database-custom-image/images/navigate-compute-instance.png new file mode 100644 index 0000000..51ecdcc Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/navigate-compute-instance.png differ diff --git a/exadata-database-service-xs/create-database-custom-image/images/oci-mngmt-interfaces.png b/exadata-database-service-xs/create-database-custom-image/images/oci-mngmt-interfaces.png new file mode 100644 index 0000000..61b2bdf Binary files /dev/null and b/exadata-database-service-xs/create-database-custom-image/images/oci-mngmt-interfaces.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md new file mode 100644 index 0000000..4aa36be --- /dev/null +++ b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md @@ -0,0 +1,92 @@ +# Create Application and Database Custom Image using OCI Console + + +## Introduction + +This lab walks you through creating Application and Database Custom Image using the OCI Console. +  + * **Database software images** are resources containing Oracle Database software used to provision and patch Oracle Databases and Oracle Database Homes. + * **Database software images** are either **Oracle-published software releases** or **custom software images you create**. + * **Custom Database Software Images** include specified patches and updates that meet your organization's standards. + +Estimated Time: 10 minutes + +Watch the video below for a quick walk-through of the lab. + [Create a Custom Database Software Image](youtube:jwxxIih3brQ) + +### Objectives + +- After completing this lab, you should be able to create application and database custom image using the OCI Console. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + +## Task 1: Create Application Custom Image using OCI Console + +1. Open the navigation menu and click **Compute**. Under Compute, click **Instances**. + + ![Naviage OCI Compute](./images/navigate-compute-instance.png" ") + +2. In the left rail, **Instances** is selected by default. Select your assigned compartment named ***MyCompartmentXX***. + + Click on the name of your **Assigned Custom Application Server** named ***MyCustomAppServer***. + + ![Click MyCustomAppServer Instance](./images/click-create-instance.png" ") + +3. Click **More Actions**, and then click **Create custom image**. + + ![Create Custom App Server More Actions](./images/click-instance-more-actions.png " ") + +4. In the **Create in compartment** list, Select your assigned compartment ***MyCompartmentXX*** + + Enter a **Name** for the image. For this lab, use the name ***MyCustomAppServerImage*** + + ![Create Custom App Server Image](./images/create-custom-app-image.png " ") + +5. Click **Create custom image**. + + +## Task 2: Create Custom Database Software Image using OCI Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Under **Resources**, click **Database Software Images**. + +3. Click **Create Database Software Image**. + + ![Create Custom Database Software Image](./images/create-custom-dbsw.png " ") + +4. In the **Display name** field, provide a name for your database software image. For this lab, use the name ***MyCustomDBimage*** + +5. Choose your **assigned compartment** ***MyCompartmentXX***. + + ![Create Custom Database Software Image](./images/create-dbsw-page.png " ") + +6. Choose the **Database version** for your image. For this workshop, select the ***19c*** version. + +7. Choose the **patch set update, proactive bundle patch, or release update**. For this workshop, choose ***19.18.0.0*** + +8. Click **Create Database Software Image**. + + ![Create Custom Database Software Image Dialog Page](./images/create-dbsw-version-page.png " ") + +You may now **proceed to the next lab**. + + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-create-instance.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-create-instance.png new file mode 100644 index 0000000..3b8731e Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-create-instance.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-instance-more-actions.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-instance-more-actions.png new file mode 100644 index 0000000..6282112 Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/click-instance-more-actions.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-app-image.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-app-image.png new file mode 100644 index 0000000..330217f Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-app-image.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-dbsw.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-dbsw.png new file mode 100644 index 0000000..62a1a2e Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-custom-dbsw.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-page.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-page.png new file mode 100644 index 0000000..c3aa5e0 Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-page.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-version-page.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-version-page.png new file mode 100644 index 0000000..08f503d Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/create-dbsw-version-page.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/navigate-compute-instance.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/navigate-compute-instance.png new file mode 100644 index 0000000..51ecdcc Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/navigate-compute-instance.png differ diff --git a/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/oci-mngmt-interfaces.png b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/oci-mngmt-interfaces.png new file mode 100644 index 0000000..61b2bdf Binary files /dev/null and b/exadata-database-service-xs/create-thin-clone-pdb-on-exascale/images/oci-mngmt-interfaces.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/create-VMCluster-CDB-PDB-on-Exascale.md b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/create-VMCluster-CDB-PDB-on-Exascale.md new file mode 100644 index 0000000..a4cc3eb --- /dev/null +++ b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/create-VMCluster-CDB-PDB-on-Exascale.md @@ -0,0 +1,187 @@ +# Create Instance of Exadata Database Service on Exascale Infrasturcture using OCI Console + + +## Introduction + +This lab walks you through how to create an instance of the Exadata Database Service on Exascale Infrasturcture using the OCI Console. +  + +Estimated Time: 2 Hours 10 minutes + +Watch the video below for a quick walk-through of the lab. + [Create a Custom Database Software Image](youtube:jwxxIih3brQ) + +### 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. + + +### Prerequisites + +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 Only) --> 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***. + + ![Select Compartment where VM Cluster will reside](./images/select-compartment.png" ") + +3. Click **Create VM Cluster** button + + This causes the **Create VM Cluster** page to be displayed. + +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 ***MyDemoExaDB-XS_VMClusterXX*** + + * 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" ") + +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***. + + **Size the VM file system storage**: + * For system storage capacity per VM (GG): ***Enter 280*** + + **Note:** The VM Filesystems storage includes /u02 capacity, where your Database Homes will go, along with all of the other VM filesystems (/, /boot, /tmp, /var, /var/log, /var/log/audit, /home, swap, kdump, /u01, grid, /u02). Any extra capacity selected beyond system minimums will go into /u02. + + ![Configure VM Cluster](./images/configure-vm-cluster-exascale.png" ") + +6. **Enter Configuration Details for Exascale Database Storage Vault:** + * Select **Create new vault**. + + **For a new vault, specify the following:** + * For the **Exascale Vault name:** enter ***MyDemoVaultXX*** . + * 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. + + 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. + + ![Configure Exascale Storage Vault](./images/configure-exascale-storage-vault.png" ") + +7. **Select the Oracle Grid Infrastructure version and add SSH key:** + * **Grid Infrastructure Release and Version fields:** display the Oracle Grid Infrastructure versions available for deployment in the VM cluster. ***Accept the default values for the 23ai release***. + + * **Add your SSH Key for future access to your VMs**. Choose from: + + * **Generate SSH key pair**(Default option) Select this option to generate an SSH keypair. Then in the dialog below click Save private key to download the key, and optionally click Save public key to download the key. + * **Upload SSH key files**: Select this option to browse or drag and drop .pub files. + * **Paste SSH keys:** Select this option to paste in individual public keys. + + ![Configure Grid Infrastructure and SSH access](./images/configure-grid-infra-and-SSH-access.png" ") + + +8. **To Configure the network settings, Select VCN and select Client and Backup subnet** + * **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 ***ClientAXX***. This is the subnet to which the VM cluster should attach. + * **For the Backup Subnet:** Click Change Compartment and select compartment named ***MyDemo***. Then select the Backup Subnet named ***MyPrivateBackupSubnet***. + * **For the Hostname Prefix:** Enter ***DemoDBXX*** + + ![Configure Network Settings](./images/configure-network-settings.png" ") + +9. **Select license type & choose opt-in choices for Diagnostic & Collections options.** + * **Choose a license type:** The type of license that you want to use for the VM cluster. Your choice affects metering for billing. ***Select the Bring Your Own License (BYOL) option.*** + + ![Choose VM Cluster License Type](./images/choose-license-type.png" ") + +10. **Select Diagnostic and Collections Options** +In the Edit Diagnostics Collection Settings dialog, you can enable or disable any of the Diagnostics Collections options. By enabling diagnostics collection and notifications, Oracle Cloud Operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. ***Accept the default values***. + * **Enable Diagnostics Events:** Allows Oracle to collect and publish critical, warning, error, and information events to me. For more information, see Overview of Database Service Events + * **Enable Health Monitoring:** Allows Oracle to collect health metrics/events such as Oracle Database up/down, disk space usage, and so on, and share them with Oracle Cloud operations. You will also receive notification of some events. + * **Enable Incident logs and trace collection:** Allows Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution. + + ![Choose Diagnostic & Collections options](./images/choose-diagnostic-and-collections-options.png" ") + +11. Click **Create VM Cluster** to proceed with provisioning. + + + + +## Task 2: Create an Oracle Database on Exadata Database Service on Exascale Infrastructure using OCI Console + +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 cloud VM cluster you want to create the database in:** + * In the left rail, **VM Clusters** is selected by default. + * Under **List Scope**, Select your assigned compartment named ***MyCompartmentXX***. + * Then **click on your clusters highlighted 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**. + + ![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 ***Pass4StudentXX*** as the **password** for the **sys** username. + + ![Define DBhome and Admin Password](./images/define-dbhome-and-admin-pwd.png " ") + +6. Now lets **configure Automatic Backups** for the database + * Select the checkbox for ** Enable Automatic Backups** + * For the **Backup Destination:** Select ***Autonomous Recovery Service*** + * For the **Protection Policy:** Select ***Silver*** + * For the **Deletion options after database termination:** Select ***Retain backups according to the protection policy retention period*** + * Next, **schedule the Day of the week and time for the initial backup to start:** Select ***Sunday between 4AM and 6AM***. + * Now wrap up the Automatic Backup configuration by **scheduling the time of day for the daily backups to start:** Select ***4AM to 6AM*** + + ![Configure Automatic Backups](./images/configure-automatic-backups-to-rcv.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 ***ExaXSDemoDB*** + ![Configure Adv Options - Mgmt Tab](./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](./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](./images/configure-adv-options-tags-tab.png " ") + +8. Click on the **Create Container Database** button to proceed with creating the Container Database. + +***!!! Congratulations:*** You may now **proceed to the next lab**. + + + +## Acknowledgements + +* **Author** - Eddie Ambler, Leo Alvarado, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Eddie Ambler, Product Management, July 2024. diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png new file mode 100644 index 0000000..d8b3b6d Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png new file mode 100644 index 0000000..daebcfd Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png new file mode 100644 index 0000000..ad6d7ba Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png new file mode 100644 index 0000000..e550635 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png new file mode 100644 index 0000000..2d2b9fd Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png new file mode 100644 index 0000000..5ecd302 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png new file mode 100644 index 0000000..bb230e1 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png new file mode 100644 index 0000000..252a499 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png new file mode 100644 index 0000000..bf9f9ba Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png new file mode 100644 index 0000000..15dadb5 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png new file mode 100644 index 0000000..476211c Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png new file mode 100644 index 0000000..2d597e9 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png new file mode 100644 index 0000000..bf82e12 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png new file mode 100644 index 0000000..c01379d Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png new file mode 100644 index 0000000..959b09e Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png new file mode 100644 index 0000000..6e4da5d Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png new file mode 100644 index 0000000..3343d28 Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png differ diff --git a/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png new file mode 100644 index 0000000..6e23dbb Binary files /dev/null and b/exadata-database-service-xs/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md b/exadata-database-service-xs/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md new file mode 100644 index 0000000..34c5df7 --- /dev/null +++ b/exadata-database-service-xs/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md @@ -0,0 +1,223 @@ +# 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** + +## Task 1: List the available Database Homes in a compartment using REST API + +1. Open the Cloud Shell. This displays the Cloud Shell at the bottom of the console: + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + + +2. Make an OCI REST API call to get a list of 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 ***Lab6***. + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10" + + + ``` +3. You will see a similar output as below. Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all available DB Homes in the specified compartment. + + ![list available dbhomes](./images/list-dbhome.png " ") + + Look for the Database Home with the **displayName** named ***MyCustomDBHome***. + + Observe the following objects and values from the API response such as: + + * ***databaseSoftwareImageId*** - If this field is populated then this is the **Custom Database Software Image** used for the Database Home + * ***dbVersion*** - The **Database Version** of the Database Home + + +## Task 2: List all the Container Databases in a Compartment + +1. From the Cloud Shell terminal, run the **OCI CLI command** below to get a list of the Container Databases in a Compartment. + + > **Note:** Replace the ***"{CompartmentID}"*** with the **Compartment OCID** used in ***Task 1*** + + ``` + + + oci db database list --compartment-id {CompartmentID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table + + + ``` + +2. You will see a similar output as below. Copy the **Container Database OCID** value and paste it in your notepad or text editor. + + ![list pluggable database](./images/list-all-cdb-in-compartment.png " ") + +## Task 3: List all the Pluggable Databases in a Container Database using REST API + +1. From the Cloud Shell terminal, make an OCI REST API call to get a list of the Pluggable Databases in a Container Database by running the **OCI RAW-REQUEST** command below: + + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{ContainerDatabaseOCID}"*** with the **Container Database OCID** obtained from ***Task 2*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" + + + ``` + +2. You will see a similar output as below. 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 specified container database. + +3. Copy the **PDB OCID** value from the **"id"** field and paste it in your notepad or text editor. + + ![list pluggable database](./images/getpdb.png " ") + + +## Task 4: Clone and start a pluggable database (PDB) in the same database (CDB) using REST API + +1. From the Cloud Shell terminal, create the JSON file for the REST API request body that contains the local clone pluggable database details resource. + + For this lab, the JSON file is pre-created; you can view the local clone pluggable database details by reading the JSON file. + + ``` + + + cat MyClonePDB.json + + + ``` + + +2. Make an OCI REST API call to clone and start a pluggable database (PDB) in the same container database (CDB) by running the **OCI RAW-REQUEST** command below: + + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{pluggableDatabaseID}"*** with the **Pluggable Database OCID** copied from ***Task3 Step 3*** + + ``` + + + oci raw-request --http-method POST --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/pluggableDatabases/{pluggableDatabaseID}/actions/localClone" --request-body file://MyClonePDB.json + + + + ``` + + + +3. You will see a similar output as below; you will see that the local clone pluggable database is on a lifecycle state of ***PROVISIONING*** + + ![local clone pluggable database](./images/clonepdb.png " ") + + +## Task 5: Discover Exadata VM Cluster Details using REST API + +1. Open the Cloud Shell. This displays the Cloud Shell at the bottom of the console. + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + +2. Make an OCI REST API call to get Exadata VM Cluster details by running the **OCI RAW-REQUEST** command below. + + > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***Lab 6 (Task 1 step 2)*** + + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}" + + + ``` + + + You will see a similar output below; pay attention to the **cpusEnabled** field. + + ``` + + { + "data": { + "availabilityDomain": "cuGa:US-SANJOSE-1-AD-1", + "compartmentId": "ocid1.compartment.oc1.....", + "cpusEnabled": 4, + "dataCollectionOptions": { + "isDiagnosticsEventsEnabled": true, + "isHealthMonitoringEnabled": true, + "isIncidentLogsEnabled": true + }, + + "status": "200 OK" +} + + ``` + + +## Task 6: List the Maintenance Updates that can be applied to the specified VM Cluster using REST API + +1. Make OCI REST API call to list maintenance updates that can be applied to the specified VM Cluster by running the **OCI RAW-REQUEST** Command below. + + > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***(Lab 6 Task 1 step 2)*** + + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}/updates" + + + ``` + + + ![list VM Cluster updates](./images/get-vmcluster-updates.png " ") + + You will see a similar output as below. Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the maintenance updates that can be applied to the specified VM Cluster using REST API + + ``` + + + { + "data": [ + { + "availableActions": [ + "ROLLING_APPLY", + "PRECHECK" + ], + "description": "Virtual Machine OS Update 22.1.11.0.0.230516", + "id": "ocid1.dbupdate.oc1.us-sanjose-1....", + "lastAction":, + "lifecycleDetails":, + "lifecycleState": "AVAILABLE", + "timeReleased": "2023-06-06T19:15:24.842Z", + "updateType": "OS_UPDATE", + "version": "22.1.11.0.0.230516" + } + ], + "headers": { + + }, + "status": "200 OK" +} + + ``` + + +You may now **proceed to the next lab**. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/clonepdb.png b/exadata-database-service-xs/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-xs/discover-env-details-on-exascale-api/images/clonepdb.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/cloudshell.png b/exadata-database-service-xs/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-xs/discover-env-details-on-exascale-api/images/cloudshell.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/cloudshelllaunch.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/cloudshelllaunch.png new file mode 100644 index 0000000..ee78be0 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png b/exadata-database-service-xs/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-xs/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/getpdb.png b/exadata-database-service-xs/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-xs/discover-env-details-on-exascale-api/images/getpdb.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png b/exadata-database-service-xs/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-xs/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhome.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhome.png new file mode 100644 index 0000000..8528e80 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhome.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale/discover-env-details-on-exascale.md b/exadata-database-service-xs/discover-env-details-on-exascale/discover-env-details-on-exascale.md new file mode 100644 index 0000000..04741dd --- /dev/null +++ b/exadata-database-service-xs/discover-env-details-on-exascale/discover-env-details-on-exascale.md @@ -0,0 +1,164 @@ +# Discover 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 + +Watch the video below for a quick walk-through of the lab. + [Discover Environment Details using OCI Console](youtube:) + +### 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 named ***MyCompartmentXX***. + * 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" ") + +3. 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. + * You can click the **Database Homes** link to see a list of the existing database homes. + * You can click the **Virtual Machines** link to see a list of the Virtual Machines that are allocated to your VM Cluster + + ![Review Resources Section on VM Cluster Details page](./images/vm-cluster-details-page-resource-section.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*** + + * 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. + * You can click the **Data Guard Association** link to see if this database has a Data Guard Peer. + * You can click the **Pluggable Database** link to see a list of the Pluggable Databases that have been created in this Container Database. + + ![Review Resources Section on VM Cluster Details page](./images/container-database-details-page-resource-section.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 to the **VM Clusters** page, where we will find a list of existing VM Clustsers and their associated **Exascale Storage Vaults**. + * On the **Pluggable Database Details** page, you will see the navigation bread crumb links. ***Click on the VM Clusters*** link. + + ![VM Clusters page - via breadcrumb link](./images/vmc-page-via-breadcumb-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. + +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 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** - Eddie Ambler, Leo Alvarado, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Eddie Ambler, Product Management, July 2024. diff --git a/exadata-database-service-xs/enable-automatic-backups/enable-automatic-backups.md b/exadata-database-service-xs/enable-automatic-backups/enable-automatic-backups.md new file mode 100644 index 0000000..0992b36 --- /dev/null +++ b/exadata-database-service-xs/enable-automatic-backups/enable-automatic-backups.md @@ -0,0 +1,70 @@ + + + +# Review Enable Automatic Backups + + +## Introduction + +This lab walks you through the steps to Enable Automatic Backups. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Enable Automatic Backups + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + +## Task 1: Enable Automatic Backups + +*(For this lab, Informational Instructions for Enabling Automatic Backups for the Exadata Database Service on Cloud@Customer environment will be presented by the speakers)* + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. + +3. In the Resources list of the VM Cluster Details page, click Databases. + +4. Click the name of the database for which you want to edit backup settings. + +5. Click Edit Backup Settings. + + Your current backup configuration determines the changes that you can make in the Backup Settings dialog, as follows: + + If automatic backups are not configured (Backup Destination Type is set to None), then you can use the following settings to define the backup configuration for the database: + + **Backup Destination Type**: From the list, choose an option. + + * **None** Select if you do not define a backup configuration for the database. + * **Local** Select to store backups locally in the Exadata Storage Servers on your Exadata Database Service on Cloud@Customer system. + * **Object Storage** Select to store backups in an object storage container managed by Oracle on Oracle Cloud Infrastructure. + * **NFS** Select to store backups in one of your previously defined backup destinations that uses Network File System (NFS) storage. + * **Recovery Appliance** Select to store backups in one of your previously defined backup destinations that uses Oracle Zero Data Loss Recovery Appliance. + + **Enable automatic backups**: Select this option to enable daily backups using the policy for automatic backups. + + **Backup retention period**: Select this option to choose one of the options for the length of time that automatic backups are retained. +6. Click **Save Changes**. + + +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-manage-db-backup-and-recovery.html#GUID-07D1B1D6-4A06-4859-B7DF-4C3A681A6B40) to learn more about Managing Database Backup and Recovery on Oracle Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/enable-dataguard/enable-dataguard.md b/exadata-database-service-xs/enable-dataguard/enable-dataguard.md new file mode 100644 index 0000000..2cb5bf6 --- /dev/null +++ b/exadata-database-service-xs/enable-dataguard/enable-dataguard.md @@ -0,0 +1,103 @@ + + + +# Enable Data Guard for local HA using OCI Console + + +## Introduction + +This lab walks you through the steps to Enable Data Guard using OCI Console. + +Estimated Lab Time: 15 minutes + + +### Objectives + +- After completing this lab, you should be able to Enable Data Guard using OCI Console + +### Prerequisites + +This lab requires completion of the following: + +* Completion of **Lab1** + + +## 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 " ") + +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 " ") + +4. In the Container Database details page, under **Resources**, click **Data Guard Associations**. + + ![Click on Dataguard Associations](./images/navigate-dg-association.png " ") + +5. Click **Enable Data Guard**. + + ![Click Enable Data Guard](./images/enable-dataguard.png " ") + + In the Enable Data Guard page, configure your Data Guard association. + + **Select Peer VM Cluster**: + + * **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 + + ![Select Peer VM Cluster](./images/select-peer-vmcluster.png " ") + + **Data Guard Assocation Details:** + + * **Select the Data Guard type**: Select 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*** + + ![Select Data Guard Association](./images/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 " ") + + **Configure standby database**: Provide the unique name for the standby database. + + * Provide the **Database password**. For this lab, use the assigned password ***Pass4Stud3nt-#*** + +6. Click **Enable Data Guard**. + + ![Click Enable Data Guard](./images/click-enable-dataguard.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***. + + + + +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. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/enable-dataguard/images/choose-database-home.png b/exadata-database-service-xs/enable-dataguard/images/choose-database-home.png new file mode 100644 index 0000000..b5ea5bd Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/choose-database-home.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/click-enable-dataguard.png b/exadata-database-service-xs/enable-dataguard/images/click-enable-dataguard.png new file mode 100644 index 0000000..96595e0 Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/click-enable-dataguard.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/dg-association-details.png b/exadata-database-service-xs/enable-dataguard/images/dg-association-details.png new file mode 100644 index 0000000..9ae04c8 Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/dg-association-details.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/enable-dataguard.png b/exadata-database-service-xs/enable-dataguard/images/enable-dataguard.png new file mode 100644 index 0000000..35064b2 Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/enable-dataguard.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/navigate-dg-association.png b/exadata-database-service-xs/enable-dataguard/images/navigate-dg-association.png new file mode 100644 index 0000000..d2f569b Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/navigate-dg-association.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/navigate-exadbcc-vmcluster.png b/exadata-database-service-xs/enable-dataguard/images/navigate-exadbcc-vmcluster.png new file mode 100644 index 0000000..fdc1056 Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/navigate-exadbcc-vmcluster.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/select-cdb.png b/exadata-database-service-xs/enable-dataguard/images/select-cdb.png new file mode 100644 index 0000000..be412cb Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/select-cdb.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/select-compartment.png b/exadata-database-service-xs/enable-dataguard/images/select-compartment.png new file mode 100644 index 0000000..dea4e7f Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/select-compartment.png differ diff --git a/exadata-database-service-xs/enable-dataguard/images/select-peer-vmcluster.png b/exadata-database-service-xs/enable-dataguard/images/select-peer-vmcluster.png new file mode 100644 index 0000000..a6c0ee2 Binary files /dev/null and b/exadata-database-service-xs/enable-dataguard/images/select-peer-vmcluster.png differ diff --git a/exadata-database-service-xs/get-started/get-started.md b/exadata-database-service-xs/get-started/get-started.md new file mode 100644 index 0000000..9ac34e9 --- /dev/null +++ b/exadata-database-service-xs/get-started/get-started.md @@ -0,0 +1,66 @@ +# 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), and Infrastructure as a Service (IaaS). + +Estimated Time: 5 minutes + +**Types of Cloud Accounts that can be used for this workshop:** + +**Oracle Cloud Paid Accounts**: 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. + +**Global Oracle Solutions Center (OSC) provided 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 access to an OSC provided environment. + + + + +### Objectives + +- For this workshop we will learn how to login to a tenancy provided by the **Global Oracle Solutions Center**. + + +### Prerequisites + +* **Cloud Account Name** - The name of your assigned OSC's Oracle Cloud tenancy + +* **Username** - Your assigned username for this workshop + +* **Password** - Your assigned password for this workshop + + +## Task 1: Log in to Oracle Cloud Tenancy provided by Global Oracle Solutions Center + +1. Go to [**cloud.oracle.com**](https://cloud.oracle.com/?region=us-sanjose-1&tenant=oscnas001) and enter your **Cloud Account Name** *(**Assigned Tenancy**)*. + + For this workshop, make sure your assigned tenancy named ***oscnas001*** is selected. + + + ![osc login](./images/osc-login.png " ") + + +2. Go to **Oracle Cloud Infrastructure Direct Sign-in** at the bottom of the page and enter your assigned **username** and **password** and click **Sign In** + + ![osc oci direct sign-in](./images/osc-direct-login.png " ") + +3. You are now signed in to Oracle Cloud! + + ![oci login](./images/oci-login-page.png " ") + +## Task 2: Review Exadata Database Service, Exadata Cloud Infrastructure, Custom Database & Application Images, and Oracle Database Cloud MAA + + *(For this lab, The Exadata Database Service on Cloud@Customer Resource Model is pre-provisioned - Informational Instructions for navigating the Exadata Database Service on Cloud@Customer environment will be presented by the speakers)* + +You may now **proceed to the next lab**. + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/get-started/images/oci-login-page.png b/exadata-database-service-xs/get-started/images/oci-login-page.png new file mode 100644 index 0000000..52160a8 Binary files /dev/null and b/exadata-database-service-xs/get-started/images/oci-login-page.png differ diff --git a/exadata-database-service-xs/get-started/images/osc-direct-login.png b/exadata-database-service-xs/get-started/images/osc-direct-login.png new file mode 100644 index 0000000..49c228b Binary files /dev/null and b/exadata-database-service-xs/get-started/images/osc-direct-login.png differ diff --git a/exadata-database-service-xs/get-started/images/osc-login.png b/exadata-database-service-xs/get-started/images/osc-login.png new file mode 100644 index 0000000..1f5f1dc Binary files /dev/null and b/exadata-database-service-xs/get-started/images/osc-login.png differ diff --git a/exadata-database-service-xs/introduction/introduction.md b/exadata-database-service-xs/introduction/introduction.md new file mode 100644 index 0000000..637cce1 --- /dev/null +++ b/exadata-database-service-xs/introduction/introduction.md @@ -0,0 +1,48 @@ +# Introduction + +## About this Workshop + +In this hands-on class, you’ll deploy and configure Oracle databases using the Exadata Database Service in our lab environment, leveraging the user interface web console and Terraform. + +In one of the most real-world classes you’ll ever attend, you’ll learn the latest techniques designed to simplify operational tasks and automate standards-based deployments of the database for your applications. You will use cloud automation functions to create database environments leveraging VM Cluster Node Subsetting consolidation feature. . You’ll learn how the Exadata platform embraces cloud economics to control costs with the ability to scale CPUs up and down and to scale out compute and storage nodes. + +To meet your desired SLA levels, you’ll 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. + +Don’t miss your chance to learn how to use cloud automation functions to standardize your database cloud environments, all while realizing the performance and scale of the Oracle Database on the Exadata Cloud Platform that is available to all types of workloads. + +Estimated Workshop Time: 160 minutes + +**What is an Oracle Exadata Database Service?** + +Oracle Exadata Database Service is a high-performance co-managed Oracle Cloud Database service that allows organizations to run databases with extreme performance, availability, and security cost-effectively. Databases run faster and with fewer resources on scale-out Exadata infrastructure that includes unique optimizations for transaction processing, analytics, and mixed workloads. Online scaling of computing resources enables customers to quickly adjust consumption to match workload demands without interrupting operations, while efficient database consolidation further lowers total costs. Full compatibility with on-premises Oracle Database and Exadata environments makes it easy for customers to migrate workloads to the cloud. + +Exadata Database Service allows you to leverage the power of Exadata in the cloud. +Exadata Database Service’s scale-out architecture allows customers to provision more compute and storage independently, to be able to +easily right-size their service to meet their growing workload demand. +Exadata Database Service offer RDMA over Converged Ethernet (RoCE) networking for high bandwidth and low latency, Exadata RDMA Memory (XRMEM) Cache, and intelligent Exadata software. + +Exadata Database Service reduces downtime and simplifies operational management with zero downtime maintenance, online scaling, and one-click provisioning of Oracle Real Application Clusters (Oracle RAC) and Oracle Active Data Guard using built-in cloud automation. Exadata Database Service has built-in Oracle Maximum Availability Architecture (Oracle MAA) best practices that help it to increase database availability out of the box. + + + +**What is an Oracle Exadata Database Service on Cloud@Customer?** + +Oracle Exadata Database Service on Cloud@Customer enables you to apply the combined power of Oracle Exadata and Oracle Cloud Infrastructure inside your own data center. You have full access to the features and capabilities of Oracle Database along with the intelligent performance and scalability of Oracle Exadata, but with Oracle owning and managing the Exadata infrastructure. You can use the Oracle Cloud Infrastructure console and APIs to manage Oracle Exadata Database Service on Cloud@Customer just as with any other cloud resource, while maintaining absolute sovereignty over your data. + +Oracle Exadata Database Service on Cloud@Customer is the simplest way to move an organization’s business-critical Oracle Database workloads to the cloud. It simultaneously runs Oracle Exadata Database Service and the fully managed Oracle Autonomous Database Service inside customers’ data centers and behind their firewalls to help meet strict data residency and security requirements. + +Oracle Exadata Database Service on Cloud@Customer provides the same user experience as Exadata Database Service on Dedicated Infrastructure with Oracle-owning and managing the infrastructure that is located in your data center. + +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-whats-new-in-exadata-cloud-at-customer-gen2.html#GUID-2F27E5A9-67A8-459E-9453-81E1F68043DE) to learn about What's New in Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png new file mode 100644 index 0000000..c420124 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png new file mode 100644 index 0000000..ee78be0 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png b/exadata-database-service-xs/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-xs/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png new file mode 100644 index 0000000..ad2d999 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png b/exadata-database-service-xs/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-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png b/exadata-database-service-xs/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-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png b/exadata-database-service-xs/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-xs/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md new file mode 100644 index 0000000..e0266df --- /dev/null +++ b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md @@ -0,0 +1,94 @@ + + + +# Scale Exadata VM Cluster Resources using OCI CLI + + +## Introduction + +The OCI CLI is a small footprint tool that you can use on its own or with the Console to perform Database Cloud Services resource tasks and other OCI tasks. The CLI provides the same core functionality as the Console, plus additional commands. Some of these, such as the ability to run scripts, extend the Console's functionality. + +**Cloud Shell**: The CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell. + +**Oracle Linux Cloud Developer image**: The CLI is pre-installed on the Oracle Linux Cloud Developer platform image. For more information. + +The CLI is built on the Oracle Cloud Infrastructure SDK for Python and runs on Mac, Windows, or Linux. The Python code makes calls to Oracle Cloud Infrastructure APIs to provide the functionality implemented for the various services. These are REST APIs that use HTTPS requests and responses. + +This lab walks you through the steps to Scale the Exadata VM Cluster OCPU resource using OCI CLI. + +Estimated Time: 10 minutes + + +### Objectives + +- After completing this lab, you should be able to scale Exadata VM Cluster OCPU resource using OCI CLI + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + + +## Task 1: Scale Exadata VM Cluster OCPU using OCI CLI + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + + ![navigage oci console](./images/navigateocimenu.png " ") + +2. In the left rail, **Exadata VM Clusters** is selected by default. Select your assigned Compartment ***MyCompartmentXX***. + + Click on the name of your assigned VM Cluster ***MyVMClusterXX***. The VM Cluster Details page displays information about the selected VM cluster. + + Under the **General Information**, In the OCID Field. Click on **Show** to display the VM Cluster OCID, and Click on **Copy** and paste the **VM Cluster OCID** to your notepad or text editor. + + Under the **Resource allocation**, pay attention to the number of ***OCPUs:*** which has the value of ***6*** + + ![vm cluster details page](./images/vmcluster-details-page.png " ") + +3. To use OCI CLI for this lab, we will be using the ***Cloud OCI Shell tool***, where CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell in the OCI Web Console. + + Click the Cloud Shell/Code Editor icon in the Console header and select Cloud Shell from the drop-down menu. + + ![oci cloudshell](./images/cloudshell.png " ") + + This displays the Cloud Shell in a "drawer" at the bottom of the console: + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + +4. Run the OCI CLI Command to Scale down the **VM Cluster OCPU Resources** from **6 OCPUs** to **4 OCPUs** + + >**Note:** Replace ***{vmClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 2)* + + ``` + + + oci db vm-cluster update --vm-cluster-id {vmClusterId} --cpu-core-count 4 --query 'data.{VMClusterOCID:id, DisplayName:"display-name", LifecycleState:"lifecycle-state", CompartmentOCID:"compartment-id"}' + + + ``` + + ![scale number of ocpus](./images/scale-ocpu.png " ") + + After running the command, you will see similar output below. + + ![LifecycleState of updating is displayed for scale number of ocpus](./images/scale-vm-cluster-updating.png " ") + + While the scale up process is running, you can see the LifecycleState of the VM cluster is changed to ***Updating***. Copy the ***Compartment OCID*** from the extracted values of the OCI CLI command results and paste it in your notepad or text editor for later use. + +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-manage-vm-clusters.html#GUID-B9529795-C3D0-423A-B83F-BDD96AB29E32) to learn more about Scaling Up or Scaling Down the VM Cluster Resources for Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshell.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshell.png new file mode 100644 index 0000000..c420124 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshell.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshelllaunch.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshelllaunch.png new file mode 100644 index 0000000..ee78be0 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/copy-compartment-ocid.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/copy-compartment-ocid.png new file mode 100644 index 0000000..dfefc84 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/copy-compartment-ocid.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/navigateocimenu.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/navigateocimenu.png new file mode 100644 index 0000000..ad2d999 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/navigateocimenu.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-ocpu.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-ocpu.png new file mode 100644 index 0000000..4e3b20a Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-ocpu.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png new file mode 100644 index 0000000..f305533 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/scale-vm-cluster-updating.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/images/vmcluster-details-page.png b/exadata-database-service-xs/scale-resources-using-oci-cli/images/vmcluster-details-page.png new file mode 100644 index 0000000..c4bc910 Binary files /dev/null and b/exadata-database-service-xs/scale-resources-using-oci-cli/images/vmcluster-details-page.png differ diff --git a/exadata-database-service-xs/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md b/exadata-database-service-xs/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md new file mode 100644 index 0000000..e0266df --- /dev/null +++ b/exadata-database-service-xs/scale-resources-using-oci-cli/scale-resources-using-oci-cli.md @@ -0,0 +1,94 @@ + + + +# Scale Exadata VM Cluster Resources using OCI CLI + + +## Introduction + +The OCI CLI is a small footprint tool that you can use on its own or with the Console to perform Database Cloud Services resource tasks and other OCI tasks. The CLI provides the same core functionality as the Console, plus additional commands. Some of these, such as the ability to run scripts, extend the Console's functionality. + +**Cloud Shell**: The CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell. + +**Oracle Linux Cloud Developer image**: The CLI is pre-installed on the Oracle Linux Cloud Developer platform image. For more information. + +The CLI is built on the Oracle Cloud Infrastructure SDK for Python and runs on Mac, Windows, or Linux. The Python code makes calls to Oracle Cloud Infrastructure APIs to provide the functionality implemented for the various services. These are REST APIs that use HTTPS requests and responses. + +This lab walks you through the steps to Scale the Exadata VM Cluster OCPU resource using OCI CLI. + +Estimated Time: 10 minutes + + +### Objectives + +- After completing this lab, you should be able to scale Exadata VM Cluster OCPU resource using OCI CLI + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab1** + + +## Task 1: Scale Exadata VM Cluster OCPU using OCI CLI + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. + + ![navigage oci console](./images/navigateocimenu.png " ") + +2. In the left rail, **Exadata VM Clusters** is selected by default. Select your assigned Compartment ***MyCompartmentXX***. + + Click on the name of your assigned VM Cluster ***MyVMClusterXX***. The VM Cluster Details page displays information about the selected VM cluster. + + Under the **General Information**, In the OCID Field. Click on **Show** to display the VM Cluster OCID, and Click on **Copy** and paste the **VM Cluster OCID** to your notepad or text editor. + + Under the **Resource allocation**, pay attention to the number of ***OCPUs:*** which has the value of ***6*** + + ![vm cluster details page](./images/vmcluster-details-page.png " ") + +3. To use OCI CLI for this lab, we will be using the ***Cloud OCI Shell tool***, where CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell in the OCI Web Console. + + Click the Cloud Shell/Code Editor icon in the Console header and select Cloud Shell from the drop-down menu. + + ![oci cloudshell](./images/cloudshell.png " ") + + This displays the Cloud Shell in a "drawer" at the bottom of the console: + + ![oci cloudshell](./images/cloudshelllaunch.png " ") + +4. Run the OCI CLI Command to Scale down the **VM Cluster OCPU Resources** from **6 OCPUs** to **4 OCPUs** + + >**Note:** Replace ***{vmClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 2)* + + ``` + + + oci db vm-cluster update --vm-cluster-id {vmClusterId} --cpu-core-count 4 --query 'data.{VMClusterOCID:id, DisplayName:"display-name", LifecycleState:"lifecycle-state", CompartmentOCID:"compartment-id"}' + + + ``` + + ![scale number of ocpus](./images/scale-ocpu.png " ") + + After running the command, you will see similar output below. + + ![LifecycleState of updating is displayed for scale number of ocpus](./images/scale-vm-cluster-updating.png " ") + + While the scale up process is running, you can see the LifecycleState of the VM cluster is changed to ***Updating***. Copy the ***Compartment OCID*** from the extracted values of the OCI CLI command results and paste it in your notepad or text editor for later use. + +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-manage-vm-clusters.html#GUID-B9529795-C3D0-423A-B83F-BDD96AB29E32) to learn more about Scaling Up or Scaling Down the VM Cluster Resources for Exadata Database Service on Cloud@Customer. + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/oci-menu-orm.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/oci-menu-orm.png new file mode 100644 index 0000000..8481b5d Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/oci-menu-orm.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-stack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-stack.png new file mode 100644 index 0000000..b9a8eec Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-stack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png new file mode 100644 index 0000000..422b6e9 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-apply-succeeded.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-click-plan.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-click-plan.png new file mode 100644 index 0000000..e788b2c Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-click-plan.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png new file mode 100644 index 0000000..04b03e1 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-name-stack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png new file mode 100644 index 0000000..991de1d Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png new file mode 100644 index 0000000..cfcf1c9 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack.png new file mode 100644 index 0000000..39b0c44 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png new file mode 100644 index 0000000..aa74815 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png new file mode 100644 index 0000000..df2643b Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack-from-zip.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png new file mode 100644 index 0000000..120d1f0 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-dbstack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png new file mode 100644 index 0000000..4fca335 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png new file mode 100644 index 0000000..be22129 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-cdb.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png new file mode 100644 index 0000000..73c1292 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png new file mode 100644 index 0000000..7701c6b Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png new file mode 100644 index 0000000..540f898 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png new file mode 100644 index 0000000..404e212 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-myappdbstack-available.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-job.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-job.png new file mode 100644 index 0000000..ac0cc19 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-job.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png new file mode 100644 index 0000000..e7032e3 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-stackdetails.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-success.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-success.png new file mode 100644 index 0000000..958768d Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-plan-success.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png new file mode 100644 index 0000000..bb9e736 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-stackdetails-apply.png differ diff --git a/exadata-database-service-xs/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md b/exadata-database-service-xs/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md new file mode 100644 index 0000000..53a2d2c --- /dev/null +++ b/exadata-database-service-xs/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md @@ -0,0 +1,327 @@ +# Use OCI Resource Manager to generate and deploy Terraform for Application and Database Stack + + +## Introduction + +This lab walks you through the steps to generate and deploy Terraform for Application and Database stack using OCI Resource Manage. + +Estimated Time: 20 minutes + + +### Objectives + +- After completing this lab, you should be able to generate and deploy Terraform for Application and Database stack using OCI Resource Manager. + + +### Prerequisites + +This lab requires the completion of the following: + +* Completion of **Lab7** + +## Task 1: Generate Terraform baseline configuration for Database development environment using OCI Resource Manager + +1. Open the navigation menu and click **Developer Services**. Under **Resource Manager**, click **Stacks**. + + ![Launch ORM Stacks](./images/oci-menu-orm.png " ") + +2. On the **Stacks** page, select your assigned compartment. + +3. Click **Create stack**. + +4. On the **Create stack** page, under **Choose the origin of the Terraform configuration**, select **Existing compartment**. + +5. Select your assigned **compartment** and assigned **region** containing the Exadata Database Service on Cloud@Customer Resource Model. + + ![select compartment for resource discovery](./images/orm-create-stack-from-compartment.png " ") + + This will create a stack that captures resources from the selected assigned compartment using **OCI Resource Manager (resource discovery)** + +6. Select the service types that you want to be discovered for your terraform script by: Selecting **Selected** for the Terraform provider services and then selecting **database** for the services value. + + ![Select compartment to create stack](./images/orm-discover-dbstack.png " ") + +7. Provide the **Name** for your stack and Select the **compartment** where you want to create the stack. + + >**Note:** For this lab, use **MyTFBaseline-Database** for the name of your discovered database stack and use your assigned compartment for the **Create in compartment** + + ![Create your discovered database stack](./images/orm-create-stack.png " ") + + + +8. Click **Next** twice. No variables are listed for the Existing compartment stack origin because no Terraform configuration exists yet. + +9. In the Review panel, verify the stack configuration. Take note of the Terraform version for future use on your stack deployment. + + ![Create database stack](./images/orm-create-stack-database.png " ") + +10. Click **Create**. + + + +11. Once the newly created stack is available, Download a copy of the generated Terraform script by clicking on the **Download** link next to **Terraform configuration**. + + ![Download database stack](./images/orm-download-dbstack.png " ") + + After downloading the zip file, you can unzip the file and view the generated Terraform configuration file in your text or code editor. + + View the *database.tf* file. + + >**Note:** Your database's generated baseline terraform code is similar to the output below. *Resources discovered in the Baseline Terraform configuration will be presented and discussed by the speakers*. Notes are added on each section of the discovered Exadata Database Service Resource Model + + This is the discovered resource for the **Custom Database Software image** + + ``` + + + ## This configuration was generated by terraform-provider-oci + + + ## This is the discovered resource for the Custom Database Software image + + resource oci_database_database_software_image export_MyCustomDBSW { + compartment_id = var.compartment_ocid + database_software_image_one_off_patches = [ + "29780459", + "30310195", + ] + database_version = "19.0.0.0" + defined_tags = { + } + display_name = "MyCustomDBSW" + freeform_tags = { + } + image_shape_family = "EXACC_SHAPE" + image_type = "DATABASE_IMAGE" + patch_set = "19.11.0.0" + } + + + ``` + + This is the discovered resource for the **Exadata VM Cluster Resource** + + + ``` + + + + ## This is the discovered resource for the Exadata VM Cluster Resource + + resource oci_database_vm_cluster export_MyVMClusterXX { + compartment_id = var.compartment_ocid + cpu_core_count = "0" + data_collection_options { + is_diagnostics_events_enabled = "true" + is_health_monitoring_enabled = "true" + is_incident_logs_enabled = "true" + } + data_storage_size_in_tbs = "30" + db_node_storage_size_in_gbs = "120" + db_servers = [ + "ocid1.dbserver.oc1.us-sanjose-1.aaaaaaaaaaaaa", + "ocid1.dbserver.oc1.us-sanjose-1.aaaaaaaaaaaaa", + ] + defined_tags = { + } + display_name = "MyVMClusterXX" + exadata_infrastructure_id = "ocid1.exadatainfrastructure.oc1.us-sanjose-1.a" + freeform_tags = { + } + gi_version = "19.19.0.0.0" + is_local_backup_enabled = "false" + is_sparse_diskgroup_enabled = "true" + license_model = "BRING_YOUR_OWN_LICENSE" + memory_size_in_gbs = "60" + ssh_public_keys = [ + ] + time_zone = "UTC" + vm_cluster_network_id = "ocid1.vmclusternetwork.oc1.us-sanjose-1.aaaaaaaa" + } + + + ``` + + This is the discovered resource for the **Database Home** + + ``` + + + ## This is the discovered resource for the Database Home + + resource oci_database_db_home export_MyCustomDBHome { + db_version = "19.18.0.0.0" + defined_tags = { + } + display_name = "MyCustomDBHome" + freeform_tags = { + } + source = "NONE" + vm_cluster_id = oci_database_vm_cluster.export_MyVMClusterXX.id + } + + + ``` + This is the discovered resource for the **Container Database** + + ``` + + + + ## This is the discovered resource for the Container Database + + resource oci_database_database export_MyCustomDBHome_database { + database { + admin_password = "" + character_set = "AL32UTF8" + db_name = "MyCDB01" + db_unique_name = "cdb01" + db_workload = "OLTP" + defined_tags = { + } + freeform_tags = { + } + ncharacter_set = "AL16UTF16" + pdb_name = "mypdb1" + sid_prefix = "myexadbcc" + } + db_home_id = oci_database_db_home.export_MyCustomDBHome.id + source = "NONE" #Required attribute + lifecycle { + ignore_changes = [source, database[0].admin_password] + } + } + + + ``` + + This is the discovered resource for the **Pluggable Databases** + + ``` + + + + ## This is the discovered resource for the Pluggable Databases + + resource oci_database_pluggable_database export_pluggable_database { + container_database_id = oci_database_database.export_MyDBHome_database.id + defined_tags = { + } + freeform_tags = { + } + #pdb_admin_password = + pdb_name = "MYPDB" + } + + resource oci_database_pluggable_database export_pluggable_database_1 { + container_database_id = oci_database_database.export_MyDBHome_database.id + defined_tags = { + } + freeform_tags = { + } + #pdb_admin_password = + pdb_name = "MYCLONEPDB" + } + + + ``` + +## Task 2: Deploy Gold Image Stack (Database and MyDesktop Application) using OCI Resource Manager and Terraform + +1. In the Breadcrumb link, Click on **Stacks** then select your assigned **compartment** and Click **Create stack**. + + ![Deploy App and DB Stack](./images/orm-deploy-app-dbstack.png " ") + +2. On the **Create stack** page, under Choose the origin of the Terraform configuration, select **My configuration**. + + Select **.Zip file** for the Terraform configuration source. then browse your desktop for a file called ***SampleTF.zip***. + + + ![Upload zip file to deploy App and DB Stack](./images/orm-deploy-app-dbstack-from-zip.png " ") + + +3. Provide the **Name** for your stack and select the **compartment** where you want to create the stack. + + >**Note:** For this lab, use ***MyAppDBStack*** for the name of your discovered database stack and use your assigned compartment for the **Create in compartment** + +4. For Terraform version, select the *version 1.2.x*. + + ![Upload zip file to deploy App and DB Stack](./images/orm-create-name-stack.png " ") + +5. Click **Next**. In the **Configure variables panel**, review and provide the required variables listed from the Terraform configuration. + + Provide required variable details for the **Application Server Stack**. + + ![Deploy Application Stack](./images/orm-deploy-application-stack.png " ") + + * Choose your **Assigned compartment** + * Provide the **Application Server display name**. For this lab, use the name ***MyAppServer2*** + * Provide the **Custom Instance Image Source ID**. For DatabaseWorld, accept the default value + + Provide required variable details for the **Exadata Database Server Stack**. + + ![Deploy Database PDB Stack](./images/orm-deploy-exadata-database-pdb.png " ") + + * Provide the **Developer Container Database OCID**. For this lab, use the value for the ***MyCDB01*** obtained from ***Lab7 (Task 2 Step 2)*** + * Provide the **Pluggable Database display name**. For this lab, use the name ***MyPDB2*** + * Provide the **Pluggable Database administrator password** + + Click on **Next** + +6. In the **Review** panel, verify the stack configuration and Click **Create** to establish your customized stack. + + ![Review App and Database Stack](./images/orm-deploy-app-db-review.png " ") + + >**Note:** Now that we have a defined stack, let's prepare to use the stack to deploy a new developer environment consisting of an Application Server and 1 Exadata Container Database and 3 Pluggable Databases. + + ![App and Database Available Stack](./images/orm-myappdbstack-available.png " ") + +7. Create Stack Deployment Plan by: Clicking on **Plan** on the Stack details page. + + ![Create Stack Deployment Plan](./images/orm-plan-job.png " ") + + In the Plan panel, use ***MyAppDBStackPlan*** for the Plan name and then Click on **Plan** to proceed. + + ![Confirm Create Stack Deployment Plan](./images/orm-click-plan.png " ") + + >**Note:** The plan job is created and is listed under Jobs. + + When the Stack Deployment Plan process is completed, the state of the plan job changes to **Succeeded**. + + ![Stack Deployment Plan Succeeded](./images/orm-plan-success.png " ") + + +8. In the **Breadcrumb** link, Click on **Stack details**. + + ![View Stack Details Page ](./images/orm-plan-stackdetails.png " ") + + Process Stack Deployment Plan by clicking on **Apply**. + + ![Create Stack Deployment Apply ](./images/orm-stackdetails-apply.png " ") + + In the Apply panel, edit the default name for the job. For this lab, we will use ***MyAppDBStackApply*** for the Apply name. + + Select **Automatically Approve** for the Apply job plan resolution and then Click on **Apply**. + + ![Click Stack Deployment Apply ](./images/orm-apply-stack.png " ") + + >**Note:** This will cause the apply job to be created and our new Application and Database stack to be deployed once the job is completed. + + ![Stack Deployment Apply Succeeded ](./images/orm-apply-succeeded.png " ") + +You may now **proceed to the next lab** + + + +## Acknowledgements + +* **Author** - Leo Alvarado, Eddie Ambler, Product Management + +* **Contributors** - Tammy Bednar, Product Management + +* **Last Updated By** - Leo Alvarado, Product Management, September 2023. diff --git a/exadata-database-service-xs/workshops/ocw24-exascale-hol/index.html b/exadata-database-service-xs/workshops/ocw24-exascale-hol/index.html new file mode 100644 index 0000000..aaac634 --- /dev/null +++ b/exadata-database-service-xs/workshops/ocw24-exascale-hol/index.html @@ -0,0 +1,62 @@ + + + + + + + + + Oracle LiveLabs + + + + + + + + + + + + +
+
+
+
+
+
+
+
+ + + + + diff --git a/exadata-database-service-xs/workshops/ocw24-exascale-hol/manifest.json b/exadata-database-service-xs/workshops/ocw24-exascale-hol/manifest.json new file mode 100644 index 0000000..c6725fd --- /dev/null +++ b/exadata-database-service-xs/workshops/ocw24-exascale-hol/manifest.json @@ -0,0 +1,50 @@ +{ + "workshoptitle": "Hands-on: Oracle Exadata Database Service with Exascale", + + "help": "livelabs-help-db_us@oracle.com", + + "tutorials": [ + { + "title": "Introduction", + "description": "Introduction", + "filename": "../../introduction/introduction.md" + }, + { + "title": "Get Started", + "description": "Login to Oracle Cloud", + "filename": "https://oracle-livelabs.github.io/common/labs/cloud-login/cloud-login.md" + }, + { + "title": "Lab 1: Create Instance of Exadata Database Service on Exascale Infrastructure", + "description": "Learn how to Create Instance of Exadata Database Service on Exscale Infrastructure using OCI Console", + "filename": "../../create-VMCluster-CDB-PDB-on-Exascale/create-VMCluster-CDB-PDB-on-Exascale.md" + + }, + { + "title": "Lab 2: Discover VM Cluster, Container Database, & Pluggable Database Details", + "description": "Learn how to Discover Environment Details using OCI Console", + "filename": "../../discover-env-details-on-Exascale/discover-env-details-on-Exascale.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": "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" + } + ] +}