3.1 Overview of Oracle Exadata Deployment Assistant

Use Oracle Exadata Deployment Assistant (OEDA) to specify the system configuration details and drive the system configuration processes.

OEDA provides a graphical user interface to gather your configuration details and create the Oracle Exadata Rack configuration file. The configuration file drives the automated installation and configuration processes for Oracle Exadata Rack.

Note:

For ease of reading, Oracle Exadata Rack is used when information refers to both Oracle Exadata and Oracle Exadata Storage Expansion Rack.

You can also use the OEDA command-line interface (OEDACLI) to perform Oracle Exadata Rack life-cycle management tasks.

You can download the latest version of OEDA from Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1). OEDA is also available on Oracle Technology Network.

In addition to Oracle Exadata Rack, OEDA is also used for Oracle Zero Data Loss Recovery Appliance and Oracle SuperCluster.

Oracle Exadata System Software release 19.1.0 introduced the Web-based interface for OEDA, which replaces the previous Java-based user interface as the graphical user interface for configuring Oracle Exadata Rack.

The following outlines how OEDA is used during the implementation of Oracle Exadata Rack:

• Before your engineered system arrives, do the following:
  1. Work with your network and database administrators to evaluate the current network settings, such as current IP address use and network configuration. OEDA supports IPv6 addresses.
  2. Define the settings for the rack, such as network configuration and backup method.
  3. Download the latest version of OEDA from Oracle Technology Network.
  4. Unzip and run the configuration script on a supported platform, and select the type of system to configure.
  5. Go through every page in OEDA and supply values for all required fields. You cannot advance to the next page if you do not supply all of the required values. You must provide naming details and DNS, NTP, and networking details.

  6. At the end of the dialogue with OEDA, configuration files are generated on the client. The files are also listed at the bottom of the InstallationTemplate.html file that is generated by OEDA. Depending on your engineered system and configuration, OEDA generates all or some of the following files:

     • databasemachine.xml
     • CustomerName-rackname.xml
     • CustomerName-rackname-preconf_GUID.csv
     • CustomerName-rackname-InstallationTemplate.html
     • CustomerName-rackname-platinum.csv
     • CustomerName-rackname-checkip.sh
     • CustomerName-rackname.zip
     • pkey_GUID.csv and pkey_racknamehostname_GUID.csv — if you enabled InfiniBand partitioning for your virtual environments

     The CustomerName-hostname.zip file contains all the generated files.

  7. Review the InstallationTemplate.html file to check the entire configuration and verify all information was entered correctly.
• Shortly before your engineered system arrives, or is scheduled to be configured, validate the network configuration, as directed by Oracle. See Verifying the Network Configuration Prior to Configuring the Rack.
• After your engineered system arrives, the configuration files are copied to a database server, and the validation and installation is completed. See Configuring Oracle Exadata Database Machine Using OEDA.

• Considerations and Requirement for Using OEDA
  Review this information before using Oracle Exadata Deployment Assistant (OEDA).