10.07.2015 Views

Expert Oracle Exadata - Parent Directory

Expert Oracle Exadata - Parent Directory

Expert Oracle Exadata - Parent Directory

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 8 CONFIGURING EXADATA• /etc/oracle/cell/network-config/cellinit.oraThe cellinit.ora file should be updated with the privateInfiniBand IP address of the compute node where the file isinstalled. Each compute node will have a unique version of thisfile.7. Update the /etc/hosts file with the contents of the priv_ib_group filegenerated from DBM Configurator. Use the hosts file on one of your othercompute nodes as a guide. It is very important not to remove comments suchas the following:#### BEGIN Generated by <strong>Exadata</strong>. DO NOT MODIFY ####8. Update the /opt/oracle.SupportTools/onecommand/*.group files on allcompute nodes, adding the nodes to the configuration.9. Create the O/S users and groups as they are defined on the other computenodes. The finger command may be used to compare user account definitionsas follows.10. Set up SSH user equivalency between the new and old compute nodes for the<strong>Oracle</strong> software owner.11. Follow the steps in the Owner’s Guide for cloning the Grid Infrastructure anddatabase homes to a replacement server. That section of the Owner’s Guide isdiscussing the replacement of a failed database server. Of course you will notbe replacing a server so you can skip over any steps having to do withremoving a failed server from the cluster. Note: The <strong>Exadata</strong> platform consists of multiple software and hardware components that require periodicupdates. These updates come in three forms: Storage Server patches, Database Server patches (bundle patches),and InfiniBand Switch updates. Considering the complexity of <strong>Exadata</strong>, it is more important than ever to keep yoursystem fairly current with the latest software and firmware patches. A word of caution though, we recommend thatyou wait at least a month after a patch is available before installing it on a production system. Even for test anddevelopment systems, we recommend you wait at least 2–3 weeks after a patch is available before installing it.<strong>Oracle</strong> maintains a document on My <strong>Oracle</strong> Support (MOS) containing a list of all supported software and patchesavailable for <strong>Exadata</strong>, starting with version 11.2. The document is continually updated with useful information,instructions and links to the latest patches as they become available. The document is MOS note 888828.1“Database Machine and <strong>Exadata</strong> Storage Server Release 2 (11.2) Supported Versions”. See Appendix B for a list ofother useful MOS notes relating to the <strong>Exadata</strong> platform.271

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!