Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATAdecide to merge these servers into your old cluster, you won’t have to makechanges to the host names. For example, our quarter rack configuration haddatabase host names of enkdb01 and enkdb02. Adding the new servers continuedwith the names enkdb03, and enkdb04. Likewise, the storage cell host namescontinued with enkcel04 through enkcel07.Client Access SCAN Name: This procedure will be creating a new RAC cluster,so you will need a new SCAN name for it. You will also need to see that it and allof the other new host names are properly registered in your company’s DNSserver (just as you did when your existing Exadata system was installed).Country Code / Time Zone: Of course, these settings should match yourexisting Exadata system.NTP and DNS Servers: These should also match your existing Exadataenvironment.Oracle Database Machine Model: This setting determines how many computenodes and storage cells the Configurator will use when creating host names andIP addresses. You will want to set this to X2-2 Quarter Rack, since it is theclosest choice to what you are actually configuring. Remember, though, thatupgrading from a quarter to half rack adds four storage cells, not three.Oracle Exadata Storage Server Nodes: You will need to adjust this number toreflect the actual number of storage cells in the upgrade. The default number ofstorage cells in a quarter rack configuration is 3. But since you are upgrading toa half rack, you will need to set this to 4.Network IP Addresses: You should continue to use the networks youconfigured for the Exadata rack you are upgrading. As you enter the starting IPaddresses for hosts in the DBM Configurator, take care that you are not creatingany address conflicts with existing hardware on your network.O/S User & Group Accounts: It is not required, but you should use the sameuser/group names and user/group IDs when configuring your new cluster. Thisis especially true if there is any chance these user accounts will ever interactbetween the new system and the old system. OneCommand will not establishuser equivalency between the old and new servers for you. So that must bedone manually after the upgrade is complete.When you are finished entering your settings, click the Generate button on the right side of thespreadsheet. This creates a network topology report below the data entry area of the spreadsheet. Thisreport area of the spreadsheet is a place where you can manually override some of the settings generatedin the data entry area of the spreadsheet. You will need to scroll down and adjust a few settings in thisarea before you are ready to create your parameter files and upload them to Exadata. You will notice thatthe topology report shows incorrect host names for the compute nodes and storage cells. Of course, thisis because the DBM Configurator assumes this is a new configuration, not an upgrade. The host namesfor the compute nodes are postfixed with 01–02, and the storage cells are postfixed with 01–03. Make thenecessary changes to the host names in the report, so they reflect compute node names of 03–04 andstorage cell host names of 04–07. Once you’ve made all the necessary changes, click the Create ConfigFiles button to generate your parameter and deployment files. Take a few minutes to review contents ofthe files to be sure they are correct before you upload them to the /opt/oracle.SupportTools/onecommanddirectory of the first new compute node, {machine_name}db03.269