Skip to content

Commit

Permalink
WMS ID # 11698 -- WIP -- Update MC PRE2981 -- Apply uniform naming st…
Browse files Browse the repository at this point in the history
…andards & Update Lab 2 & 9 (#66)

* Update Lab 1 to 3 for OCW24 WMS ID 11641

Update Lab 1 to 3 for OCW24 WMS ID 11641

* Update Lab 1 filename to lowercase

HOL 2952 -- WMS ID 11641 -- Update Lab 1 filename to lowercase

* Rename create-VMCluster-CDB-PDB-on-Exascale.md to create-vmcluster-cdb-pdb-on-exascale.md

Signed-off-by: eambler <[email protected]>

* Update Lab 3 images and Step 6 instructions

Update Lab 3 images and Step 6 instructions. Added step to defer immediate PDB backup after clone creation.

* Adding Labs for OCW24 Master Class

Adding Labs for OCW24 Master Class

* Update configure-network-settings.png

Adjust Hostname Prefix to not conflict with DB Name in instructions

* WMS ID 11641 -- HOL 2952 -- Update Lab 2 images and minor text and look and feel  updates

WMS ID 11641 -- HOL 2952 -- Update Lab 2 images and minor text and look and feel  updates

* WMS # 11698 - Update Labs for OCW24 Masterclass [PRE2981]

WMS # 11698

 Update Labs for OCW24 Masterclass [PRE2981]

* WMS ID # 11698 -- WIP -- Update MC PRE2981 -- Working on Lab 2

WMS ID # 11698 -- Updating Lab 2 to have proper Naming and images for Standby VM Cluster

* WMS ID # 11698 -- WIP -- Update MC PRE2981 -- Apply uniform naming standards

WMS ID # 11698 -- WIP -- Update MC PRE2981 -- Apply uniform naming standards & Updated Lab 2 & 9

---------

Signed-off-by: Hope Fisher <[email protected]>
Signed-off-by: eambler <[email protected]>
Co-authored-by: Hope Fisher <[email protected]>
  • Loading branch information
eambler and hope-fisher authored Aug 23, 2024
1 parent 68c78a1 commit 6167948
Show file tree
Hide file tree
Showing 24 changed files with 142 additions and 53 deletions.
Original file line number Diff line number Diff line change
@@ -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**.

![Navigate 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**.

<!--
## Learn More
* Click [here](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/exadata/doc/ecc-create-first-db.html) to learn more about Creating an Oracle Database on Exadata Database Service.
-->

## Acknowledgements

* **Author** - Leo Alvarado, Eddie Ambler, Product Management

* **Contributors** - Tammy Bednar, Product Management

* **Last Updated By** - Leo Alvarado, Product Management, September 2023.
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

## Introduction

This lab walks you through how to create an Exadata VM Cluster & Database Home deployed on the Exadata Database Service on Exascale Infrastructure using the OCI Console. This Exadata VM Cluster will be used as a standby target inour upcoming labs.
This lab walks you through how to create an Exadata VM Cluster & Database Home deployed on the Exadata Database Service on Exascale Infrastructure using the OCI Console. This Exadata VM Cluster will be used as a standby target in our upcoming labs.


Estimated Time: 2 Hours 10 minutes
Expand All @@ -30,61 +30,60 @@ This lab requires completion of the following:

2. In the left rail, **VM Clusters** is selected by default. Under **List Scope**, Select your assigned standby compartment named ***MyStandbyCompartmentXX***.

![Select Compartment where Standby Exadata VM Cluster will reside](./images/select-standby-compartment.png" ")
![Select Compartment where Standby Exadata VM Cluster will reside Image](./images/select-standby-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 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 ***MyStandbyVMClusterXX***
* **For Display Name:** Enter ***MyStandbyVMClusterXX***

* For Cluster Name: Enter ***MyDemoClus***
* **For Cluster Name:** Enter ***MyClusterXX***

* For Availability Domain: Select the availability domain from the displayed options available.
* **For Availability Domain:** Select the availability domain from the displayed options available.

![Provide Basic Standby VM Cluster Info Image](./images/provide-basic-standby-vm-cluster-info-exascale.png" ")

5. **To Configure the VM cluster, provide the following information:**
* For the number of VMs in the cluster: ***Enter 2***
* For ECPUs enabled per VM: ***Enter 8***
* **For number of VMs in the cluster:** ***Enter 2***
* **For ECPUs enabled per VM:** ***Enter 8***

<u>**Size the VM file system storage**</u>:
* For system storage capacity per VM (GG): ***Enter 280***
* **For system storage capacity per VM (GB):** ***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" ")
![Configure VM Cluster](./images/configure-standby-vm-cluster-exascale.png" ")

6. **Enter Configuration Details for Exascale Database Storage Vault:**
* Select **Create new vault**.
* Select ***Create new vault***.

**For a new vault, specify the following:**
* For the **Exascale Vault name:** enter ***MyStandbyStorageVaultXX*** .
* For the **Storage Capacity for Databases (GB):** ***enter 300***.

**Note:** The minimum size configuration for an Exascale Database Storage Vault is 300 GB. 50 GB of the space that you allocate in your Vault is reserved for an internal ACFS file system. This ACFS file system resides within your Exascale Database Storage Vault, but is reserved for system use. Thus, if you provisioned the minimum of 300 GB in your Exascale Database Storage Vault, then 250 GB of that 300 GB capacity will be available storage for your databases.
> **Note:** The minimum size configuration for an Exascale Database Storage Vault is 300 GB. 50 GB of the space that you allocate in your Vault is reserved for an internal ACFS file system. <br>This ACFS file system resides within your Exascale Database Storage Vault, but is reserved for system use. <br>Thus, if you provisioned the minimum of 300 GB in your Exascale Database Storage Vault, then 250 GB of that 300 GB capacity will be available storage for your databases.
When you create a new vault, the Provisioning status window opens to provide you with the status of vault creation, and the name of the vault that is being created in the format Vault-YYYYMMDDHHMM indicating the creation date, where YYYY is the year, MM is the month, DD is the day, HH is the hour, and Mm is the minute.

![Configure Exascale Storage Vault](./images/configure-exascale-storage-vault.png" ")
![Configure Exascale Storage Vault for Standby VM Cluster Image](./images/configure-exascale-storage-vault-for-standby-vmc.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. <br/>
***Accept the default values for the 23ai release***.

* **Add your SSH Key for future access to your VMs**. <u>Choose from:</u>
![Select Grid Infrastructure version Image](./images/select-grid-infra-version.png" ")

8. **Add your SSH Key for future access to your VMs**. <u>Choose from:</u>

* **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.
* **Generate SSH key pair**(Default option) ***Select this option to generate an SSH keypair for this lab.*** <br>Then in the dialog below click ***Save private key*** to download the key, and then 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" ")
![Add SSH Key Image](./images/add-ssh-key.png" ")


8. **To Configure the network settings, Select VCN and select Client and Backup subnet**
9. **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***. <br/>
Then select the Virtual Cloud Network named ***MyDemoVCN***.

Expand All @@ -93,52 +92,51 @@ This lab requires completion of the following:
* **For the Backup Subnet:** Click Change Compartment and select compartment named ***MyDemo***. <br/>
Then select the Backup Subnet named ***MyBackup-PrivateSubnet***.

* **For the Hostname Prefix:** Enter ***MyHostVM***
* **For the Hostname Prefix:** Enter ***StandbyHost***

![Configure Network Settings](./images/configure-network-settings.png" ")
![Configure Standby VM Network Settings Image](./images/configure-standby-vm-network-settings.png" ")

9. **Select license type & choose opt-in choices for Diagnostic & Collections options.**
10. **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" ")
![Choose BYOL for VM Cluster License Type Image](./images/choose-byol-license-type.png" ")

10. **Select Diagnostic and Collections Options**
11. **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.
12. Click **Create VM Cluster** to proceed with provisioning.
* The provisioning automation will display the Vault creation progress screen
* Next, you will see the **VM Cluster Details** page displayed initially with a state of ***PROVISIONING*** and then a state of ***AVAILABLE*** once the process completes.

![Vault Creation Progress Image](./images/vault-creation-progress.png" ")
![Standby VM Cluster Creation Provisioning Image](./images/standby-vmc-creation-provisioning.png" ")
![Standby VM Cluster Creation Available Image](./images/standby-vmc-creation-available.png" ")



## Task 2: Create an Oracle Database Home 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**.
1. On the **VM Cluster Details page** under **Resources** Click on ***Database Homes*** and then click on the ***Create Database Home** button.

![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ")
![Select Create Database Home button Image](./images/dbhome-create-for-standby-vmc.png " ")

2. **Navigate to the cloud VM cluster you want to create the database home in:**
* In the left rail, ensure ***VM Clusters*** is selected.
* Under **List Scope**, Select your assigned compartment named ***MyStandbyCompartmentXX***.
* Then **click on your VM Clusters** ***assigned name*** to view the **VM Cluster Details page**.

![Select Compartment and VM Cluster where Container Database will reside](./images/select-compartment-and-vm-cluster.png" ")
2. On the **Create Database Home page**, enter ***MyDemo23aiDBhome02*** and validate that the **Database image** selected is ***Oracle Database 23ai***.

![Name VMC Standby DBhome and Select Version Image](./images/dbhome-name-and-select-version-for-standby-vmc.png " ")

3. On the **VM Cluster Details page** under **Resources** Click on **Database Homes** and then click on the ***Create Database Home** button.
3. Click on the ***Create*** button to proceed with creating the Database Home.

![Create Container Database button](./images/vmc-details-pg-create-cdb-on-exascale.png " ")
* The provisioning automation will display the **Database Home Details** page with a state of ***PROVISIONING*** and then a state of ***AVAILABLE*** once the process completes.

4.
![Standby VMC DB Home Creation Provisioning Image](./images/dbhome-creation-provisioning-for-standby-vmc.png" ")

8. Click on the **Create Container Database** button to proceed with creating the Container Database.
![Standby VMC DB Home Creation Available Image](./images/dbhome-creation-completed-for-standby-vmc.png" ")

![Container Database Details Page Image](./images/cdb-details-page-with-pdb.png " ")
***!!! Congratulations:*** You may now **proceed to the next lab**.


Expand All @@ -152,4 +150,4 @@ In the Edit Diagnostics Collection Settings dialog, you can enable or disable an

* **Contributors** - Tammy Bednar, Product Management

* **Last Updated By** - Eddie Ambler, Product Management, July 2024.
* **Last Updated By** - Eddie Ambler, Product Management, August 2024.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ This lab requires the completion of the following:
* In the **Clone Pluggable Database** configuration page, select the PDB Clone type. Select ***Local Clone***.
* Provide the information to configure the new PDB.
* For the **PDB Name** enter: ***ThinPDB1***
* For the **Database TDE wallet password** enter: ***Pass4StudentOCW24-#***
* For the **Database TDE wallet password** enter: ***Pass4OCW24Student-#***
* For this lab we will defer the initial PDB backup by ***unchecking the box*** to **Take a backup of the PDB immediately after cloning**
* Next, ensure to ***check the box*** to **Enable Thin Clone**
* Click on the ***Create Pluggable Database*** button to start the clone provisioning process.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ In the Edit Diagnostics Collection Settings dialog, you can enable or disable an
5. Specify the **Database Home Source and Administrator Credentials:**
* For the **Database Home source** choose: **Select an Existing Database Home**
* Select Database Home with display name of ***MyDemo23aiDBhome01***
* Next configure your **Administrator Credentials:** by entering ***Pass4StudentOCW24-#*** as the **password** for the **sys** username.
* Next configure your **Administrator Credentials:** by entering ***Pass4OCW24Student-#*** as the **password** for the **sys** username.

![Define DBhome and Admin Password Image](./images/define-dbhome-and-admin-pwd.png " ")

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,9 @@ This lab requires completion of the following:

**<u>In the Select Peer VM Cluster Section of the page:</u>**

* For the **Peer Region**: Select your ***assigned peer region***
* For the **Availability Domain**: Select your ***assigned availabilty domain***
* Then select the **Compartment** named ***MyDemoStandby*** and Select the **peer VM Cluster** named ***MyDemoStandbyVMCluster***
* For the **Peer Region**: Select your ***assigned Peer Region***
* For the **Availability Domain**: Select your ***assigned Availabilty Domain***
* Then select the **Compartment** named ***MyStandbyCompartmentXX*** and Select the **peer VM Cluster** named ***MyStandbyVMClusterXX***

>**Note:** The peer Region selected will determine if you are configuring a local standby or a DR standby.
Expand All @@ -70,12 +70,12 @@ This lab requires completion of the following:
![Select Peer VMC and Data Guard Association Details Image](./images/choose-peer-vmc-and-dg-association-details.png " ")

6. **Choose the Database Home and name the standby database:**
* For the **Database Home** choose ***Select an existing Database Home*** then select ***MyDemoStandby23aiDBHome02***.
* For the **Database Home** choose ***Select an existing Database Home*** then select ***MyDemo23aiDBHome02***.

* For the **Database unique name** for the standby database: enter ***MyDemoDB_23aiStandbyXX***
<br/>( Where ***XX*** is your assigned student # for the workshop).

* For the **Database password**. For this lab, use ***Pass4OCW24-#***
* For the **Database password**. For this lab, use ***Pass4OCW24Student-#***

**<u>Under Advanced Options on the Management Tab:</u>**

Expand All @@ -90,8 +90,7 @@ This lab requires completion of the following:
![Data Guard Association Completed Image](./images/dataguard-association-completed.png " ")


You may now **proceed to the next lab**
***Congratulations***, you may now **proceed to the next lab**.

## Learn More

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 6167948

Please sign in to comment.