Exadata-- Initial Deployment , OEDA and checkip script

In these days, we are migrating several EBS instances to Exadata.

We (as Apps and Core DBAs) are involved in these works, from deployment to the end.

We are not cabling the Exadata but, we are usually there to check and to give the inputs.

In Exadata implementations and migration projects, everyting starts with the initial deployment.

I mean the deployment of Exadata.
The deployment of Exadata is usually straight forward and the process we follow during the deployment, make us feel pretty professional.

There are two tools that we use for the initial deployment of Exadata.

The first one is "OEDA"( Oracle Exadata Deployment Assistant) and the second one is the "checkip script" that is generated by OEDA.

Using OEDA, we sent Oracle almost all the inputs that are needed for the deployment.
Things like, our scan name, our IP addresses,  our DNS IPs, ASM diskgroup names and everything...
OEDA replaces the manual configuration forms that we used in the past for deploying the older versions of Exadata.

OEDA is a tool that can be used even in our Windows clients.
It is an easy to use tool, which is fully documented Oracle Exadata Database Machine Installation and Configuration Guide (https://docs.oracle.com/cd/E80920_01/DBMIN/exadata-deployment-assistant.htm)

After giving all the necessary inputs, OEDA create the configuration files which will be used by the Oracle Field engineer during the deployment..

All the configuration files are created under the folder named "ExadataConfigurations".

After we run OEDA, we continue with executing the checkip script.

checkip script can be found in the ExadataConfigurations folder that is created by the OEDA during its run.

Checkip is the tool for ensuring all the ips that are given while running OEDA, are available and all the DNS entries and relevant stuff like that are already configured in the client/customer environment. (checkip script can be run on windows as well..)

Note that, checkip uses the JRE which is deployed by OEDA!. So , if you are planning to execute the checkip script directly from the machine where you also executed OEDA, then this is not a problem.
But if you are planning to execute the checkip script from another machine, then you need to download OEDA to that machine also.. (as the JRE, that checkip is designed to use, comes with OEDA)

The following DNS entries must be configured before running the tool;

DNS entry for Management/Admin network
DNS entry for ILOM Network
DNS entry for  Public/Client network
DNS entry for  VIP network
DNS entry for  SCAN IPs

So, it is like the tool to crosscheck the inputs that are given in OEDA.

checkip script produces an output file when we execute it.

In this output file we need to see the prefix, named GOOD for every check and we need to see the successful message at the end of that output file;

SUCCESS: 

 Successfully completed execution of step Validate Configuration File [elapsed Time [Elapsed = 95573 mS [1.0 minutes] Tue Jul 04 09:51:26 EEST 2017]]

At the end of the day, we sent the output of checkip script and the template files that are created under the ExadataConfigurations folder, to Oracle and wait for the deployment date.

So, in summary; there are 3+1 steps:

1. Customer should fill OEDA configuration.

2. Customer to run checkip script, generated by OEDA utility.

3. Customer to send Oracle the OEDA configuration files and checkip script output for validation.

4. Once configuration files has been validated and checkip script found to be ready, Oracle will be able to schedule HW and SW engineers visits. (this is done by Oracle)

One more thing;

In addition to the outputs of these 2 tools, there is one more file that is sent to Oracle for Exadata deployment. It is named as Exadata Logistic template deployment form, and it is usually filled easily.

In Exadata Logistic template deployment form, we send the information like the company name, work location, dress code, closest hotel, Vpn access(if available) and the necessary contacts to Oracle.

Well.. This is all we need to do as customer site dbas and consultants for the initial deployment of Exadata.

The real excitement, however; begins once the machine is deployed.

Once this instrument(Exadata) is deployed, we need to play it, we need to play it well. 

(The important thing is not the words, but the actions :) )