Configuring Oracle Exadata Database Machine Using OEDA

6.16.1 Configuring Oracle Exadata Database Machine Using OEDA

Use Oracle Exadata Deployment Assistant (OEDA) to configure your engineered system.

The deployment phase of OEDA can be performed on one of the database servers of your new Oracle Exadata or any other host that is connected to the same network as the new engineered system rack. Do not run install.sh from a storage server. If you plan to run OEDA on a host outside of the new rack, then create the OEDA home directory and Workdir, as described below, on the host machine instead.

Note:

OEDA configures all Exadata components, including the database servers (with or without virtualization), storage servers, and the RDMA Network Fabric. For successful configuration, OEDA requires access to:

The client and administration network interfaces on the database servers, including the VM server host and the VM guests where applicable.
The administration network interfaces on the storage servers.
The administration network interfaces on the RDMA Network Fabric switches.

Ensure that you run the OEDA deployment phase on a host with access to all of the required network interfaces.

Note:

Running OEDA from a client machine outside of the rack means the software image files are transferred over the network, causing the process to be slower.

Note:

For this procedure, Oracle VM refers to OVM and KVM. Starting with Oracle Exadata Database Machine X8M-2, Oracle Linux KVM is the virtualization technology for systems that use RoCE Network Fabric. Otherwise, Oracle VM is a Xen-based virtualization technology, which is used across Oracle Exadata Database Machine systems that use InfiniBand Network Fabric.

You must have completed the other tasks described in Overview of Oracle Exadata Deployment Assistant before starting this task.

If you are installing Oracle VMs on the database servers, then run /opt/oracle.SupportTools/switch_to_ovm.sh on each database server.
Disk space for unused system partitions must be reclaimed before installing software on all database servers with InfiniBand Network Fabric. Use the following command to reclaim the disk space: /opt/oracle.SupportTools/reclaimdisks.sh -free -reclaim. This command is not required on RoCE-based Exadata database servers.
Create a directory for the extracted OEDA files on the host where you will run install.sh.
OEDA will not run if staged on the root file system (/)of any database server. Create a directory to store the latest version of OEDA and all required files on a file system that has at least 30 GB of available free space.
- For bare-metal database servers, create a directory on the /u01 file system, for example /u01/onecommand or /u01/oeda.
- For Oracle VM servers, create a directory on the /EXAVMIMAGES file system.
Download the latest version of OEDA for the operating system of the client or server where you will run install.sh.
Unzip the downloaded file into the OEDA home directory you created. This will create a directory like /u01/onecommand/linux-x64. This directory is referred to as the OEDA home directory.
Download the required image files for the Oracle software.
OEDA requires patches available from My Oracle Support or Oracle Software Delivery Cloud ( https://edelivery.oracle.com). Review the README file for OEDA to determine the file name or patch number, which is based on the version of Oracle software being installed. Place the files in the WorkDir sub-directory in the OEDA home directory.
- If you are installing on a bare-metal database server, then download the patches, as specified in Section 2 of the OEDA README file. After downloading the patch ZIP file, extract the contents into the WorkDir sub-directory.
- If you are configuring Oracle VM on the database servers, then download the gold image files as indicated in the topic "Oracle Exadata Deployment Assistant Support for Oracle Virtual Machines" in the OEDA README file. After downloading the gold image ZIP files, extract the contents into the WorkDir sub-directory.
  
  A gold image is a copy of a software-only, installed Oracle home. It is used to copy an image of an Oracle home to a new host on a new file system to serve as an active, usable Oracle home.
Copy the required OEDA configuration files to the WorkDir sub-directory on the database server or Oracle VM.

When you used OEDA to specify the configuration details for your new engineered system, it created several configuration files and a ZIP file that contains all the generated files. The required files are also listed at the bottom of the InstallationTemplate.html file that was generated by OEDA. You can copy the ZIP file and extract it into the WorkDir sub-directory, or copy the required files directly into the WorkDir sub-directory.
Log in to the database server or Oracle VM and go to the OEDA home directory.
Run the install.sh script to install and deploy the software on your new engineered system.
In the following command syntax, configuration_file is the full path name for the main configuration file, CustomerName-rackname.xml
```
# ./install.sh -cf configuration_file [-s step_number |  \
    -r step_numberA stepnumberB]
```
You can use the following options with the install.sh script:
- -cf file: Configuration file name
- -h: Help output for the script
- -l: List the steps of OEDA
- -r {n-N | n }: Run steps n through N of OEDA, or run the specified step.
- -s n: Run step n of OEDA.
- -u {n-N | n }: Undo steps n through N, or one step.

Note:

Always use the latest OEDA patch listed in My Oracle Support note 888828.1. Refer to the README in the patch for the latest steps.

The following steps are performed by the OEDA deployment script. However, the actual steps for a specific deployment may differ depending on the deployment options chosen. For example, the "Update Nodes for Eighth Rack" step is performed only if you are deploying an Eighth Rack configuration.

1. Validate Configuration File
2. Update Nodes for Eighth Rack
3. Create Virtual Machine
4. Create Users
5. Setup Cell Connectivity
6. Create Cell Disks
7. Create Grid Disks
8. Configure Alerting
9. Install Cluster Software
10. Initialize Cluster Software
11. Install Database Software
12. Relink Database with RDS
13. Create ASM Diskgroups
14. Create Databases
15. Apply Security Fixes
16. Install Exachk
17. Setup ASR Alerting
18. Create Installation Summary
19. Resecure Machine