Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATAFieldData Diskgroup NameReco Diskgroup NameDescriptionThe name for the ASM DATA disk group is generatedautomatically in the form: DATA_{machine_name}. The defaultname can be changed here, as needed, before generating yourparameter files.The name for the ASM RECO disk group is generatedautomatically in the form: RECO_{machine_name}. The defaultname can be changed here, before generating your parameterfiles.The DBM Configurator process is as follows:1. Enter the configuration parameters from the configuration worksheet into theDBM Configurator.2. Click the Generate button on the right side of the spreadsheet. A brief reportshowing the topology of your system is generated at the bottom of thespreadsheet. Scroll down to review your settings and make corrections to theoutput as needed. When you are finished making changes, you are ready tocreate the output files.3. The last step is to click the Create Config Files button. This generates theparameter and deployment files used by OneCommand. It also creates aninstallation template in a separate spreadsheet tab in the Configurator. Theinformation in the template consists mostly of the input parameters youprovided in an easy-to-read format. Review the template carefully and makechanges in the data entry or topology report areas as needed. If you must goback and make any changes, you should click the Generate and Create ConfigFiles buttons again so that your changes are written to the output files. Caution: Be careful when filling out the spreadsheet. It’s very easy for a typo to slip through and cause youproblems later. The topology report generated below the data entry fields is useful for catching errors in the hostnames and IP addresses you entered. This report is created when you click the Generate button.Step 3: Upload Parameter and Deployment FilesThe DBM Configurator generates a number of files that will be used to configure your Exadata DatabaseMachine. These files are saved in the C:\dbmachine_{company_name}\{machine_name} directory. The filesare primarily used by OneCommand to perform the installation and configuration process. But a few ofthe files are used by other processes. For example, the checkip.sh script uses the dbm.dat file to performnetwork readiness tests prior to running OneCommand. These files will be needed for various tasksgoing forward in the configuration, and they must be uploaded to the first compute node on yourExadata platform.254