Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATA Note: OneCommand is constantly changing to improve the installation process and to support additional bundlepatches. The number of steps and what they do is very likely to change with each version of Exadata. So be sureto review the README file for instructions on how to run OneCommand on your system before you begin.There are number of ways Deploy112 may be used. For example, the following command-lineoptions process all 31 steps of the installation process, only stopping if a step failes:[root@exadb01 onecommand]# ./deploy112.sh -i -r 0-30Each step must complete successfully before you can proceed to the next. Oracle recommendsrunning the steps one at a time, reviewing the output at the end of each before proceeding on to thenext. Deploy112 provides this capability with the -s command line option. For example, the installationprocedure would look something like the following:[root@exadb01 onecommand]# ./deploy112.sh -i -s 0Check output for errors…[root@exadb01 onecommand]# ./deploy112.sh -i -s 1Check output for errors…[root@exadb01 onecommand]# ./deploy112.sh -i -s 2Check output for errors…[root@exadb01 onecommand]# ./deploy112.sh -i -s 3and so on…Deploy112 takes as input the parameters from the files you generated earlier using the DBMConfigurator. Log files are created each time Deploy112 is called to execute a configuration step, and forsome steps, it dynamically generates and executes a shell script that carries out all the tasks required.Reviewing these files can be very useful in determining why a step failed. The log files and dynamicallygenerated shell scripts are stored in the onecommand/tmp directory.The output generated by the various installation steps varies quite a bit. But in general, Deploy112displays some header information telling you what step it is running, where to find the log file, andwhether it completed successfully. For example, the following output was generated by running step 1on the quarter rack system in our lab:Script started, file is /opt/oracle.SupportTools/onecommand/tmp/STEP-1-exadb01-20110513110841.log=========== 1 SetupSSHForRoot Begin ===============Setting up ssh for root on ALL nodes....Checking nodes in /opt/oracle.SupportTools/onecommand/all_group......INFO: We're running... /opt/oracle.SupportTools/onecommand/setssh-Linux.sh -s -c Y -h/opt/oracle.SupportTools/onecommand/all_group -p welcome1 -n N -x...................................setssh-Linux.sh Done.SUCCESS: Running SetSSH completed successfully...Return Status: 0 Step# 1exadb01: Fri May 13 11:09:50 CDT 2011exadb02: Fri May 13 11:09:50 CDT 2011267