Run the Java OneCommand

Language:

Caution - Ensure that you backup all existing databases before running the Java OneCommand.

Caution - You must use the latest version of OEDA and the Java OneCommand patch (patch 19766190 or later). Refer to the Oracle Exadata Deployment Assistant (OEDA) section in MOS Note 888828.1 for details.

Caution - Any version of Java OneCommand prior to patch 19766190 can destroy the storage cell disks and griddisk if an undo option is performed on certain steps (Create Cell disk, for example). This can cause complete destruction of all the griddisks on the storage cells. In addition, re-running the griddisk creation step or mistakenly specifying a non-unique diskgroup in OEDA will result in the destruction of existing griddisks. Be aware that older versions of Java OneCommand also destroy cell disks and griddisks with the Create Cell Disks step.

Locate the configuration files for the new clusters that were generated at the end of the OEDA process when you added zones to the Database Domains.
The configuration files for the new clusters that you created should be named customer-name-name-prefix-cluster-clucluster-number.xml.

For example, using the example configuration, the two new cluster files that were created at the end of the OEDA process as described in Creating Configuration Files Using OEDA would be:
- Acme-osc01-cluster-clu6.xml
- Acme-osc01-cluster-clu7.xml

Using the first new cluster configuration file, display the list of functions that will be performed by the Java OneCommand:

./install.sh -cf /path-to-config-file/customer-name.name-prefix.xml -l

For example:

./install.sh -cf /path-to-config-file/Acme-osc01-cluster-clu6.xml -l

Information similar to the following is displayed:

1. Validate Configuration File
2. Setup Required Files
3. Create Users
4. Setup Cell Connectivity
5. Verify IB and Calibrate Cells
6. Create Cell Disks
7. Create Grid Disks
8. Install Cluster Software
9. Initialize Cluster Software
10. Install Database Software
11. Relink Database with RDS
12. Create ASM Diskgroups
13. Create Databases
14. Apply Security Fixes
15. Create Installation Summary
16. Resecure Machine

The output that you see and the number assigned to each step in the output varies depending on the configuration choices you made in OEDA.

Note the specific steps that you will not run in Java OneCommand.
In the next step, you will run the appropriate steps in Java OneCommand. Do not run any of the following steps in Java OneCommand in the next step:
- Verify IB and calibrate cells (step 5 in the example output above)
- Create cell disks (step 6 in the example output above)
- Configure cell alerting (not shown in the example output above)

Run the appropriate steps in the Java OneCommand, using the cluster configuration file that was generated at the end of the OEDA process as input:
```
./install.sh -cf customer-name.name-prefix.xml -s step-number
```
where step-number is the number of each step that you are running, in order. For example:
```
./install.sh -cf Acme-osc01-cluster-clu6.xml -s 1
```
Run all of the steps in the Java OneCommand except for the following:
- Verify IB and calibrate cells
- Create cell disks
- Configure cell alerting
You can also run a series of steps by using the -r option. For example, if you wanted to run steps 1 through 5, enter the following:
```
./install.sh -cf Acme-osc01-cluster-clu6.xml -r 1-5
```
You can destroy a zone from a Database Domain using the instructions in Delete a Template Zone From a Database Domain if necessary (for example, if Java OneCommand fails at step 2 for some reason). However, use caution when destroying zones from a Database Domain.

Repeat Step 2 through Step 4 for each new cluster configuration file that you generated at the end of the OEDA process.

Create additional links on the IB storage network for the zones that you set up on the Database Domains.
Go to Creating Additional Links on the IB Storage Network for Zones.