4 Deploying Oracle Software on Oracle Database Appliance

Complete these tasks to deploy the Oracle Database Appliance software.

About Deploying Oracle Database Appliance 18.1

Review this information to understand how to deploy Oracle Database Appliance 18.1.

Oracle Database Appliance ships from the factory with a bare metal configuration, default ISO image, and Appliance Manager installed. To deploy Oracle Database Appliance to use Oracle Database 18.1, you must re-image the machine with the 18.1 image. Re-imaging uses ILOM to install Oracle Database Appliance software for Oracle Database 18.1 on the local (boot) drive.

After imaging is completed, redeploy the End User image, then restore from backup, as needed.

Re-imaging does not patch the firmware or update the component versions, it only re-images the local system disk from an OS perspective. Re-imaging with older release of Oracle Database Appliance software does not rollback the firmware version.

To reimage the Oracle Database Appliance node, use the Oracle Integrated Lights Out Manager (ILOM) interface that you configured as part of readying the system for deployment .

To complete the first part of the deployment, you can either connect a monitor and keyboard to the system or connect a laptop to the serial port. If you use the serial port, ensure that the baud rate speeds match. After the first network is configured, you can perform the remaining deployment steps on the Oracle Database Appliance system or from a remote system.

Re-imaging and deploying Oracle Database Appliance requires a direct connection to the system to configure the Oracle Integrated Lights Out Manager (ILOM) and the first network.

The procedure to deploy software consists of the following steps:

  1. Ready the system, including configuring the ILOM interface.

  2. If you are re-imaging an appliance that is already deployed, create a backup, if needed.

  3. Download the Oracle Database Appliance 18.1 image.

  4. Re-image the system with Oracle Database Appliance 18.1.

  5. Download the Oracle Database Appliance GI and DB software.

  6. Update the repository with Oracle Database Appliance GI and DB software.

  7. Launch the Web Console to deploy your configuration. The Web Console provides all of the fields necessary to deploy Oracle Database Appliance, including configuring the system, network, database, and optionally, Oracle Auto Service Request (Oracle ASR).

  8. Restore from backup, if needed.

Note:

Oracle Database Appliance 18.1 is only available for bare metal DCS platforms. When you deploy Oracle Database Appliance 18.1, the only database version available is Oracle Database 18.1.1.0.0.

Re-imaging Oracle Database Appliance with an Oracle Database 18.1 Image

Use Oracle Integrated Lights Out Manager (ILOM) to re-image Oracle Database Appliance with an Oracle Database 18.1image.

Before downloading the image, ensure that the initial network connection is configured. To use scp or sftp, you must first set up a static IP address (for example, oda_host) and configure Oracle Database Appliance with that address by using the configure-firstnet command. This command ensures the system is available in your network, enabling you to use the Oracle Appliance Manager Web Console to deploy Oracle Database Appliance.

  1. From an external client machine, log on to My Oracle Support. Locate the ISO patch for the Oracle Database Appliance18.1 ISO Image for your hardware model.
    See Appendix A in the Oracle Database Appliance Release Notes for patch information and links to download the patch for your hardware model.
  2. Select the patch version for Oracle Appliance Kit 18.1, then click Download to download the zip file onto your external client.
  3. Use either a Secure Copy (scp) command or a USB storage device to copy the file from the external client to dom0 on Node 0. Use the /tmp directory as the target location.

    Note:

    If you use a USB drive to transfer the file, then format it first as FAT32, ext3, or ext4. NTFS file formats are not supported.

  4. Unzip the patch bundle.
  5. Open a browser and connect to Oracle Integrated Lights Out Manager (ILOM) on Node0 as root.
    https://ilom-ip-address
  6. Launch the Remote Console.
    1. Expand Remote Control in the left navigation.
    2. Click the Redirection tab.
    3. Click Launch for the Remote Console in the Actions menu.
      The state of the system determines what appears on the Console page.
  7. Add the Oracle Database 18.1 for Oracle Database Appliance ISO image.
    1. Click the KVMS tab, then select Storage.
    2. Click Add.
    3. Browse to the Oracle Database Appliance Bare Metal ISO Image, highlight the image, then click Select.
    4. Click Connect.
      The mounting of the ISO image is successful when the Connect button changes to a Disconnect button.
    5. Click OK
      The CD-ROM icon in the top right corner is highlighted.
  8. Configure the CD-ROM as the next boot device.
    1. Expand Host Management in the left menu of the ILOM Remote Console tab.
    2. Click Host Control.
    3. Select CDROM from the Next Boot Device menu, then click Save.
  9. Power cycle the node.
    1. Click Power Control in the Host Management menu.
    2. Select Power Cycle , then click Save.

    When the node comes back after the power cycle, re-imaging starts automatically. The Oracle Linux page appears, followed by the Running Post-Install scripts page.

    The Running Post-Install scripts page is a static page and might give the impression that the re-imaging process is not progressing. The post-install process during re-imaging will wait until the synchronization between the partitions of the two mirrored local hard disks is complete, which can take 15 to 20 minutes to complete.

    To check the progress of re-synchronization, press the ALT-F2 key combination to open a second console and enter the following command:

    # cat /proc/mdstat

    When the re-synchronization is complete, re-imaging is completed and the machine restarts.

  10. If the machine is a multi-node server, then repeat the steps for Node1.
After the machine restarts, the system is ready for you to deploy the Oracle software on the appliance to create an Oracle Database Appliance bare metal platform.

Related Topics

Updating the Repository with the GI and RDBMS Files

Download the Oracle Database Appliance GI and RDBMS Software Clone File from My Oracle Support and update the patch repository.

Update the patch repository with the following patch files:

  • GI Clone: Contains the latest Grid Infrastructure components needed to deploy, or create, an Oracle Database Appliance.

  • RDBMS 18.1.1.0.0Software Clone file: Contains the components needed to create database homes and databases in Oracle Database Appliance.

The patches are available for download in My Oracle Support. You must download the GI and DB software files to an external client and then copy the files from the external client to a /tmp directory on the appliance. If there is more than one zip file for a patch, unzip and then concatenate the zip files. In some cases, there might not be sufficient space in the /tmp directory. Consider creating a /tmp directory in the /u01 directory.

Copy the file using a Secure Copy (scp) or Secure File Transfer Protocol (sftp) protocol. To use scp or sftp, you must first set up a static IP address (for example, oda_host) and configure Oracle Database Appliance with that address by using the configure-firstnet command. This command ensures the system is available in your network, enabling you to use the Oracle Appliance Manager Web Console to deploy Oracle Database Appliance.

  1. From an external client machine, log on to My Oracle Support.
  2. Locate and download the GI patch.
    The patch file is split into more than one zip file. You must unzip the files and concatenate the zip files into a single zip file. See Appendix A in the Oracle Database Appliance Release Notes for patch information and download links. Select 18.1.1.0.0 from the release drop-down menu.
    1. Download the GI patch to a temporary location on the external client.
    2. Unzip the files and concatenate the files into a single zip file. For example, a file named p27604593_18.zip.
  3. Locate and download the 18.1.1.0.0 RDBMS Clone patch to a temporary location on the external client.
    See Appendix A in the Oracle Database Appliance Release Notes for patch information and download links. Select 18.1.1.0.0 from the release drop-down menu.
  4. Upload the files from the external client to the appliance. You can use the scp protocol, sftp protocol, or a USB storage device to copy the files.
  5. Navigate to the directory and unzip each patch.
  6. Run the command odacli update-repository to unpack the bundle to the correct locations in the file system. You must include the fully qualified directory.
    If you have more than one bundle, you can use a comma-separated list. Spaces are not allowed between the filenames.
    # odacli update-repository -f /u01/tmp/patch_file_name.zip
  7. Run the command odacli list-jobs to check the status. 
    # odacli list-jobs
  8. If the system is a multi-node system, run these steps on both nodes.
After the GI and RDBMS Clone files are in the patch repository, you can deploy the appliance.

Related Topics

Deploying a Single Node Bare Metal Platform

Configure the system, network, user groups, and database and deploy the single node Oracle Database Appliance (X7-2S, X7-2M, X6-2S, X6-2M, or X6-2L.)

Use the checklists that you completed earlier as a reference for the configuration settings needed to deploy the appliance.

Before deploying Oracle Database Appliance, complete the tasks in “Preparing for Oracle Database Appliance Installation” and “Readying Oracle Database Appliance for Deployment”.

Complete the following tasks to prepare for deploying Oracle Database Appliance:

  1. Register your hardware SI and new software licenses that you received with Oracle Database Appliance to your My Oracle Support profile.

  2. Plan your configuration options.

  3. Gather your system requirements and complete the checklists for your deployment. You can use the checklists as a reference for the configuration settings needed to deploy the appliance.

Complete the following tasks to ready the system before deploying Oracle Database Appliance:

  1. Attach the network cables.

  2. Perform a first startup of the appliance.

  3. Configure Oracle Integrated Lights Out Manager (ILOM).

  4. Configure an initial network connection.

  5. Download the latest version of the Oracle Database Appliance Software and copy it to the appliance.

  6. Log into the Web Console. When you launch the Web Console on an unconfigured appliance, the Appliance page notifies you that the appliance is not configured and provides a link to the pages needed to configure and create the appliance.

See also:

Your browser determines how you log into the Web Console. In some cases, you must accept credentials for the DCS-controller on port 7093, and DCS-agent on port 7070. If you experience problems launching the Web Console, see Logging into the Web Console for more information.

  1. Launch the Web Console and enter the user name oda-admin and password. 
    https://ODA-host-ip-address:7093/mgmt/index.html
  2. Click Create Appliance.
  3. Enter the following information to configure the system information:
    1. Host Name: Enter the host name.
      The host name can contain alphanumeric characters and dashes (-), but cannot start with a number or dash (-) or end with dash (-). Do not exceed 30 characters.
    2. Domain Name: Enter the domain name.
      For example, example.com.
    3. (Optional) Region: Select the region of the world where the Oracle Database Appliance is located.
    4. (Optional) Time Zone: Select the time zone where the Oracle Database Appliance is located.
    5. Data Storage Percentage: Enter a whole number between 10 and 90 to define the percentage of storage reserved for DATA, the remainder is reserved for RECO. For example, if you enter 80, then 80% of the storage is for DATA and 20% is for RECO.
    6. Diskgroup Redundancy: This field appears when the Web Console detects that the system has at least five (5) NVMe storage devices. Select Normal or High.
      If the system has less than five (5) NVMe storage devices, redundancy is automatically set to Normal and this field does not appear.
    7. Master Password and Confirm Password: Enter the master password in both fields.
      The master password is the password set for UNIX users, root, SYS, SYSTEM, and PDBADMIN. The password must begin with an alpha character and cannot contain quotation marks. Do not exceed 30 characters.
    8. (Optional) DNS Servers: Enter addresses for one or more DNS servers.
    9. (Optional) NTP Servers: Enter addresses for one or more NTP servers.
  4. Enter the following information to configure the network information:
    The Network Information page enables you to configure the primary client access network and an Oracle Integrated Lights Out Manager (ILOM) network. You are only required to configure the client access network. The ILOM configuration is optional if you already configured the ILOM for the appliance and you do not need to make changes.
    1. Client Access Network IP Address: Enter the IP address for the primary client access network.
    2. Client Access Network Subnet Mask: Enter the subnet mask address for the primary client access network.
    3. Client Access Network Gateway: Enter the gateway address for the primary client access network.
    4. (Optional) ILOM Host Name: Enter the name of the Oracle ILOM host.
    5. (Optional) ILOM Network IP Address: Enter the IP address for the ILOM.
    6. (Optional) ILOM Network Subnet Mask: Enter the subnet mask address for the ILOM.
    7. (Optional) ILOM Network Gateway: Enter the gateway address for the ILOM.
  5. Determine how you want to configure your users and groups and whether or not you want to allow operating system role separation:
    • Two users with six groups: Customize Users and Groups, select No. Allow OS Role Separation, select Yes. This is the default configuration.
      Description of GUID-A2E586CE-51E0-4699-84CD-086C7FA853A3-default.png follows
      Description of the illustration GUID-A2E586CE-51E0-4699-84CD-086C7FA853A3-default.png
    • Two customized users with six customized groups: Customize Users and Groups, select Yes. Allow OS Role Separation, select Yes.
    • Single user with two groups: Customize Users and Groups, select No. Allow OS Role Separation, select No
    • Single user with six groups: Customize Users and Groups, select Yes. Allow OS Role Separation, select No. SAP deployments use this configuration.
  6. Do you want to create an initial database? Select Yes and go to Step 8 or select No and go to Step 9.
  7. Enter the following information to configure the database:
    1. DB Name: Enter a name for the database.
      The name must contain alphanumeric characters and cannot exceed 8 characters. Enter a name, do not use the default database name db1.
    2. (Optional) DB Unique Name: Enter a globally unique name for the database.
      Databases with the same DB Name within the same domain (for example, copies of a database created for reporting or a physical standby) must have a different DB Unique Name that is unique within the enterprise. The name can contain alphanumeric, underscore (_), dollar ($), and pound (#) characters, but must begin with an alphabetic character. No other special characters are permitted in a database name. The unique name cannot exceed 30 characters.
    3. DB Version: Select a database bundle patch number.
    4. CDB: Select Yes or No to specify whether or not you want a Container Database (CDB). This field is only visible for Oracle Database 12.2.x.
    5. (Optional) PDB Name: Enter a name for the pluggable database (PDB).
      The name must begin with an alphanumeric character. The following characters are valid: alphanumeric characters, and underscore (_).
    6. (Optional) PDB Admin User: Enter an Admin user name for the pluggable database (PDB).
    7. Database Edition: Select the Oracle Database edition, either Standard Edition and Enterprise Edition. Your license determines which database edition you are eligible to create in the appliance.
    8. (Optional) Shape: Select a database shape from the list.
    9. (Optional) Database Class: Select a database class from the list.
      The database version and edition determine the classes that are available. The Enterprise Edition supports OLTP, DSS, or IMDB, the Standard Edition only supports OLTP.
    10. (Optional) Storage: Select ACFS or ASM.
      The default is ASM.
    11. (Optional) Configure EM Express: Select Yes to configure the Oracle Enterprise Manager Database Express (EM Express) console.
    12. (Optional) Characterset: Select a characterset.
    13. (Optional) National Characterset: Select a national characterset.
    14. (Optional) Language: Select the database language.
    15. (Optional) Territory: Select a territory or location from the list.
  8. (Optional) Configure and enable Oracle ASR on the ASR page.

    You can configure and enable Oracle Auto Service Request (Oracle ASR) now or later:

    • To not enable Oracle ASR during deployment, select No and click Submit. After deployment, you can configure an internal Oracle ASR or register with an external Oracle ASR Manager from either the Web Console or command-line interface.

      • Internal Oracle ASR: choose to configure Oracle ASR Manager on Oracle Database Appliance or use Oracle ASR Manager configured on another server in the same network as your appliance.

      • External Oracle ASR: If you already have Oracle ASR Manager configured elsewhere, you can register Oracle Database Appliance with your existing Oracle ASR Manager.

    • To enable Oracle ASR, select Yes and complete the fields:
    1. ASR User Name: Enter the e-mail address associated with the My Oracle Support account under which the server is registered.
    2. Password: Enter the password associated with the My Oracle Support account under which the server is registered.
    3. SNMP Version: Select V2 or V3. V2 is the default and recommended version.
    4. (Optional) HTTP Proxy used for Upload to ASR: Select Yes or No.
    5. Proxy Server Name: If you are using a proxy for upload, enter the proxy server name.
    6. Proxy Port: If you are using a proxy for upload, enter the proxy port.
    7. (Optional) HTTP Proxy Requires Authentication: If you are using a proxy for upload, select Yes if you require authentication. If you do not require authentication, select No.
    8. (Optional) Proxy Password: If you are using a proxy for upload and require authentication, enter the proxy password.
  9. Click Submit. When prompted, click Yes to confirm that you want to start the job to deploy the appliance.

The job to create the appliance takes time to complete. To monitor the job progress, click the Activity tab . Click the job number to view the tasks.

The deployment is complete when the word SUCCESS appears after each task. To check the status from the command line, run the command odacli list-jobs . A job is not complete if the status is running.

After deployment, the root and database users SYS, SYSTEM, and PDBADMIN are set to the master password. The oracle and grid passwords are set to password. Change these passwords to comply with your user security protocols.

Deploying a Multi-Node Bare Metal Platform

Configure the system, network, user groups, and database and deploy Oracle Database Appliance X7-2-HA.

Use the checklists that you completed earlier as a reference for the configuration settings needed to deploy the appliance. When you launch the Web Console on an unconfigured appliance, the Appliance page notifies you that the appliance is not configured and provides a link to the pages needed to configure and create the appliance.

See Also:

Your browser determines how you log into the Web Console. In some cases, you must accept credentials for the DCS-controller on port 7093, and DCS-agent on port 7070. If you experience problems launching the Web Console, see Logging into the Web Console for more information.

Before deploying Oracle Database Appliance, complete the tasks in “Preparing for Oracle Database Appliance Installation” and “Readying Oracle Database Appliance for Deployment”.

  1. Open a browser and enter the following URL to launch the Web Console:
    The URL must include the host name or IP address of the first node (Node0).
    https://Node0-ODA-host-ip-address:7093/mgmt/index.html
  2. Enter the user name oda-admin and the password.
  3. Click Create Appliance.
    If Create Appliance is disabled, ensure that you are launching the console on the first node (Node0).
  4. Enter the following system information to configure the system:
    1. Host Name: Enter the host name.
      The host name can contain alphanumeric characters and dashes (-), but cannot start with a number or dash (-) or end with dash (-). Do not exceed 30 characters.
    2. Domain Name: Enter the domain name.
    3. Region: Select the region of the world where the Oracle Database Appliance is located.
    4. Time Zone: Select the time zone where the Oracle Database Appliance is located.
    5. (Optional) DNS Servers: Enter addresses for one or more DNS servers.
    6. (Optional) NTP Servers: Enter addresses for one or more NTP servers.
    7. Diskgroup Redundancy: This field appears when the Web Console detects that the system has at least five (5) NVMe storage devices. Select Normal or High.
      The redundancy level is for DATA, RECO, and FLASH. If you select High redundancy, then DATA, RECO, and FLASH are all High redundancy.

      If the system has less than five (5) NVMe storage devices, redundancy is automatically set to Normal and this field does not appear.

    8. Data Storage Percentage: Enter a whole number between 10 and 90 to define the percentage of storage reserved for DATA, the remainder is reserved for RECO. For example, if you enter 80, then 80% of the storage for DATA and 20% for RECO.
    9. Master Password and Confirm Password: Enter the master password in both fields.
      The master password is the password set for UNIX users, root, SYS, SYSTEM, and PDBADMIN. The password must begin with an alpha character and cannot contain quotation marks. Do not exceed 30 characters.
  5. Enter the following information to configure the network:
    This page enables you to configure the primary client access network, virtual networks, and an Oracle Integrated Lights Out Manager (ILOM) network. You are only required to configure the client access network. The ILOM configuration is optional if you already configured the ILOM for the appliance and you do not need to make changes.
    1. Client Access Network Host Name: For Node0, enter the host name for the primary client access network.
    2. Client Access Network IP Address: For Node0, enter the IP address for the primary client access network.
    3. Client Access Network Subnet Mask: Enter the subnet mask address for the primary client access network.
    4. Client Access Network Gateway: Enter the gateway address for the primary client access network.
    5. Client Access Network Interface: Enter the interface for the primary client access network.
    6. VIP Name for Node0: Enter the name of the virtual IP network for Node0.
    7. VIP IP Address for Node0: Enter the virtual IP address that resides on Node0 and is shared between the nodes.
    8. VIP Name for Node1: Enter the name of the virtual IP network for Node0.
    9. VIP IP Address for Node1: Enter the virtual IP address that resides on Node1 and is shared between the nodes.
    10. (Optional) ILOM Host Name: Enter the name of the Oracle ILOM host.
    11. (Optional) ILOM Network IP Address: Enter the IP address for the ILOM.
    12. (Optional) ILOM Network Subnet Mask: Enter the subnet mask address for the ILOM.
    13. (Optional) ILOM Network Gateway: Enter the gateway address for the ILOM.
  6. Determine how you want to configure your users and groups and whether or not you want to allow operating system role separation:
    • Two users with six groups: Customize Users and Groups, select No. Allow OS Role Separation, select Yes. This is the default configuration.
      Description of GUID-A2E586CE-51E0-4699-84CD-086C7FA853A3-default.png follows
      Description of the illustration GUID-A2E586CE-51E0-4699-84CD-086C7FA853A3-default.png
    • Two customized users with six customized groups: Customize Users and Groups, select Yes. Allow OS Role Separation, select Yes.
    • Single user with two groups: Customize Users and Groups, select No. Allow OS Role Separation, select No
    • Single user with six groups: Customize Users and Groups, select Yes. Allow OS Role Separation, select No. SAP deployments use this configuration.
  7. Do you want to create an initial database? Select Yes and go to Step 8 or select No and go to Step 9.
  8. Enter the following information to configure an initial database:
    1. DB Name: Enter a name for the database.
      The name must contain alphanumeric characters and cannot exceed 8 characters.
    2. (Optional) DB Unique Name: Enter a globally unique name for the database.
      Databases with the same DB Name within the same domain (for example, copies of a database created for reporting or a physical standby) must have a different DB Unique Name that is unique within the enterprise. The name must contain alphanumeric, underscore (_), dollar ($), and pound (#) characters, but must begin with an alphabetic character. No other special characters are permitted in a database name. The unique name cannot exceed 30 characters.
    3. DB Version: Select a database bundle patch number.
    4. CDB: Select Yes or No to specify whether or not you want a Container Database (CDB).
    5. PDB Name: Enter a name for the pluggable database (PDB).
      The name must begin with an alphanumeric character. The following characters are valid: alphanumeric characters, and underscore (_).
    6. PDB Admin User: Enter an Admin user name for the pluggable database (PDB).
    7. Database Edition: Select the Oracle Database edition, either Standard Edition and Enterprise Edition. Your license determines which database edition you are eligible to create in the appliance.
    8. Deployment: Select a deployment type from the list. The options are RAC, RAC-One, or SI (single instance database). If you select a single instance database, then select the node for the SI database deployment.
      If you select a single instance database, then you have the option to create the database on either Node0 or Node1. The default is Node0.
    9. Shape: Select a database shape from the list.
    10. Database Class: Select a database class from the list. The options are OLTP, DSS, or IMDB.
    11. Storage: Select ACFS or ASM.
      ASM is the default.
    12. Date Files on Flash Storage: Select Yes or No.
      This option is only available if the HA system has HDD storage drives.
    13. Configure EM Express: Select Yes to configure the Oracle Enterprise Manager Database Express (EM Express) console.
    14. Characterset: Select a characterset.
    15. National Characterset: Select a national characterset.
    16. Language: Select the database language.
    17. Territory: Select a territory or location from the list.
  9. (Optional) Configure and enable Oracle ASR on the ASR page.

    You can configure and enable Oracle Auto Service Request (Oracle ASR) now or later:

    • To not enable Oracle ASR during deployment, select No and click Submit. After deployment, you can configure an internal Oracle ASR or register with an external Oracle ASR Manager from either the Web Console or command-line interface.

      • Internal Oracle ASR: choose to configure Oracle ASR Manager on Oracle Database Appliance or use Oracle ASR Manager configured on another server in the same network as your appliance.

      • External Oracle ASR: If you already have Oracle ASR Manager configured elsewhere, you can register Oracle Database Appliance with your existing Oracle ASR Manager.

    • To enable Oracle ASR, select Yes and complete the fields:
    1. ASR User Name: Enter the e-mail address associated with the My Oracle Support account under which the server is registered.
    2. Password: Enter the password associated with the My Oracle Support account under which the server is registered.
    3. SNMP Version: Select V2 or V3. V2 is the default and recommended version.
    4. HTTP Proxy used for Upload to ASR: Select Yes or No.
    5. Proxy User Name: If you are using a proxy for upload, enter the proxy user name.
    6. Proxy Port: If you are using a proxy for upload, enter the proxy port.
    7. (Optional) HTTP Proxy Requires Authentication: If you are using a proxy for upload, select Yes if you require authentication. If you do not require authentication, select No.
    8. (Optional) Proxy Password: If you are using a proxy for upload and require authentication, enter the proxy password.
  10. Click Submit. When prompted, click Yes to confirm that you want to start the job to deploy the appliance.
The job to create the appliance takes time to complete. To monitor the job progress, click the Activity tab . Click the job number to view the tasks.

After deployment, the root and database users SYS, SYSTEM, and PDBADMIN are set to the master password. The oracle and grid passwords are set to the default password. Change these passwords to comply with your user security protocols.