Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATAregister new network names with the domain name server. It’s important to understand how theseconfiguration settings are used, so we’ll spend a substantial amount of time discussing them in “Step 1:The Configuration Worksheet.”Once you have completed the configuration worksheet, you will transfer that information to theDBM Configurator (dbm_configurator.xls). This is an Excel spreadsheet that generates all the parameterand deployment files OneCommand needs for configuring your system. In addition to parameter anddeployment files, the DBM Configurator generates the checkip.sh script you should use to verify yournetwork settings. This script validates the format of the IP addresses you entered, checks to see if any ofthem are already in use, and verifies that the network names you specified can be resolved by your DNSserver. Once this is done, you are ready to upload these files to Exadata.Before running OneCommand, you will need to stage the installation media for the GridInfrastructure and the database (including any Oracle-prescribed patches). The final step of the processis to execute OneCommand. Its operation consists of multiple steps that configure all the components ofyour Exadata Database Machine. The top-level script that runs OneCommand is called deploy112.sh(112 presumably stands for 11gR2). This script can be run end-to-end, executing all of the stepsautomatically, or you may specify a step to run using command-line options. We strongly recommendrunning these steps one at a time. Doing so makes it much easier to troubleshoot if a step fails tocomplete successfully. Note: Rather than create an Exadata-specific release of their Grid Infrastructure, ASM, and RDBMS products,Oracle chose to integrate the Exadata specific code right into the same 11gR2 product you would install on non-Exadata platforms. When they did this, Oracle provided a mechanism for releasing Exadata-specific patches thatcould be managed separately from the mainstream product and coined a new term, bundle patches. Bundlepatches are Oracle’s way of tracking and distributing fixes for their storage cell software as well as Exadataspecificfixes for the Grid Infrastructure, ASM, and database software.When you take delivery of your Exadata Database Machine, certain tasks will he completed by anOracle hardware technician. These tasks include connecting all the networked components inside theExadata rack and configuring IP addresses for the private network (IB switch). When this process iscomplete, all compute nodes and storage cells will be connected together through the IB switch.OneCommand is only run from the first compute node and uses the private network to executeconfiguration commands on other servers and storage cells, as well as to install the Grid Infrastructureand RDBMS software on all database servers. There is no place in the configuration worksheet or theDBM Configurator to specify the network address, and the default is 192.168.10. If this network addressis already in use elsewhere in your network infrastructure, this may create routing problems later. Besure to mention this to your Oracle delivery coordinator early in the process so they can negotiate anappropriate network address for your InfiniBand network.Configuring ExadataThe first step in configuring Exadata is generally to work through the configuration worksheet. If you arecomfortable with the process, you can opt out of step 1 and enter your parameters directly into the DBMConfigurator as you gather them. But don’t underestimate the value of the configuration worksheet. It isan integral part of the process Oracle uses; and for good reason. Even experienced Exadata technicians241