Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATAIn addition to the files listed in this table, OneCommand also creates a database template(dbmDBTemplate) used for creating your starter database. The template contains database parameters thatshould be used whenever creating databases on Exadata, such as these:_file_size_increase_increment_kill_diagnostics_timeout_lm_rcvr_hang_allow_timeThe template file, dbmDBTemplate.dbt, is installed in the $ORACLE_HOME/assistants/dbca/templatesdirectory during the OneCommand installation process.Step 4: CheckIP (checkip.sh)One of the files the DBM Configurator generates is a shell script used to validate your network settings.The checkip.sh (CheckIP) script reads your network configuration settings from its parameter file(dbm.dat, also generated by the Configurator) and runs a variety of tests to verify network readinessbefore, during, and after the configuration process. CheckIP tests the network to confirm that thefollowing conditions are met:• IP addresses that should respond to a ping, do.• IP addresses that should not respond to a ping, do not.• Host names that must be registered in DNS can be both forward and reverseresolved using the first DNS server specified in the dbm.dat file.Before running OneCommand, the checkip.sh script (CheckIP) should be run to validate thereadiness of your corporate network. The script has several modes of operation that validate yournetwork configuration at various points of the configuration process. At this point, you should runCheckIP in pre_applyconfig mode from a server, external to Exadata platform. The server you choose torun CheckIP from must have the same network visibility as your Exadata system will have. For example,the server must have access to the same DNS server and NTP server, and it must be able to ping the IPaddresses you listed in your network settings for Exadata. Ideally, the server you choose should run theLinux operating system, but Unix servers may work as well. CheckIP uses the Bash shell, which ispopular on the Linux platform but also available on most versions of Unix. The O/S commands requiredby CheckIP include host, ping, ntpdate, tr, cut, sed, wc, grep, and head. Be aware that even if thesecommands are available on your Unix server, they may produce incompatible output and cause falsefailures in the output. The checkip.sh script and the dbm.dat parameter file are created in Linux/Unixformat, so when you upload them from your laptop, be sure to transfer them in binary mode. If you wantto be sure, you can use the dos2unix command after uploading them to ensure that the format is correctbefore executing the script. Upload the checkip.sh and dbm.dat files to a server on your network and runthe following command as the root user:./checkip.sh -m pre_applyconfigCheckIP will print its progress out to the screen as well as build a dbm.out report file. The following listingshows sample output from the CheckIP script:Running in mode pre_applyconfigUsing name server 192.168.10.15 found in dbm.dat for all DNS lookupsProcessing section #Processing sectionProcessing section DOMAIN258