Hardware and Software requirements (HP-UX 11i and Solaris 9.0) including the packages to be installed.

Hardware Requirment:-

RAM: – At least 1024 MB of physical RAM is required. SAT servers had 8GB of RAM. To check use the following command can be used. grep “Physical:” /var/adm/syslog/syslog.log

Swap Configuration: –

  1. Between 512 MB and 2048 MB  1.5 times the size of RAM
  2. Between 2049 MB and 8192 MB                Equal to the size of RAM
  3. More than 8192 MB                                  0.75 times the size of RAM

To check the swap space use following command: – /usr/sbin/swapinfo –a

Space Requirment in /tmp: – 400 MB of disk space in the /tmp directory

Space Need for Oracle Software installation mount point: – 3GB.

Disk Space on Shared Storage for database files: – 5GB minimum for seed database creation. Shared storage should be accessible from all nodes in cluster and should be updatable too. For testing this, one can write on all shared disks from node1 and try to read from rest of all the nodes in cluster and should be able to see the contents written from node1 on all rest of the three nodes. Regarding disk more detail will be provided later.

OS version: – HP-UX PA-RISC Version 11i v1 (11.11) and Solaris Operating System (SPARC) Version 9.

OS patches: – Patches for HP-UX 11i V1 (11.11):

PHNE_31097: ONC/NFS general release/performance patch

PHSS_31221: HP aC++ -AA runtime libraries (aCC A.03.60)

Network Configuration Setup( all node in cluster) : –

10g either R1 or R2 needs three IP addresses configured.

  1. Public IP address listed in /etc/hosts and optionally registered in DNS. This is the IP, which users use to connect to the server.
  2. Interconnect IP, which is needed for internode communication. This should be the dedicated network and public traffic should not use this. It should be listed in /etc/hosts. This IP must be on same subnet on all hosts.
  3. Virtual IP: – Using this IP, Oracle client will connect to Oracle database server. This should be listed in /etc/hosts and optionally in DNS.This IP should not be configured when we start the installation. VIPCA (Virtual IP configuration Assistant) will ask for this IP and once VIPCA is completed, this IP will be configured. This IP must be on same subnet on all hosts.

Note: – Interconnect and virtual IP should be configured with failover using either IPMP (Solaris) or APA (HP-UX). More detail on Metalink Note: 296874.1, 368464.1, 283107.1

Creating Oracle Software Owner (On all hosts in cluster).

  1. First create a group for oracle software owner using follwing command:  groupadd orpsatdo
  2. Create a user and make above created group as primary group using following command: – useradd –g orpsatdo –d /oracle/psatado –s /usr/bin/ksh orpsatdo

# Default user .profile file (/usr/bin/sh initialization).
# Set up the search paths:

# Set up the shell environment:
set -u
trap “echo ‘logout'” 0

# Set up the shell variables:
export EDITOR
umask 022

Configuring SSH and SCP (on all node in cluster)

Oracle 10g needs SSH and SCP for autologin configured on all nodes of the cluster for root user as well oracle software owner. Steps to configure SSH:-

1) Login to the server/target on which you want to enable auto-logon

2) Goto the SSH installation directory eg. “/opt/ssh/etc (HP-UX) and /etc/ssh/etc (Solaris)”

3) Open the file named “vi sshd_config”

4) Change and enable the following parameters:
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

5) Save the file and restart ssh. This will enable the SSH auto-logon to this machine now.

How to configure SSH login using public Key

1) Login to the server which needs to auto-login (source), eg. orpsatgv

2) Create a ssh public and private key using the command “ssh-keygen -t rsa”
3) Keep the filenames as default when the above output ask for a filename.
4) FTP to the target server where you want to auto-logic “sftp orpsatdo@”

5) Put/Upload the source “id_rsa.pub” into the /tmp folder

6) Come out of the FTP
7) Login to the target machine using SSH/telnet
8) Goto the <home directory>/.ssh
9) Append the source generated key using the command “cat /tmp/id_rsa.pub >> authorized_keys”
Make sure you append using “>>” and not overwrite the authorized_keys file.
Best way is to backup the autorized_keys file before appending.
10) Disconnect and then reconnect the target server. You should be able to login without password. If this happens,
your SSH key generation is successfull.

Once ssh is setup using above steps for root as well as oracle software owner, create following links as root.

  1. ln –s /usr/bin/ssh /usr/bin/local/ssh
  2. ln –s /usr/bin/scp /usr/bin/local/ssh

Note: – On solaris, to allow root login without password, you need to uncomment PermitRootLogin yes parameter and restart the ssh deamon in /etc/ssh/etc/sshd_config.

Note: – Once Ssh is configured, you should try following combination for logging in and should not get the banner other wise oracle clusterware will give error telling that ssh not configured.

  1. local node to localhost for root and oracle user.
  2. localhost node to hostname for root and oracle user.
  3. local node to IP of local machine for root and oracle user.
  4. local node to all hosts in cluster for root and oracle user using hotname and IP.
  5. above combination must be tried on all nodes.

Changing the kernel Parameters

On HP-UX oracle was oracle running so did not set but using kmtune, kernel parameter can be changed and if its dynamic parameter does not need the restart the system even. Following command will tell either parameter is dynamic or not

kmtune -q shmmax

Parameter             Current Dyn Planned                    Module     Version


shmmax             8589934592  Y  8589934592

On solaris, we followed the following method to change the kernel parameter.

  1. Added the following values in /etc/system
    1. a. forceload: sys/semsys
    2. b. set shmsys:shminfo_shmmax = 8589934592
    3. c. set semsys:seminfo_semmns = 6000
    4. d. set semsys:seminfo_semmsl = 600

    If you don’t add forceload: sys/semsys, it will load the shmmax but will not load semmns and semmsl kernel parameters

  2. Restart the system and check the value of changed parameters using sysdef | grep –i sem or shm

Formating and preparing the shared disks

  1. All commands to be executed by root.
  2. Check the disks attached to system using format command. We need some small number of disks for following files.
    1. Two 100 MB slices for OCR
    2. Three 100 MB slices for Voting disks
    3. One 100 MB slice for ASM spfile.
  3. So on first three disks, I created three slices for above files and rest all space used for ASM. For formatting all the disks and use complete disk for one slice we used following scripts.

while [ $i -lt 28 ] ; do
ret=`format -d c2t50060E8004764814d${i} <<EOF
i=`expr ${i} + 1`

Now we will proceed with Installation since all required OS infrastructure (Network, Disks, Users etc) is setup. First Oracle Clusterware is to be installed and than RDBMS.Following is the procedure to install CRS.For some important steps, I have put screenshots too.

I assume that installation is being started from remote machine and VNC(Virtual Network Computing) is setup properly to install in GUI mode

  1. before starting the installation, verify your environment using cluvfy. One can use following commands to verify atleast major components
    1. cd to cluvfy directory like /stage/102R2/clusterware/cluvfy.
    2. ./runcluvfy.sh comp –n psatdo1 psatdo2 /dev/asm to veryfiy shared storage.
    3. ./runcluvfy.sh stage –pre crsinst  -n psatdo1,psatdo2 –q /dev/asm/*
    4. ./runcluvfy.sh comp nodecon -n psatdo1,psatdo2 -verbose
  2. From Installation directory, start the runInstaller.
  3. First screen is Welcome Screen, so just press next.
  4. On Next screen, you will be asked for inventory location. Make sure you don’t have oraInst.loc already at /var/opt/oracle. If so, this screen will not be displayed and inventory will be created at the path mentioned in oraInst.loc.
  5. Next Screen is again for checking the per-requisit for cluster installation. If you have setup your environment as discussed above and cluvfy has verified it, should not give error. If it gives warning for any kernel parameter, just note down the name of parameter and after installation change it correct value.
  6. Next Screen is path for CRS Installation.

Viewers of this post also viewed...