Aix 7.1 Gpfs.base Download

  

Fix versions and fileset release for GPFS File Manager. Fix versions and fileset release for GPFS File Manager.

Oracle Real Application Clusters (RAC) provides software for creating a cluster in Oracle. This tutorial explains how to configure Oracle RAC using GPFS 3.5 and covers the concepts, pre-requisites, and hardware and software configuration along with screen captures. We divide this tutorial into five steps. • • • • • We will use three logical partitions (LPARs): zag02, zag03, and zag04 for this setup. Part 1: System preparation • File set installation: After IBM AIX® (we are using AIX 7.1) is installed on the nodes, install the following file sets on all three LPARs. File set installation File sets Functionality Dsm.core Dsm.dsh This is required for distributed shell (dsh) to work fine.

Openssh.base.client openssh.base.server openssl.base openssl.man.en_US openssh.base.client openssh.base.server openssl.base This is required for Secure Shell (SSH) to work fine. Vnc-3.3.3r2-5.aix5.1.ppc.rpm This is required for opening a vnc session to the nodes. Rsct.basic.rte rsct.compat.clients.rte bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat bos.perf.proctools Other required file sets.

After the file sets are installed, start configuring the systems. • Ensure that the dsh between the systems is working fine. Distributed shell (dsh) is used to facilitate the running of commands on all the cluster nodes. For dsh to work, you only need to install the dsm file set on the node you want to run the command, typically the first cluster node.

Gpfs.base

You might not necessarily install it on the rest of the nodes. Perform the following steps: # cat /.wcoll Zag02 Zag03 Zag03 # echo 'export WCOLL=/.wcoll >>/.profile' # export WCOLL=/.wcoll Test the dsh functionality using the date command. # dsh date Zag02: Mon Dec 9 02:28:14 CST 2013 Zag03: Mon Dec 9 02:28:14 CST 2013 Zag04: Mon Dec 9 02:28:14 CST 2013 • Ensure that the remote shell (rsh) between the nodes is working fine.

Oracle uses rsh and rcp to copy files from one node to the other. # dsh 'echo '+ +' >/.rhosts' # dsh chmod 600 /.rhosts • Ensure that SSH is working fine between the nodes. Log on to each node to generate a public key file (id_rsa.pub): Write the Oracle user authorized keys of node2 and node3 into the local node Oracle user's authorized key. As an Oracle user, run the following commands: # ssh-keygen –t rsa As root user, run # ssh-keygen –t rsa On the first node (zag02): Write the root user's public key to the root user and the Oracle user's authorized keys. # dsh cat /.ssh/id_rsa.pub >>/.ssh/authorized_keys # dsh cat /.ssh/id_rsa.pub >>~oracle/.ssh/authorized_keys # dsh cat ~oracle/.ssh/id_rsa.pub >>/.ssh/authorized_keys # dsh cat ~oracle/.ssh/id_rsa.pub >>~oracle/.ssh/authorized_keys Write the root user authorized keys of node2 and node3 into the local node's root user's authorized key. # rsh node2 cat /.ssh/authorized_keys >>/.ssh/authorized_keys # rsh node3 cat /.ssh/authorized_keys >>/.ssh/authorized_keys # rsh node2 cat /home/oracle/.ssh/authorized_keys >>/home/oracle/.ssh/authorized_keys # rsh node3 cat /home/oracle/.ssh/authorized_keys >>/home/oracle/.ssh/authorized_keys Now, on the first node, the root user and the Oracle user have all combinations of public keys in their authorized _keys files.

Write the files to node2 and node3. # rcp /.ssh/authorized_keys node2:/.ssh/authorized_keys # rcp /.ssh/authorized_keys node3:/.ssh/authorized_keys # rcp /home/oracle./.ssh/authorized_keys node2:/home/oracle./.ssh/authorized_keys # rcp /home/oracle./.ssh/authorized_keys node3:/home/oracle./.ssh/authorized_keys SSH requires an appropriate ownership and no read/write permission by group and other. # dsh chown root /.ssh/authorized_keys # dsh chmod 600 /.ssh/authorized_keys # dsh chown oracle:dba /home/.ssh/authorized_keys # dsh chmod 600 /home/.ssh/authorized_keys • Modify the /etc/hosts file. Add the machine name details used in the setup in the /etc/hosts file as shown below. Decyder Software Download more. Configure the IPs on the respective adapters using the chinet command.