Install one node RAC on AIX system

Install one node RAC on AIX system

Step 1: Set the Environment Variable for Oracle

ORACLE_BASE = /u01/app/oracle
--- Local volume on both nodes ($ORACLE_BASE)
----- Local volume on both nodes ($ORACLE_HOME for the database)
- Local volume on both nodes ($ORACLE_HOME for the cluster and ASM)

Step 2: Create a user oracle and its roles:
Grid Installation: oracle (gid: oinstall, groups: dba)
Oracle Database: oracle (gid:oinstall, groups:dba)
Created with same uid and gid as on the two Oracle RAC One Node servers:

-- Change the owner of location
dap-node01:/ > id oracle
uid=400(oracle) gid=401(oinstall) groups=400(dba),402(asm),403(asmdba)
dap-node01:/ > chown -R oracle:oinstall /u01/app
dap-node01:/ > chown -R oracle:oinstall /u01/app/download/
dap-node01:/ > chmod -R 775 /u01/app/download/

--Set the shell limits for the oracle user:
oracle@dap-aca1-ora01 /u01/app/download > ulimit -a

Step3: Check the other Operating System Requirement:

oracle@dap-aca1-ora01 /u01/app $ /usr/sbin/lsps –a
--System Architecture
oracle@dap-aca1-ora01 /u01/app $ /usr/bin/getconf HARDWARE_BITMODE
# bootinfo –K

--Filesystem disk space requirements
oracle@dap-aca1-ora01 /tmp > df -k (on /tmp and /u01/app)

--Operating system requirements
dat-gen-cls03:/ > oslevel –r

--Check package Installed:
dat-gen-cls03:/ > lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat
bos.perf.perfstat bos.perf.proctools xlC.aix61.rte gpfs.base

Step 4: FIX for SSH
By default, OUI searches for SSH public keys in the directory /usr/local/etc/, and ssh-keygen binaries in /usr/local/bin. However, on AIX, SSH public keys typically are located in the path /etc/ssh, and ssh-keygen binaries are located in the path /usr/bin. To ensure that OUI can set up SSH, use the following command to create soft links:

# ln -s /etc/ssh /usr/local/etc
# ln -s /usr/bin /usr/local/bin

Step 5: Edit host file of system to make entries of IP address
Edit all host file with:

Node 1 Public IP
Node 1 VIP IP
Node 1 Private IP
Node 2 Public IP
Node 2 VIP IP
Node 2 Private IP
Cluster SCAN Public IP
Node 3 Public IP

Step 6: Cluster Verification Utility Issue in Checking Network Parameters
During an Oracle RAC database installation, the Cluster Verification Utility may not check the network parameters (tcp_sendspace, tcp_recvspace, udp_sendspace, udp_recvspace, sb_max, rfc1323) correctly.
This may happen as part of the prerequisite check or if you run the following command:

cluvfy stage -pre crsinst

Establish a symlink /etc/no to /usr/sbin/no.
(ln -s /usr/sbin/no /etc/no)
This issue is tracked with Oracle bug 13077654.

Step 7: Setup the SSH Key on both the nodes

bash-3.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/oracle/.ssh/id_rsa):
Created directory ''.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:

bash-3.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/oracle/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:

bash-3.2$ cd .ssh
bash-3.2$ cat >authorized_keys

bash-3.2$ scp oracle@dap-aca1-ora01:/home/oracle
oracle@dap-aca1-ora01's password:

bash-3.2$ pwd
bash-3.2$ cat ../ >>authorized_keys
bash-3.2$ scp authorized_keys dap-aca1-ora02:/home/oracle/.ssh

Note! Make sure you test all combinations for SSH:
Node 1 Public -> Node 2 Public -> Node1 Public
Node 1 Private -> Node 2 Private -> Node 1 Private
Node 1 Public -> Node 1 Public -> Node 1 Private
Node 2 Public -> Node 2 Public -> Node 2 Private

Step 8: Setting ephemeral settings
As root:

/usr/sbin/no -p -o tcp_ephemeral_low=9000 -o tcp_ephemeral_high=65500
/usr/sbin/no -p -o udp_ephemeral_low=9000 -o udp_ephemeral_high=65500
/usr/sbin/no -a | fgrep ephemeral
tcp_ephemeral_high = 65500
tcp_ephemeral_low = 9000
udp_ephemeral_high = 65500
udp_ephemeral_low = 9000

Follow instructions from MOS Note ID 811293.1:
Ensure that the network tuning parameters are set in accordance with the following to ensure optimal interconnect performance:

tcp_recvspace = 65536
tcp_sendspace = 65536
udp_sendspace = 65536 (64k is max value)
udp_recvspace = 655360 (Minimum recommended value is 10x udp_sendspace, parameter value must be less than sb_max)
rfc1323 = 1
sb_max = 4194304
ipqmaxlen = 512

NOTE: Failure to set the udp_sendspace will result in failure of for GI installations, see Document 1280234.1.

/usr/sbin/no -p -o tcp_recvspace=65536 -o tcp_sendspace=65536
/usr/sbin/no -p -o udp_sendspace=65536 -o udp_recvspace=655360
/usr/sbin/no -p -o rfc1323=1
/usr/sbin/no -p -o sb_max=4194304
/usr/sbin/no -r -o ipqmaxlen=512

Setting ipqmaxlen to 512 in nextboot file

Warning: changes will take effect only at next reboot reboot??????

Step 9: Manage the ASM Disks
All disks needed for the solution should be part of the order of the new servers.
Configuring disks for use by ASM:
Note: Remember to change owner of the disk devices to user oracle and group dba/oinstall:

oracle@dap-aca1-ora01 /dev > ls -al rasm*
# cd /dev
# bootinfo -s rasm_0090_14D95

Note: It will only give you the right result when your prompt is standing on /dev.

Set user capabilities:
# lsuser -a capabilities root
# lsuser -a capabilities oracle

Enter or edit the following line in the .profile for Oracle user:
Specifying a value of “umask 022” for the default file mode creation mask and “export AIXTHREAD_SCOPE=S”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s