Previous Next JavaScript must be enabled to correctly display this content

## 4 Provisioning Oracle Database Appliance Bare Metal System

Understand the process to configure Oracle Database Appliance bare metal system.

The Browser User Interface is the preferred method of deploying your bare metal platform configuration. The Browser User Interface provides all of the fields necessary to provision Oracle Database Appliance, including configuring the system, network, database, and Oracle Auto Service Request (Oracle ASR). If you prefer to use the command-line interface, you must create a JSON file to configure the deployment options.

- Verifying Cabling and Network Connections
  After powering on Oracle Database Appliance, verify that the network connections are set up correctly.
- Plumbing the Network
  Plumb the Oracle Database Appliance network with the public internet protocol (IP) information assigned to a node, to enable provisioning of the Oracle Database Appliance software.
- Downloading Oracle Database Appliance Software
  Download Oracle Database Appliance software and copy to a temporary location before applying updates to your appliance.
- Installing Oracle Database Appliance Software
  Install Oracle Database Appliance software, before creating the appliance.
- Creating the Appliance
  Create the appliance using the Browser User Interface or ODACLI commands.
- Managing Local Volumes
  Understand how you can modify the size of logical volumes `LOGVOLOPT` and `LOGVOLU01`.

Related Topics

- Deployment Checklist for Oracle Database Appliance Bare Metal Systems

### Verifying Cabling and Network Connections

After powering on Oracle Database Appliance, verify that the network connections are set up correctly.

Run the validation scripts only on Oracle Database Appliance HA models.

1. Log into the Oracle Database Appliance console and access the server node with user name as `root` and password `welcome1`.
2. Run validation scripts on both nodes, to verify cabling. For example:

       # /opt/oracle/dcs/bin/odacli validate-storagetopology
       INFO : ODA Topology Verification
       INFO : Running on Node0
       INFO : Check hardware type
       SUCCESS : Type of hardware found : X7-2
       INFO : Check for Environment(Bare Metal or Virtual Machine)
       SUCCESS : Type of environment found : Bare Metal
       INFO : Check number of Controllers
       SUCCESS : Number of ahci controller found : 1
       SUCCESS : Number of External SCSI controllers found : 2
       INFO : Check for Controllers correct PCIe slot address
       SUCCESS : Internal RAID controller :
       SUCCESS : External LSI SAS controller 0 : 3b:00.0
       SUCCESS : External LSI SAS controller 1 : 5e:00.0
       INFO : Check if JBOD powered on
       SUCCESS : 2JBOD : Powered-on
       INFO : Check for correct number of EBODS(2 or 4)
       SUCCESS : EBOD found : 4
       INFO : Check for External Controller 0
       SUCCESS : Cable check for port 0 on controller 0
       SUCCESS : Cable check for port 1 on controller 0
       SUCCESS : Overall Cable check for controller 0
       INFO : Check for External Controller 1
       SUCCESS : Cable check for port 0 on controller 1
       SUCCESS : Cable check for port 1 on controller 1
       SUCCESS : Overall Cable check for controller 1
       INFO : Check for overall status of cable validation on Node0
       SUCCESS : Overall Cable Validation on Node0
       SUCCESS : JBOD0 Nickname set correctly
       SUCCESS : JBOD1 Nickname set correctly

3. If there is a storage expansion shelf connected to the appliance, then power it on. Run the `storagetopology` command on both nodes to make sure the cabling is correct. For example:

       # /opt/oracle/dcs/bin/odacli validate-storagetopology
       INFO : ODA Topology Verification
       INFO : Running on Node0
       INFO : Check hardware type
       SUCCESS : Type of hardware found : X7-2
       INFO : Check for Environment(Bare Metal or Virtual Machine)
       SUCCESS : Type of environment found : Bare Metal
       INFO : Check number of Controllers
       SUCCESS : Number of ahci controller found : 1
       SUCCESS : Number of External SCSI controllers found : 2
       INFO : Check for Controllers correct PCIe slot address
       SUCCESS : Internal RAID controller :
       SUCCESS : External LSI SAS controller 0 : 3b:00.0
       SUCCESS : External LSI SAS controller 1 : 5e:00.0
       INFO : Check if JBOD powered on
       SUCCESS : 2JBOD : Powered-on
       INFO : Check for correct number of EBODS(2 or 4)
       SUCCESS : EBOD found : 4
       INFO : Check for External Controller 0
       SUCCESS : Cable check for port 0 on controller 0
       SUCCESS : Cable check for port 1 on controller 0
       SUCCESS : Overall Cable check for controller 0
       INFO : Check for External Controller 1
       SUCCESS : Cable check for port 0 on controller 1
       SUCCESS : Cable check for port 1 on controller 1
       SUCCESS : Overall Cable check for controller 1
       INFO : Check for overall status of cable validation on Node0
       SUCCESS : Overall Cable Validation on Node0
       SUCCESS : JBOD0 Nickname set correctly
       SUCCESS : JBOD1 Nickname set correctly

4. Verify the interconnect network:

       # ethtool p1p1
       Settings for p1p1:
       Supported ports: [ FIBRE ]
       Supported link modes: 1000baseT/Full
       Supported pause frame use: Symmetric Receive-only
       Supports auto-negotiation: Yes
       Advertised link modes: 1000baseT/Full
       10000baseT/Full
       Advertised pause frame use: No
       Advertised auto-negotiation: Yes
       Speed: 25000Mb/s <<<<<<<<<<<<<<<<<<<<<<< check speed
       Duplex: Full
       Port: Direct Attach Copper
       PHYAD: 1
       Transceiver: internal
       Auto-negotiation: on
       Current message level: 0x00000000 (0)
       Link detected: yes
       # ethtool p1p2
       Settings for p1p2:
       Supported ports: [ FIBRE ]
       Supported link modes: 1000baseT/Full
       Supported pause frame use: Symmetric Receive-only
       Supports auto-negotiation: Yes
       Advertised link modes: 1000baseT/Full
       10000baseT/Full
       Advertised pause frame use: No
       Advertised auto-negotiation: Yes
       Speed: 25000Mb/s <<<<<<<<<<<<<<<<<<<<<<< check speed
       Duplex: Full
       Port: Direct Attach Copper
       PHYAD: 1
       Transceiver: internal
       Auto-negotiation: on
       Current message level: 0x00000000 (0)
       Link detected: yes

Related Topics

- Deployment Checklist for Oracle Database Appliance Bare Metal Systems

Parent topic: Provisioning Oracle Database Appliance Bare Metal System

### Plumbing the Network

Plumb the Oracle Database Appliance network with the public internet protocol (IP) information assigned to a node, to enable provisioning of the Oracle Database Appliance software.

Important:

On Oracle Database Appliance X9-2, X10, and X11, the `odacli configure-firstnet` command supports bonding of ports across two supported network PCI cards of the same type.

Remember:

To change the network bonding after the system is deployed, run the `cleanup.pl -cleanDefNet` command to ensure that no network setup exists in the bonding interface, and then run the `odacli configure-firstnet` command to configure the new bonding.

Note:

If you enable Link Aggregation Control Protocol (LACP) on the bonding interface when you run the `odacli configure-firstnet` command, then `lacp_rate` is set to 1 (fast). You must adjust the switch setting so that it can support this `lacp_rate`.

1. Connect to Oracle ILOM remote console, then log into Oracle Database Appliance as `root`.
2. Run the command `configure-firstnet` on both nodes. You can choose to enable Link Aggregation Control Protocol (LACP) on the bonding interface when you run `odacli configure-firstnet`.

       # /opt/oracle/dcs/bin/odacli configure-firstnet
       Use bonding on different network interfaces:
           bonding between ports on the same network card [0]
           bonding between Network Card 1 in slot 6 and Network Card 2 in slot 4 [1]
           bonding between Network Card 1 in slot 6 and Network Card 3 in slot 8 [2]
           bonding between Network Card 2 in slot 4 and Network Card 3 in slot 8 [3]
       Please input your selection (0 - 3) [0]:
       Select the Interface to configure the network on (btbond1 btbond3 btbond5) [btbond1]:
       Use LACP bonding on btbond1 (yes/no) [no]:
       Configure DHCP on btbond1 (yes/no) [no]:
       INFO: You have chosen Static configuration
       Use VLAN on btbond1 (yes/no) [no]:

3. Complete the network configuration as prompted and configure the public network interface. Also provide the netmask and gateway IP address.

You use this network connection to transfer the software to the server node.

Example 4-1 Example of a Bonded Configuration

For a bonded configuration, answer `yes` to using a bonding public interface and configure the first network to use a `btbond3` interface without configuring DHCP.

    # /opt/oracle/dcs/bin/odacli configure-firstnet
    Select the Interface to configure the network on (btbond1 btbond3 btbond4) [btbond1]:btbond3
    Use LCAP bonding on btbond3 (yes/no) [no]:yes
    INFO: network interface [btbond3] in LACP mode
    Configure DHCP on btbond3 (yes/no) [no]:
    INFO: You have chosen Static configuration
    Use VLAN on btbond3 (yes/no) [no]:yes
    Configure VLAN on btbond3, input VLAN ID [2 - 4094] 119
    INFO: using network interface btbond3.119
    Enter the IP address to configure : 10.31.129.36
    Enter the Netmask address to configure : 255.255.255.240
    Enter the Gateway address to configure [10.31.129.33] :
    INFO: Restarting the network
    Shutting down interface btbond1: [ OK ]
    Shutting down interface btbond2: [ OK ]
    Shutting down interface p3p1: [ OK ]
    Shutting down interface p3p2: [ OK ]
    Shutting down interface sfpbond1: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface btbond1: Determining if ip address 10.209.13.109 is already in use for device btbond1...
    [ OK ]
    Bringing up interface btbond2: [ OK ]
    Bringing up interface sfpbond1: [ OK ]

Example 4-2 Example of Configuring VLAN

    # /opt/oracle/dcs/bin/odacli configure-firstnet
    Select the Interface to configure the network on (btbond1 btbond3 btbond4) [btbond1]:btbond3
    Use LCAP bonding on btbond3 (yes/no) [no]:yes
    INFO: network interface [btbond3] in LACP mode
    Configure DHCP on btbond3 (yes/no) [no]:
    INFO: You have chosen Static configuration
    Use VLAN on btbond3 (yes/no) [no]:yes
    Configure VLAN on btbond3, input VLAN ID [2 - 4094] 119
    INFO: using network interface btbond3.119
    Enter the IP address to configure : 10.31.129.36
    Enter the Netmask address to configure : 255.255.255.240
    Enter the Gateway address to configure [10.31.129.33] :
    INFO: Restarting the network
    Shutting down interface btbond1:                           [  OK  ]
    Shutting down interface em1:                               [  OK  ]
    Shutting down interface p1p1:                              [  OK  ]
    Shutting down interface p1p2:                              [  OK  ]
    Shutting down loopback interface:                          [  OK  ]
    Bringing up loopback interface:                            [  OK  ]
    Bringing up interface btbond1:
    Determining if ip address 192.0.2.24 is already in use for device btbond1...
                                                               [  OK  ]
    Bringing up interface em1:                                 [  OK  ]
    Bringing up interface p1p1:
    Determining if ip address 192.0.2.24 is already in use for device p1p1...                                                           [  OK  ]
    Bringing up interface p1p2:
    Determining if ip address 192.0.2.24 is already in use for device p1p2...
                                                               [  OK  ]
    Bringing up interface btbond1.122:
    Determining if ip address 192.0.2.24 is already in use for device btbond1.122...
                                                               [  OK
    ...

Configuring LACP after Deployment

Use the `-o` option with the `odacli configure-firstnet` command to enable or disable LACP on a bonding interface.

Enabling LACP on a bonding interface after deployment:

    # odacli configure-firstnet -o
    INFO: Configure network option
    Select the Interface to configure the network on (btbond1 btbond3 btbond5) [btbond1]:btbond3
    Use LACP bonding on btbond3 (yes/no) [no]: yes
    INFO: network interface [btbond3] setup in LACP mode

Disabling LACP on a bonding interface after deployment:

    # odacli configure-firstnet -o
    INFO: Configure network option
    Select the Interface to configure the network on (btbond1 btbond3 btbond5) [btbond1]:btbond3
    Use LACP bonding on btbond3 (yes/no) [yes]: no
    INFO: network interface [btbond3] setup in active-backup mode

Parent topic: Provisioning Oracle Database Appliance Bare Metal System

### Downloading Oracle Database Appliance Software

Download Oracle Database Appliance software and copy to a temporary location before applying updates to your appliance.

1. Download the software files from My Oracle Support to a temporary location on an external client. Refer to the release notes for details about the software for the latest release.
   For example, download the Oracle Database Appliance GI Clone for ODACLI/DCS stack (patch 30403673) and Oracle Database Appliance RDBMS Clone for ODACLI/DCS stack (patch 30403662) for 19.30:

       p30403673_1930000_Linux-x86-64.zip
       p30403662_1930000_Linux-x86-64.zip

2. Unzip the software — it contains README.html and one or more zip files for the patch.

       unzip p30403673_1930000_Linux-x86-64.zip
       unzip p30403662_1930000_Linux-x86-64.zip

   The GI and RDBMS Clone files for release 19.30 are extracted.

       odacli-dcs-19.30.0.0.0-date-GI-19.30.0.0.zip
       odacli-dcs-19.30.0.0.0-date-DB-19.30.0.0.zip

3. Copy the software files from the external client to Oracle Database Appliance. Use the `scp` or `sftp` protocol to copy the bundle.
   Example using `scp` command:

       scp software_file root@oda_host:/tmp

   Example using `sftp` command:

       sftp root@oda_host

   Enter the `root` password, and then copy the file.

       put software_file

   For example, for release 19.30:

       put odacli-dcs-19.30.0.0.0-date-GI-19.30.0.0.zip
       put odacli-dcs-19.30.0.0.0-date-DB-19.30.0.0.zip

The GI and RDBMS Clone files are copied to the temporary location on the appliance. You can update the repository, and create the appliance, as explained in the next topic.

Parent topic: Provisioning Oracle Database Appliance Bare Metal System

### Installing Oracle Database Appliance Software

Install Oracle Database Appliance software, before creating the appliance.

Ensure that the Oracle Database Appliance patches are downloaded and available for updating the repository, as described in the topic Downloading Oracle Database Appliance Software.
Starting with Oracle Database Appliance release 19.12, the sizes of volumes `/u01` and `/opt` are smaller than the corresponding sizes in earlier releases. The size of `/u01` is now 40GB and the size of `/opt` is now 30GB. A new ACFS file system, mounted at `/opt/oracle/oak/pkgrepos/orapkgs/clones`, is created during provisioning. The DATA disk group provides space of 150 GB for the file system. The Oracle Grid Infrastructure and Oracle Database clone files are stored on this file system.

Important:

If you want to install third-party software on your Oracle Database Appliance, then ensure that the software does not impact the Oracle Database Appliance software. The version lock on Oracle Database Appliance RPMs displays a warning if the third-party software tries to override Oracle Database Appliance RPMs. You must restore the affected RPMs before patching Oracle Database Appliance so that patching completes successfully.

Important:

To ensure that your deployment has the latest Oracle Database Appliance firmware, download the latest server patch and update the repository. Then, run the `odacli describe-component` command to check whether the firmware is current or out-of-date. If the firmware is not current, then run the `odacli update-server` and `odacli update-storage` commands before you deploy the Oracle Database Appliance software. If the firmware is current, then you can deploy the Oracle Database Appliance software as described in this topic, without updating the server and storage. Before updating the server or storage, ensure that you run the `odacli create-prepatchreport` command to generate the prechecks report, otherwise an error is displayed.

Note:

Public network gateway must be responsive to ping requests. Oracle Clusterware uses the public network gateway as ping target to facilitate the VIP failover in Oracle Database Appliance high-availability environment.

Note:

Starting with Oracle Database Appliance release 19.27, Oracle ASM Filter Driver (ASMFD) is not automatically configured during provisioning of the appliance. Do not specify the `enableAFD` parameter in the provisioning JSON file.

1. Verify the current system version by running the following command on both nodes:

       [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-component -v

   On a single-node Oracle Database Appliance system, run the command `odacli describe-component` without the `-v` option.

       [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-component

2. Update the repository with Oracle Grid Infrastructure and Database software only. To prevent space issues in `/opt`, it is recommended that you add other repositories after the bare metal instance is provisioned.

       [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/GI_clone_file,/tmp/DB_clone_file

   For example, for release 19.30:

       [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.30.0.0.0-date-DB-19.30.0.0.zip,/tmp/odacli-dcs-19.30.0.0.0-date-GI-19.30.0.0.zip

3. Confirm that the repository update is successful:

       [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID

4. Delete the software zip files from the temporary location on the appliance to save space:

       [root@oda1 opt]# rm software_file
       rm: remove regular file software_file? y

You have now updated the repository with the Oracle Database Appliance software, and can create your appliance, as described in the next topic.

Related Topics

- Deployment Checklist for Oracle Database Appliance Bare Metal Systems

Parent topic: Provisioning Oracle Database Appliance Bare Metal System

### Creating the Appliance

Create the appliance using the Browser User Interface or ODACLI commands.

Note:

If you plan to enable multi-user access, then refer to the chapter Implementing Multi-User Access on Oracle Database Appliance before you create your appliance.

Creating the Appliance using ODACLI Commands

You can use the command `odacli create-appliance` and a JSON file that includes your appliance configuration settings to deploy the appliance instead of using the Browser User Interface. Review the readme in the `/opt/oracle/dcs/sample` directory carefully along with the provided JSON example files. Create a JSON file with the necessary changes based on your environment and requirements.

See Also:

Creating an Appliance Using a JSON File in this guide for example JSON files and the procedure to create a JSON file.

Note:

It is important to review the readme and the examples carefully before creating your JSON file. If you do not enter your network and Oracle ILOM information correctly based on your setup, you will lose network access to both the host and Oracle ILOM.

Creating the Appliance using the Browser User Interface (BUI)

Follow these steps to create the appliance using the BUI:

Ensure that ports 7070 and 7093 on the network between Oracle Database Appliance and the client machine, are open.

1. Open a browser window.
2. Go to the following URL: `https://ODA-host-ip-address:7093/mgmt/index.html`
3. Get the security certificate (or certificate), confirm the security exception, and add an exception.
4. Navigate to the Browser User Interface (BUI). You are prompted to set the password for the `oda-admin` user.

       https://ODA-host-ip-address:7093/mgmt/index.html

5. Log into the BUI with the new password.
   When you launch the Browser User Interface 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.

   Note:

   If you face any issues when logging into the Oracle Database Appliance Browser User Interface, then see the topic Errors When Logging into the Browser User Interface in the chapter Troubleshooting Oracle Database Appliance.
6. Click Create Appliance.
7. In the Create Appliance page, if you want to create the appliance from a saved configuration, click Browse, and select the JSON file. The information from the saved configuration file is loaded. You can retain or edit the fields. Otherwise, manually, provide the values to create the appliance.
8. In the System Information tab, specify the values as follows.
   1. System 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: If there are two disks, then you can select the disk group redundancy as Normal or Flex. To select the the redundancy as High, there must exist more than four disks, and a quorum disk. If five or more disks are configured, then the quorum disk is not required. Select Normal, High, or Flex, as per your deployment requirement.
      The Flex parameter defines the disk group redundancy. Flex redundancy requires at least 3 storage devices, including a quorum. For a database to be placed on Oracle ASM, you can set the database redundancy during its creation. For a database to be placed on Oracle ACFS, the database inherits the redundancy of the ACFS file system. You can specify an ACFS file system redundancy during its creation. You can set the disk group redundancy only during appliance creation. The database redundancy can be set anytime you create the database.
      The redundancy level for DATA, RECO, and FLASH can be set to Normal, Flex, or High based on whether there are two, four, or more disks.

      Note: For Oracle Database Appliance hardware models other than X8-2, the redundancy level for REDO is always High.

   8. Data Storage Percentage: Enter a whole number between 40 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. Disk Group for Database Home Storage: Select the disk group, whether DATA or RECO depending on your hardware model, and specify the size to be allocated. This chooses the disk group from which the ACFS storage required for database homes is allocated.
   10. System Password and Confirm Password: Enter the system password in both fields.
       The system password is the password set for UNIX and `root` users. The password must begin with an alpha character and cannot contain quotation marks. Do not exceed 30 characters.
   11. Specify the DNS Servers and NTP Servers details.
       Starting with Oracle Database Appliance release 19.16, if you specify DNS servers, then ensure that all host names (except SCAN) are resolvable to one and only one IP address through the given domain name and DNS servers. These include Client Access Network Host Name, VIP Name, and ILOM Host Name. This does not apply to SCAN names as they can resolve to multiple IP addresses. If any of the above host names does not resolve to an IP address or resolves to multiple IP addresses, then the the following error is displayed:

           DCS-10045:Validation error encountered: Hostname 'hostname1' does not resolve to a unique IP address.

9. In the Network Information tab, configure the primary client access network, virtual networks, and an Oracle Integrated Lights Out Manager (Oracle 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.
   Specify the following, depending on whether it is a single-node or two-node Oracle Database Appliance deployment:
   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. VIP Name for Node0: Enter the name of the virtual IP network for Node0.
   4. VIP IP Address for Node0: Enter the virtual IP address that resides on Node0 and is shared between the nodes.
   5. VIP Name for Node1: Enter the name of the virtual IP network for Node0.
   6. VIP IP Address for Node1: Enter the virtual IP address that resides on Node1 and is shared between the nodes.
   7. (Optional) ILOM Host Name: Enter the name of the Oracle ILOM host for Node0 and Node1.
   8. (Optional) ILOM Network IP Address: Enter the IP address for the ILOM for Node0 and Node1.
   9. (Optional) ILOM Network Subnet Mask: Enter the subnet mask address for the ILOM.
   10. (Optional) ILOM Network Gateway: Enter the gateway address for the ILOM.
   11. Client Access Network Subnet Mask: Enter the subnet mask address for the primary client access network.
   12. Client Access Network Gateway: Enter the gateway address for the primary client access network.
   13. Client Access Network Interface: Enter the interface for the primary client access network.
   14. SCAN Name: Specify the Single Client Access Name (SCAN).
   15. SCAN IP Address: Specify the SCAN IP address. You can specify up to three SCAN IP addresses.
   Specify the VIP address and SCAN only for high-availability deployments.
10. 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.
    - 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.
11. Do you want to create an initial database? Select Yes and go to Step 9 or select No and go to Step 10.
12. 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.
       For Oracle Database 19c Standard Edition, you can only create single-instance Oracle Database, with or without high-availability.
    8. SYS and PDB Admin User Password: Provide a password for the database.
    9. 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.
       For Standard Edition Oracle Database 19c or later, you can choose to enable high availability for single-instance databases. For Standard Edition Oracle Database 19.6 or later, if you choose to create a single-instance database, then the high availability feature is available by default. To disable high-availability, set the value in the Enable High Availability field to No.
       For Enterprise Edition Oracle Database 19.15 or later or Oracle Database 21.6 or later, you can choose to enable high availability for single-instance databases. For Enterprise Edition Oracle Database 19.15 or later or Oracle Database 21.6 or later, if you choose to create a single-instance database, then the high availability feature is disabled by default. To enable high-availability, set the value in the Enable High Availability field to Yes.
       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.
    10. Shape: Select a database shape from the list.
    11. In the Database Class field, select a database class from the drop-down list. If an option is not available in the list, it is not supported for the database edition on the Oracle Database Appliance or the version that you selected. The default is OLTP.
    12. In the Storage field, select ACFS or ASM from the drop-down list. The default is Oracle ASM.
    13. If you specified the disk group redundancy as Flex, then you can select the Database Redundancy value as Mirror or High.
    14. Data Files on Flash Storage: Select Yes or No.
        This option is only available if the HA system has HDD storage drives.
    15. Configure EM Express: Select Yes or No.
        Select Yes to configure the Oracle Enterprise Manager Database Express (EM Express) console for Oracle Database 12.2.1.0 or 12.1.0.2. Selecting Yes enables you to use the console to manage the database.
    16. Character set: Select a character set.
    17. National Characterset: Select a national characterset.
    18. Language: Select the database language.
    19. Territory: Select a territory or location from the list.
    20. For Oracle Database Enterprise Edition 19c or later, you can choose to enable Transparent Database Encryption (TDE). Select Yes or No in the Enable TDE option. Specify and confirm the TDE Password. By default, the TDE option is disabled.
13. In the Diagnostics Information tab, configure and enable Oracle ASR or choose to enable trace file redaction.
    Enable Trace File Redaction: Select Yes if you want to redact sensitive information in diagnostics collections.

    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 Browser User Interface 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. Select Internal or External in the ASR Type field.
    2. ASR User Name: Enter the e-mail address associated with the My Oracle Support account under which the server is registered.
    3. Password: Enter the password associated with the My Oracle Support account under which the server is registered.
    4. (Optional) Specify the HTTPS Port Number for the ASR manager. The default port number is 16162.
    5. HTTP Proxy used for Upload to ASR: Select Yes or No.
    6. Proxy Server Name: If you are using a proxy for upload, enter the proxy server name.
    7. Proxy Port: If you are using a proxy for upload, enter the proxy port.
    8. (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.
    9. Proxy User Name: If you are using a proxy for upload, enter the proxy user name.
    10. (Optional) Proxy Password: If you are using a proxy for upload and require authentication, enter the proxy password.
14. Click Submit. When prompted, click Yes to confirm that you want to start the job to deploy the appliance.
15. Verify that the appliance is deployed. Run the `odacli describe-system` command. For high-availability deployments, run the command on both nodes.

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 system password. The `oracle` and `grid` passwords are set to the default password. Change these passwords to comply with your user security protocols.

Related Topics

- Errors When Logging into the Browser User Interface
- Deployment Checklist for Oracle Database Appliance Bare Metal Systems
- Reimaging an Oracle Database Appliance Baremetal System

Implementing Multi-User Access on Oracle Database Appliance
odacli Multi-User Access Commands

Parent topic: Provisioning Oracle Database Appliance Bare Metal System

### Managing Local Volumes

Understand how you can modify the size of logical volumes `LOGVOLOPT` and `LOGVOLU01`.

About Local Volumes

During imaging, Oracle Database Appliance creates a RAID1 volume between the two operating system disk. On all systems with Oracle Linux 8 and later, two small partitions are created on this RAID1 volume to support Unified Extensible Firmware Interface (UEFI). The rest of the disk space is assigned to a third partition. A physical volume is initialized on this third partition which is fully assigned to a volume group `VolGroupSys`. Several logical volumes namely `LogVolRoot`, `LogVolU01`, `LogVolOPT`, and `LogVolSwap` are created in `VolGroupSys`. On single-node Oracle Database Appliance systems, two more logical volumes, `LogVolRECO` and `LogVolDATA`, each of 1 GB in size are also created. Oracle Database Appliance formats `LogVolRoot`, `LogVolU01`, and `LogVolOPT` as `ext4` (fourth extended file system), and mounts them at `/`, `/u01`, and `/opt` respectively. These logical volumes use only a part of the available storage, approximately 125 GB.

Note:

The term Local Volume refers to the logical volume and the physical volumes initialized on the operating system disk.
The local volumes `LOGVOLOPT` and `LOGVOLU01` may not have sufficient space for creating Oracle Grid Infrastructure homes, installing additional software, creating Oracle Grid Infrastructure log files, and others. In such cases, extending the size of these local volumes is useful.

Note:

After extension, the size of local volumes cannot be reduced through Oracle Database Appliance tooling. Ensure that you carefully plan local volume extensions.

Viewing and Extending the Local Volume Size Using ODACLI Commands

Run the following command to view all the local volumes:

    odacli list-localvolumes

The command displays the total size of the physical volume, the free space available in the volume group, and the space required to support ODABR backup during patching. It also displays the space available for extending the local volumes in a safe manner such that sufficient buffer is reserved for ODABR backup. In addition, it shows the details of all the local volumes in the system.

To modify the local volume size, run the following command:

    odacli extend-localvolume --name volume_name --increment-size increment_size_in_GB --force

The command enables extension of `LogVolU01` and `LogVolOPT` only. It allows extension up to the size showed by the `Space for extension` field in the `odacli list-localvolumes` output.

Viewing and Extending the Local Volume Size Using BUI

Follow these steps:

1. Navigate to the Browser User Interface. You are prompted to set the password for the `oda-admin` user.

       https://ODA-host-ip-address:7093/mgmt/index.html

2. In the Appliance home page, click the Local Volumes link on the left-hand pane.
3. In the Local Volumes Details page, you can view the physical volume and logical volume details. For high-availability system, you can view these details for both nodes.
4. To increase the local volumes `LOGVOLOPT` and `LOGVOLU01` sizes, click Extend. Confirm your action in the popup window.
5. In the Extend Local Volume page, select the Volume Name, and specify the Increment Size in GB. Click Force Run to override the ODABR backup space requirement. You can extend both `LOGVOLOPT` and `LOGVOLU01` volumes.
6. Confirm the operation and submit the job. Track the status of the job completion and verify that it completes successfully.

Parent topic: Provisioning Oracle Database Appliance Bare Metal System