diff --git a/exadata-database-service-xs/.vscode/settings.json b/exadata-database-service-xs/.vscode/settings.json new file mode 100644 index 0000000..6f3a291 --- /dev/null +++ b/exadata-database-service-xs/.vscode/settings.json @@ -0,0 +1,3 @@ +{ + "liveServer.settings.port": 5501 +} \ No newline at end of file diff --git a/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md b/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md index fcc5b98..6a9d6ba 100644 --- a/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md +++ b/exadata-database-service-xs/change-license-type/change-license-type-using-oci-console.md @@ -1,22 +1,21 @@ -# Change License Type using OCI Console +# Change License Type using OCI CLI ## Introduction -This lab walks you through the steps to Change License Type using OCI Console. +This lab walks you through the steps to Change License Type using OCI CLI. -**Estimated Lab Time:** ***15 minutes*** +Estimated Lab Time: 15 minutes - ### Objectives -- After completing this lab, you should be able to Change License Type of the Exadata VM Cluster by using the OCI Console. +- After completing this lab, you should be able to Change License Type using OCI CLI ### Prerequisites @@ -24,49 +23,105 @@ This lab requires completion of the following: * Completion of **Lab1** -## Task 1: Change License Type of Exadata VM Cluster using OCI Console - -1. Navigate to the Exadata Database Service on Exascale Infrastructure using OCI Console - - * Open the **navigation menu** and click ***Oracle Database***. - * Under **Oracle Database**, click ***Oracle Database Service on Exascale Infrastructure***. - ![Navigate from OCI Console to ExaDB-XS Image](./images/console-to-exadb-xs.png " ") - * **Note:** This will cause the **VM Clusters** page to be displayed. - -2. Navigate to your Compartment and VM Cluster +## Task 1: Change License Type using OCI CLI - * On the left rail, ensure that **VM Clusters** is selected (default selection). - * For the **List Scope**, select your assigned compartment named ***MyCompartmentXX***. - * In the list of displayed VM clusters, click on the name of your **Assigned VM Cluster** named ***MyDemoVMClusterXX***. - ![Navigate to Compartment and VM Cluster Image](./images/select-compartment-and-mydemo-vm-cluster.png " ") - * **Note:** This will cause the **VM Cluster Details** page to be displayed. +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. -3. On the VM Cluster Details page, take note of the current **License Type** selection +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyVMClusterXX***. - ![Note current VM Cluster License Type Image](./images/vmc-current-license-type.png " ") + **To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***.** + +3. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section. + + ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") -4. On the VM Cluster Details page, Click **Update License Type** + Paste the VM Cluster OCID to a text editor. - ![Update License Type Image](./images/update-license-type-button.png " ") +4. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. + + ![navigate to oci cloudshell](./images/oci-cloud-shell.png "navigate to oci cloudshell") + + This displays the Cloud Shell in a "drawer" at the bottom of the console: -5. Change the license type from **Bring Your Own License (BYOL)** to ***License Included*** + ![oci cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") + +5. Run the OCI CLI Command to change the license type of the VM Cluster. - ![Update License Type Image](./images/change-license-included.png " ") + For this lab, we will change the license type from ***Bring Your Own License (BYOL)*** to ***License Included***. + + + >**Note:** Replace ***{VMClusterId}*** with the VM Cluster OCID copied from *(Task 1 Step 3)* + + ``` + + + oci db exadb-vm-cluster update --exadb-vm-cluster-id {VMClusterID} --license-model LICENSE_INCLUDED + + + ``` -6. Click **Save Changes** + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***exadb-vm-cluster*** ***update*** ***--exadb-vm-cluster-id*** ***{VMClusterID}*** ***--license-model*** ***LICENSE_INCLUDED*** -7. On the VM Cluster Details page, validate that the **License Type** selection has been changed to ***License Included*** + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exadb-vm-cluster*** is the **resource type** for the Exadata VM Cluster on Exascale Infrastructure. + * ***update*** is the **action** to update the Exadata VM Cluster on Exascale Infrastructure. + * ***--exadb-vm-cluster-id*** is the **parameter** for the VM Cluster OCID. + * ***--license-model LICENSE_INCLUDED*** is the **parameter** to change the license type of the VM Cluster to ***License Included***. + + After running the command, you will see similar output below. + + ![change license type](./images/change-license-type-updating.png "change license type") + + You will see that the VM Cluster status ***"lifecycle-state"*** is ***UPDATING***. + +1. Once the change license type operation has been completed, Run the OCI CLI Command to get information about the Exadata VM Cluster on Exascale Infrastructure and to view the new license type for the VM Cluster. + + >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 3)* + + ``` + + + oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterId} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state",LicenseModel:"license-model"}' + + + ``` + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***exadb-vm-cluster*** ***get*** ***--exadb-vm-cluster-id*** ***{VMClusterID}*** ***--query*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exadb-vm-cluster*** is the **resource type** for the Exadata VM Cluster on Exascale Infrastructure. + * ***get*** is the **action** to get information about the Exadata VM Cluster on Exascale Infrastructure. + * ***--exadb-vm-cluster-id*** is the **parameter** for the VM Cluster OCID. + * ***--query*** is the query parameter used for structured query options to display the specific VM Cluster data fields and values for ***Display Name***, ***Enabled ECPUs***, ***Lifecycle state***, and ***License model*** + - ![Note updated VM Cluster License Type Image](./images/vmc-updated-license-type.png " ") + After running the command, you will see similar output below. + + ![change license type completed](./images/change-license-type-completed.png "change license type completed") + + Pay attention to the following VM Cluster details from the command output: + * **Display Name:** ***"MyDemoVMClusterXX"*** + * **Enabled ECPUs:** ***16*** + * **License Model:** ***"LICENSE_INCLUDED"*** + * **Lifecycle State:** ***"AVAILABLE"*** + + +***Congratulations!!!*** You may now **proceed to the next lab**. -You may now **proceed to the next lab** ## Acknowledgements -* **Authors** - Eddie Ambler, Leo Alvarado, Product Management +* **Author** - Leo Alvarado, Eddie Ambler, Product Management * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Eddie Ambler, Product Management, August 2024. +* **Last Updated By** - Leo Alvarado, Product Management, August 2024. diff --git a/exadata-database-service-xs/change-license-type/images/change-license-type-completed.png b/exadata-database-service-xs/change-license-type/images/change-license-type-completed.png new file mode 100644 index 0000000..11ebf9e Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/change-license-type-completed.png differ diff --git a/exadata-database-service-xs/change-license-type/images/change-license-type-updating.png b/exadata-database-service-xs/change-license-type/images/change-license-type-updating.png new file mode 100644 index 0000000..437017b Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/change-license-type-updating.png differ diff --git a/exadata-database-service-xs/change-license-type/images/cloudshelllaunch.png b/exadata-database-service-xs/change-license-type/images/cloudshelllaunch.png new file mode 100644 index 0000000..94d968e Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png b/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png deleted file mode 100644 index 476211c..0000000 Binary files a/exadata-database-service-xs/change-license-type/images/console-to-exadb-xs.png and /dev/null differ diff --git a/exadata-database-service-xs/change-license-type/images/copy-vmcluster-ocid.png b/exadata-database-service-xs/change-license-type/images/copy-vmcluster-ocid.png new file mode 100644 index 0000000..81674f1 Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/copy-vmcluster-ocid.png differ diff --git a/exadata-database-service-xs/change-license-type/images/oci-cloud-shell.png b/exadata-database-service-xs/change-license-type/images/oci-cloud-shell.png new file mode 100644 index 0000000..7154802 Binary files /dev/null and b/exadata-database-service-xs/change-license-type/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png b/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png deleted file mode 100644 index 59c2cc4..0000000 Binary files a/exadata-database-service-xs/change-license-type/images/select-compartment-and-mydemo-vm-cluster.png and /dev/null differ diff --git a/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png b/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png deleted file mode 100644 index 546fbaa..0000000 Binary files a/exadata-database-service-xs/change-license-type/images/vmc-current-license-type.png and /dev/null 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 index 34c5df7..14cb991 100644 --- 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 @@ -18,201 +18,274 @@ 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 +## Task 1: Get the VM Cluster Details using OCI CLI -1. Open the Cloud Shell. This displays the Cloud Shell at the bottom of the console: +**To use OCI CLI for this lab, we will be using the** ***OCI Cloud Shell tool***. + - ![oci cloudshell](./images/cloudshelllaunch.png " ") +1. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. + + ![navigate to oci cloudshell](./images/oci-cloud-shell.png "navigate to oci cloudshell") + This displays the Cloud Shell in a "drawer" at the bottom of the console: -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 cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") - 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 " ") +**For this lab, we will be using the** ***OCI Code Editor*** **to store the required details in this lab.** - Look for the Database Home with the **displayName** named ***MyCustomDBHome***. +2. Click on the ***Expand*** icon in **Actions** and select ***Open Code Editor***. - Observe the following objects and values from the API response such as: + ![expand actions to show open code editor](./images/expand-code-editor.png "expand actions to show open code editor") - * ***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 + This displays the Code Editor in a side by side view with the Cloud Shell. + ![launch code editor](./images/code-editor-launch.png "launch code editor") -## Task 2: List all the Container Databases in a Compartment + Click ***Open*** and select ***PRE2981MC*** folder and open the ***MyWorksheet*** file. -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*** - - ``` - + ![open my worksheet](./images/open-myworksheet-mc.png "open my worksheet") - oci db database list --compartment-id {CompartmentID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table + You can use the code editor to copy and paste obtained environment details in the lab. - - ``` + ![show sample worksheet](./images/my-worksheet-sample.png "show sample worksheet") + + For better code viewing, under ***View*** select ***View: Toggle Word Wrap***. -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: + +3. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section. - > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{ContainerDatabaseOCID}"*** with the **Container Database OCID** obtained from ***Task 2*** + ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") + - ``` - + Paste the VM Cluster OCID value in your code editor. - 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. +4. Run the OCI CLI Command to get the VM Cluster Configuration. - ![list pluggable database](./images/getpdb.png " ") + >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 3)* - -## 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. + oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state",CompartmentOCID:"compartment-id"}' - For this lab, the JSON file is pre-created; you can view the local clone pluggable database details by reading the JSON file. - + ``` - + **Description:** - cat MyClonePDB.json + The OCI CLI command syntax is: **oci** ***db*** ***exadb-vm-cluster*** ***get*** ***--exadb-vm-cluster-id*** ***{VMClusterID}*** ***--query*** - - ``` - + **Where:** -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: + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exadb-vm-cluster*** is the **resource type** for the Exadata VM Cluster on Exascale Infrastructure. + * ***get*** is the **action** to get information about the Exadata VM Cluster on Exascale Infrastructure. + * ***--exadb-vm-cluster-id*** is the **parameter** for the ***VM Cluster OCID***. + * ***--query*** is the query parameter used for structured query options to display the specific VM Cluster data fields and values for the ***Display Name***, ***Enabled ECPUs***, ***Lifecycle state***, and ***Compartment OCID*** + + After running the command, you will see similar output below. + + ![show vm cluster details with compartment id](./images/show-vm-cluster-details-comp-ocid.png "show vm cluster details with compartment id") + + Pay attention to the following VM Cluster details from the command output: + * ***CompartmentOCID*** + * **Display Name** + * **Enabled ECPUs** + * **Lifecycle State** + + Copy the ***CompartmentOCID*** value and paste it value and paste it in your code editor. + +## Task 2: List the available Database Homes in a compartment using REST API + +1. From the Cloud Shell terminal, make an OCI REST API call to get a list of the available Database Homes in a compartment by running the **OCI RAW-REQUEST** command below: - > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{pluggableDatabaseID}"*** with the **Pluggable Database OCID** copied from ***Task3 Step 3*** + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{CompartmentOCID}"*** with the **Compartment OCID** obtained from ***Task 1 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 + - + 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; you will see that the local clone pluggable database is on a lifecycle state of ***PROVISIONING*** + **Description:** - ![local clone pluggable database](./images/clonepdb.png " ") + The REST API Request is: ***GET /20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10*** + * ***dbHomes*** is the **resource type** for the Oracle Database Home. + * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to list the available Database Homes. + * ***lifecycleState=AVAILABLE*** is the **query** to include a filter to return only Database Homes with the lifecycle state of Available. + * ***limit*** is the **query** to define the maximum number of items to return per page -## 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. You will see a similar output as below. + + ![list database homes](./images/list-dbhome.png "list database homes") + + Copy the **DB Home OCID** value from the ***"id"*** field and paste it in your notepad or text editor. -2. Make an OCI REST API call to get Exadata VM Cluster details by running the **OCI RAW-REQUEST** command below. + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the database homes in the specified compartment. - > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***Lab 6 (Task 1 step 2)*** +## Task 3: List the available Container Databases in a specified compartment using OCI CLI + +1. Run the OCI CLI Command to list the available Container Databases in a specified compartment. + + >**Note:** Replace ***{CompartmentOCID}*** with the Compartment OCID obtained from ***Task 1 Step 3*** ``` - oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}" + oci db database list --compartment-id {CompartmentOCID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table ``` - + + **Description:** - You will see a similar output below; pay attention to the **cpusEnabled** field. + The OCI CLI command syntax is: **oci** ***db*** ***database*** ***list*** ***--compartment-id*** ***{CompartmentOCID}*** ***--query*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***database*** is the **resource type** for the Container Database (CDB). + * ***list*** is the **action** to lists all Container Databases (CDBs) in a specified Compartment. + * ***--compartment-id*** is the **parameter** for the ***Compartment OCID***. + * ***--query*** is the query parameter used for structured query options to display the specific Container Database data fields and values for the ***Container Database Name***, ***Container Database OCID***, and ***Lifecycle state*** + + After running the command, you will see similar output below. + + ![show list of container databases](./images/list-cdb.png "show list of container databases") + + Copy the ***ContainerDatabaseOCID*** value and paste it in your code editor. + +## Task 4: List the available Pluggable Databases (PDBs) in a Container Database (CDB) using REST API + +1. Run the OCI CLI Command to list the available Pluggable Databases in a Container Database. + + >**Note:** Replace ***{ContainerDatabaseOCID}*** with the ***Container Database (CDB) OCID*** obtained from ***Task 3*** ``` - { - "data": { - "availabilityDomain": "cuGa:US-SANJOSE-1-AD-1", - "compartmentId": "ocid1.compartment.oc1.....", - "cpusEnabled": 4, - "dataCollectionOptions": { - "isDiagnosticsEventsEnabled": true, - "isHealthMonitoringEnabled": true, - "isIncidentLogsEnabled": true - }, - - "status": "200 OK" -} - + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10" + + ``` + **Description:** + + The REST API Request is: ***GET /20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10*** + + * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB). + * ***databaseId*** is the **Container Database OCID**. + * ***limit*** is the **query** to define the maximum number of items to return per page -## Task 6: List the Maintenance Updates that can be applied to the specified VM Cluster using REST API + After running the command, you will see similar output below. -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. + ![show list of pluggable databases](./images/list-pdbs.png "show list of pluggable databases") + + Look for the ***pdbName*** - ***MYPDB01*** and copy the **PDB OCID** value from the ***"id"*** field and paste it in your notepad or text editor. + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the Pluggable Databases in the Container Database. + +## Task 5: Create Thin Clone of Pluggable Database (PDB) using REST API + +1. Prepare the JSON file for the Create Pluggable Database REST API call request body that contain the Create Thin Clone Pluggable Database Details resource. - > **Note:** Replace the ***"{VMClusterOCID}"*** with the **VM Cluster OCID** copied from ***(Lab 6 Task 1 step 2)*** + For this lab, the JSON file is pre-created; you can view the Create Pluggable Database details by reading the JSON file using the Code Editor. + Open the ***Code Editor*** tab. Click ***Open***. + ![open code editor](./images/open-code-editor.png "open code editor") + + Select the ***PRE2981MC*** folder then select the ***MyThinClonePDB.json*** file and click on ***Open***. + + ![open MyThinClonePDB.json](./images/open-my-thin-clone.png "open MyThinClonePDB.json") + + Provide the required ***Create Pluggable Database*** details + + ![open MyThinClonePDB.json](./images/my-thin-clone-pdb-json.png "open MyThinClonePDB.json") + + * **pdbName:** ***"ThinPDB2"*** + * **pdbAdminPassword:** ***"Pass4OCW24Student-#"*** + * **tdeWalletPassword:** ***"Pass4OCW24Student-#"*** + * **containerDatabaseId:** ***"{ContainerDatabaseOCID}"*** - Replace ***{ContainerDatabaseOCID}*** with **CDB OCID** obtained from ***Task 3*** + * **pdbCreationTypeDetails:** + * **creationType:** ***"LOCAL\_CLONE\_PDB"*** + * **sourcePluggableDatabaseId:** ***{PluggableDatabaseOCID}*** - Replace ***{PluggableDatabaseOCID}*** with **PDB OCID** obtained from ***Task 4*** + * **isThinClone:** ***"true"*** + + +2. Make an OCI REST API call to create thin clone of pluggable database and starts a pluggable database (PDB) in the specified container database (CDB) by running the **OCI RAW-REQUEST** command below: + + Open the **OCI Cloud Shell** tab and run the following command + + ![create thin clone using REST API](./images/create-thin-clone-pdb.png "create thin clone using REST API") + + > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** + ``` - oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/vmClusters/{VMClusterOCID}/updates" + oci raw-request --http-method POST --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/pluggableDatabases" --request-body file://MyThinClonePDB.json + ``` - + **Description:** - ![list VM Cluster updates](./images/get-vmcluster-updates.png " ") + The REST API Request is: ***POST /20160918/pluggableDatabases*** - 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 + * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB). + * ***--request-body*** contains the **Create Pluggable Database Details** resource stored in the JSON file ***MyThinClonePDB.json***. + + After running the command, you will see similar output below. + + ![create thin clone using REST API](./images/create-thin-clone-pdb.png "create thin clone using REST API") + + You will see that the Pluggable Database status ***"lifecycle-state"*** is ***PROVISIONING***. + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to start the provisioning of the thin clone of a pluggable database. + +## Task 6: List Exascale Storage Vault using REST API + +1. Make an OCI REST API call to get a list of the Exascale Storage Vaults in the specified compartment by running the **OCI RAW-REQUEST** command below: + + > **Note:** Replace ***{CompartmentOCID}*** with the ***Compartment OCID*** obtained from ***Task 1*** + + ``` + + + oci raw-request --http-method GET --target-uri "https://database.us-sanjose-1.oraclecloud.com/20160918/exascaleDbStorageVaults?compartmentId={CompartmentOCID}&limit=10" + + + + ``` - ``` - - { - "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" -} + **Description:** + + The REST API Request is: ***GET /20160918/exascaleDbStorageVaults*** + + * ***exascaleDbStorageVaults*** is the **resource type** for the Exascale Storage Vault. + * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to get a list of the available Exascale Storage Vaults. + + After running the command, you will see similar output below. + + ![list exascale storage vault](./images/list-exascale-storage-vault-in-a-compartment.png "list exascale storage vault") + + Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of the available Exascale Storage Vaults in a specified comparment. - ``` - -You may now **proceed to the next lab**. +***Congratulations!!!*** You may now **proceed to the next lab**. ## Acknowledgements @@ -220,4 +293,4 @@ You may now **proceed to the next lab**. * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Leo Alvarado, Product Management, September 2023. +* **Last Updated By** - Leo Alvarado, Product Management, August 2024. 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 index ee78be0..aafc145 100644 Binary files a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/cloudshelllaunch.png 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/code-editor-launch.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/code-editor-launch.png new file mode 100644 index 0000000..f9f4ff7 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/code-editor-launch.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png new file mode 100644 index 0000000..81674f1 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png new file mode 100644 index 0000000..cdf1766 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png new file mode 100644 index 0000000..f2d59b2 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/expand-code-editor.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/expand-code-editor.png new file mode 100644 index 0000000..0ec3685 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/expand-code-editor.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-cdb.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-cdb.png new file mode 100644 index 0000000..cce8914 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-cdb.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 index 8528e80..77755d7 100644 Binary files a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhome.png 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-api/images/list-dbhomes.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhomes.png new file mode 100644 index 0000000..bbf159f Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-dbhomes.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png new file mode 100644 index 0000000..13232b0 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-pdbs.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-pdbs.png new file mode 100644 index 0000000..a3964a4 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/list-pdbs.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png new file mode 100644 index 0000000..60eeb0f Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-worksheet-sample.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-worksheet-sample.png new file mode 100644 index 0000000..5a448df Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/my-worksheet-sample.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/oci-cloud-shell.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/oci-cloud-shell.png new file mode 100644 index 0000000..97201c7 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-code-editor.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-code-editor.png new file mode 100644 index 0000000..bcf3f50 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-code-editor.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-my-thin-clone.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-my-thin-clone.png new file mode 100644 index 0000000..714b5b1 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-my-thin-clone.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png new file mode 100644 index 0000000..a716027 Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png differ diff --git a/exadata-database-service-xs/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png new file mode 100644 index 0000000..e8c9d1b Binary files /dev/null and b/exadata-database-service-xs/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.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 index 2e1bc7b..a19fb7c 100644 --- 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 @@ -89,6 +89,17 @@ To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***. ``` + **Description:** + + The OCI CLI command syntax is: **oci** ***db*** ***exascale-db-storage-vault*** ***get*** ***--exascale-db-storage-vault-id*** ***{ExascaleVaultID}*** + + **Where:** + + * ***db*** is the **service type** for the Oracle Database Cloud Services. + * ***exascale-db-storage-vault*** is the **resource type** for the Exascale Storage Vault. + * ***get*** is the **action** to get information about the Exascale Storage Vault Configuration. + * ***--exascale-db-storage-vault-id*** is the **parameter** for the Exascale Storage Vault OCID. + After running the command, you will see similar output below. ![show storage vault details](./images/get-storage-vault-details.png "show storage vault details") 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 index 991de1d..128da50 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-database.png 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 index cfcf1c9..56b7f06 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack-from-compartment.png 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 index 39b0c44..e163a19 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-create-stack.png 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 index aa74815..a6d7145 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-review.png 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-db-stack.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-stack.png new file mode 100644 index 0000000..7449ff0 Binary files /dev/null and b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-app-db-stack.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 index 4fca335..62651fe 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-application-stack.png 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-pdb.png b/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png index 73c1292..82ef757 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-deploy-exadata-database-pdb.png 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 index 7701c6b..78fc123 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-discover-dbstack.png 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 index 540f898..4ca1383 100644 Binary files a/exadata-database-service-xs/use-orm-generate-tf-dbstack/images/orm-download-dbstack.png 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/use-orm-generate-tf-dbstack.md b/exadata-database-service-xs/use-orm-generate-tf-dbstack/use-orm-generate-tf-dbstack.md index 53a2d2c..d5d1474 100644 --- 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 @@ -17,7 +17,7 @@ Estimated Time: 20 minutes This lab requires the completion of the following: -* Completion of **Lab7** +* Completion of **Lab1** ## Task 1: Generate Terraform baseline configuration for Database development environment using OCI Resource Manager @@ -27,23 +27,23 @@ This lab requires the completion of the following: 2. On the **Stacks** page, select your assigned compartment. -3. Click **Create stack**. +3. Click ***Create stack***. -4. On the **Create stack** page, under **Choose the origin of the Terraform configuration**, select **Existing compartment**. +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. +5. Select your ***assigned compartment*** and assigned **region** containing the Exadata Database Service on Exascale Infrastructure. ![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. +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** + >**Note:** For this lab, use ***MyTFBaseline-Database*** for the name of your discovered database stack and select your ***assigned compartment*** for the **Create in compartment** ![Create your discovered database stack](./images/orm-create-stack.png " ") @@ -69,37 +69,31 @@ This lab requires the completion of the following: >**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 is the discovered resource for the ***Exascale Storage Vault Resource*** - ``` + ``` - ## 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 Exascale Storage Vault Resource + + resource oci_database_exascale_db_storage_vault export_MyDemoStorageVault { + additional_flash_cache_in_percent = "0" + availability_domain = var.availability_domain--IBjw-US-SANJOSE-1-AD-1 + compartment_id = var.compartment_ocid + description = "MyDemoStorageVault" + display_name = "MyDemoStorageVault" + freeform_tags = {} + high_capacity_database_storage { + total_size_in_gbs = "300" + } + time_zone = "UTC" + } + ``` - This is the discovered resource for the **Exadata VM Cluster Resource** + This is the discovered resource for the ***Exadata VM Cluster on Exascale Infrastructure*** ``` @@ -108,94 +102,50 @@ This lab requires the completion of the following: ## 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 = { + resource oci_database_exadb_vm_cluster export_MyDemoVMCluster { + availability_domain = var.availability_domain--IBjw-US-SANJOSE-1-AD-1 + backup_network_nsg_ids = [] + backup_subnet_id = "ocid1.subnet.oc1.us-sanjose-1.xxxxxxxx" + cluster_name = "MyDemoClus" + compartment_id = var.compartment_ocid + data_collection_options { + is_diagnostics_events_enabled = "true" + is_health_monitoring_enabled = "true" + is_incident_logs_enabled = "true" } - 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" + display_name = "MyDemoVMCluster" + domain = "clientprivnet.mydemovcn.oraclevcn.com" + exascale_db_storage_vault_id = oci_database_exascale_db_storage_vault.export_MyDemoStorageVault.id + grid_image_id = "ocid1.dbpatch.oc1.us-sanjose-1.xxxxxxx" + hostname = "myhostvm" + license_model = "BRING_YOUR_OWN_LICENSE" + node_config { + enabled_ecpu_count_per_node = "8" + total_ecpu_count_per_node = "12" + vm_file_system_storage_size_gbs_per_node = "280" } - - - ``` - - 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 = { + node_resource { + node_name = "" } - display_name = "MyCustomDBHome" - freeform_tags = { + node_resource { + node_name = "" } - source = "NONE" - vm_cluster_id = oci_database_vm_cluster.export_MyVMClusterXX.id + nsg_ids = [] + scan_listener_port_tcp = "1521" + scan_listener_port_tcp_ssl = "2484" + shape = "EXADBXS" + ssh_public_keys = [] + subnet_id = "ocid1.subnet.oc1.us-sanjose-1.xxxxxxx" + system_version = "24.1.0.0.0.240517.1" + time_zone = "UTC" + + ignore_changes = [node_resource[0].node_name, node_resource[1].node_name] } ``` - 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*** ``` @@ -203,25 +153,23 @@ This lab requires the completion of the following: ## 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" - } + resource oci_database_pluggable_database export_pluggable_database { + #container_database_admin_password = + container_database_id = "ocid1.database.oc1.us-sanjose-1.xxxxxxx" + #convert_to_regular_trigger = <> + defined_tags = { + } + freeform_tags = { + } + #pdb_admin_password = + #pdb_creation_type_details = + pdb_name = "MYPDB01" + #refresh_trigger = <> + #rotate_key_trigger = <> + #should_create_pdb_backup = <> + #should_pdb_admin_account_be_locked = <> + #tde_wallet_password = <> +} ``` @@ -232,9 +180,9 @@ This lab requires the completion of the following: ![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**. +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***. + 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 " ") @@ -252,19 +200,19 @@ This lab requires the completion of the following: Provide required variable details for the **Application Server Stack**. - ![Deploy Application Stack](./images/orm-deploy-application-stack.png " ") + ![Deploy Application Stack](./images/orm-deploy-application-stack.png "Deploy Application Stack") - * 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 + * For the **ApplicationServer_CompartmentOCID**, Select your ***Assigned compartment*** + * Provide the **Application Server name**. For this lab, use the name ***MyAppServer*** Provide required variable details for the **Exadata Database Server Stack**. - ![Deploy Database PDB Stack](./images/orm-deploy-exadata-database-pdb.png " ") + ![Deploy Database PDB Stack](./images/orm-deploy-exadata-database-pdb.png "Deploy Database PDB Stack") - * 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** + * Provide the **Developer Container Database OCID**. For this lab, use the value for the ***ContainerDatabaseOCID*** obtained from ***Lab10 Task 3*** + * Provide the **Pluggable Database display name**. For this lab, use the name ***ThinPDB3*** + * Provide the ***Pluggable Database administrator password*** + * Provide the ***TDE Wallet Password*** Click on **Next** @@ -272,9 +220,7 @@ This lab requires the completion of the following: ![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 " ") + ![App and Database Available Stack](./images/orm-myappdbstack-available.png " ") 7. Create Stack Deployment Plan by: Clicking on **Plan** on the Stack details page. @@ -309,7 +255,7 @@ This lab requires the completion of the following: ![Stack Deployment Apply Succeeded ](./images/orm-apply-succeeded.png " ") -You may now **proceed to the next lab** +