We are going to install a single node RAC database with ASM on Red Hat 5 Update 3 to leverage the latest and greatest features of Oracle Database 11g Release 2.

Before we start, let’s see the /etc/hosts file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
# RAC Node #1
192.168.242.128 jin1.dbaexpert.com jin1
192.168.242.228 jin1-vip.dbaexpert.com jin1-vip
192.168.242.108 jin-cluster.dbaexpert.com jin-cluster
192.168.60.128 jin1-priv.dbaexpert.com jin1-priv

[oracle@jin1 grid]$ ./runInstaller
Starting Oracle Universal Installer…

Checking Temp space: must be greater than 80 MB. Actual 115174 MB Passed
Checking swap space: must be greater than 150 MB. Actual 2047 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-09-03_01-01-57AM. Please wait …

Picture 2.png

Click on the Next button to select the Installation Type
Picture 7.png
In our particular example, we will choose a Advanced Installation
Click on the Next button

Picture 8.png
Select any additional language besides English you would like to install
Click on Next
Picture 10.png

Note: Make sure that the GNS VIP Address is on a separate subnet from your public network; otherwise, you will receive an error stating that the Grid Naming Service (GNS) Virtual IP Address is already assigned to another system.

Click on the Next button to be routed to the Cluster Node Information screen
Picture 11.png
If you want to add additional RAC instances, click on the Add button. In this screen, click on the SSH Connectivity button to setup and test user equivalence.

Picture 12.png

Click on the Setup button
You will get a small window indicating that ssh is being setup. Once ssh connectivity is established, you will get a window indicating that a passwordless SSH connectivity between the nodes have been established as shown here:
Picture 6.png
Click on the OK button
From the Specify Network Interface Usage screen, specify your private and public network interfaces.
Picture 13.png
Click on the Next button

At the Storage Option Information Screen, select the option to place the OCR and Vote disks on ASM
Picture 14.png
Click on Next

From the Create Disk Group screen, we will create the DATA diskgroup based on the ORCL:DATA1 and ORCL:DATA2 ASMLIB disks:
Picture 15.png
Click on Next

From the Specify ASM Password screen, select the option to specify the same password for the SYS and ASMSNMP accounts. For security considerations, you should set the passwords to be different since they have different privileges.
Picture 16.png

Note: You will notice two differences in the password fields. First, as you start typing, you get an error message stating that the passwords do not match. Once you complete the password confirmation field, the password mismatch warning will go away. Also, oracle performs a password security check and informs you if your passwords conform to their security assessment.

Click on Next
If your passwords do not conform to their standards, you will receive another warning:
Picture 17.png
Click on the Yes button to continue

From the Failure Isolation Support screen, keep the “Do not use Intelligent Mangement Interface (IPMI) option
Click on Next

From the Privileged Operating System Groups screen, select the OSASM, OSDBA and OSOPER groups accordingly:
Picture 19.png

Note:
If all the three OS groups are the same, you will receive a warning message stating that they are in the same group as shown here:
Picture 20.png
Again, click on the Yes button to continue

From the Specify Installation Location, change your ORACLE_BASE accordingly.
Picture 21.png
Click on Next

From the Create Inventory screen, specify the directory for the Oracle Inventory.
Note: Starting in Oracle Database 11g Release 1, the oraInventory directory defaults to one level below ORACLE_BASE.
Picture 22.png
Click on Next

In the Perform Prerequisite Checks, we have several things to fix (really couple things to fix and couple of other things to ignore 🙂 ).
Picture 23.png
First, you will notice the new Fix and Check Again button. Click on the Fix & Check Again button.

You will immediately see a window to execute the fixit script as root:
Picture 24.png

Execute the script as root from the specified directory:
[root@jin1 CVU_11.2.0.1.0_oracle]# ./runfixup.sh
Response file being used is :./fixup.response
Enable file being used is :./fixup.enable
Log file location: ./orarun.log
Setting Kernel Parameters…
fs.file-max = 327679
fs.file-max = 6815744
net.ipv4.ip_local_port_range = 9000 65500

After a successful execution as root, click on the OK button to go back to the Perform Prerequisite Checks screen. The OUI will automatically re-run the prerequisite checks and report any errors. You are strongly recommended to resolve all the issues reported from the Perform Prerequisite Checks screen. In our example, we will ignore the warnings for the Physical Memory, Swap Size and Network Time Protocol (NTP).
Click on Next

In the Summary screen, you have the option to save the installation options that you chose as a response file.
Picture 26.png
Click on the Finish button

You can monitor the installation from the progress window.

Once the software copy is complete, you will be directed to execute orainstRoot.sh and root.sh script from each of the RAC nodes.
Picture 27.png

First, let’s run the orainstRoot.sh script:
[root@jin1 oraInventory]# ./orainstRoot.sh
Changing permissions of /apps/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.

Changing groupname of /apps/oraInventory to oinstall.
The execution of the script is complete.

Next run root.sh:
[root@jin1 grid]# ./root.sh
Running Oracle 11g root.sh script…

The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /apps/11.2.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin …
Copying oraenv to /usr/local/bin …
Copying coraenv to /usr/local/bin …

Creating /etc/oratab file…
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
2009-09-03 02:46:14: Parsing the host name
2009-09-03 02:46:14: Checking for super user privileges
2009-09-03 02:46:14: User has super user privileges
Using configuration parameter file: /apps/11.2.0/grid/crs/install/crsconfig_params
Creating trace directory
LOCAL ADD MODE
Creating OCR keys for user ‘root’, privgrp ‘root’..
Operation successful.
root wallet
root wallet cert
root cert export
peer wallet
profile reader wallet
pa wallet
peer wallet keys
pa wallet keys
peer cert request
pa cert request
peer cert
pa cert
peer root cert TP
profile reader root cert TP
pa root cert TP
peer pa cert TP
pa peer cert TP
profile reader pa cert TP
profile reader peer cert TP
peer user cert
pa user cert
Adding daemon to inittab
CRS-4123: Oracle High Availability Services has been started.
ohasd is starting

CRS-2672: Attempting to start ‘ora.gipcd’ on ‘jin1’
CRS-2672: Attempting to start ‘ora.mdnsd’ on ‘jin1’
CRS-2676: Start of ‘ora.gipcd’ on ‘jin1’ succeeded
CRS-2676: Start of ‘ora.mdnsd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.gpnpd’ on ‘jin1’
CRS-2676: Start of ‘ora.gpnpd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.cssdmonitor’ on ‘jin1’
CRS-2676: Start of ‘ora.cssdmonitor’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.cssd’ on ‘jin1’
CRS-2672: Attempting to start ‘ora.diskmon’ on ‘jin1’
CRS-2676: Start of ‘ora.diskmon’ on ‘jin1’ succeeded
CRS-2676: Start of ‘ora.cssd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.ctssd’ on ‘jin1’
CRS-2676: Start of ‘ora.ctssd’ on ‘jin1’ succeeded

ASM created and started successfully.

DiskGroup DATA created successfully.

clscfg: -install mode specified
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ‘root’, privgrp ‘root’..
Operation successful.
CRS-2672: Attempting to start ‘ora.crsd’ on ‘jin1’
CRS-2676: Start of ‘ora.crsd’ on ‘jin1’ succeeded
CRS-4256: Updating the profile
Successful addition of voting disk 43eecaac84f14f5fbf2cf15d80b43d14.
Successfully replaced voting disk group with +DATA.
CRS-4256: Updating the profile
CRS-4266: Voting file(s) successfully replaced
## STATE File Universal Id File Name Disk group
— —– —————– ——— ———
1. ONLINE 43eecaac84f14f5fbf2cf15d80b43d14 (ORCL:DATA1) [DATA]
Located 1 voting disk(s).
CRS-2673: Attempting to stop ‘ora.crsd’ on ‘jin1’
CRS-2677: Stop of ‘ora.crsd’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.asm’ on ‘jin1’
CRS-2677: Stop of ‘ora.asm’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘jin1’
CRS-2677: Stop of ‘ora.ctssd’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.cssdmonitor’ on ‘jin1’
CRS-2677: Stop of ‘ora.cssdmonitor’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.cssd’ on ‘jin1’
CRS-2677: Stop of ‘ora.cssd’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘jin1’
CRS-2677: Stop of ‘ora.gpnpd’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘jin1’
CRS-2677: Stop of ‘ora.gipcd’ on ‘jin1’ succeeded
CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘jin1’
CRS-2677: Stop of ‘ora.mdnsd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.mdnsd’ on ‘jin1’
CRS-2676: Start of ‘ora.mdnsd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.gipcd’ on ‘jin1’
CRS-2676: Start of ‘ora.gipcd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.gpnpd’ on ‘jin1’
CRS-2676: Start of ‘ora.gpnpd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.cssdmonitor’ on ‘jin1’
CRS-2676: Start of ‘ora.cssdmonitor’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.cssd’ on ‘jin1’
CRS-2672: Attempting to start ‘ora.diskmon’ on ‘jin1’
CRS-2676: Start of ‘ora.diskmon’ on ‘jin1’ succeeded
CRS-2676: Start of ‘ora.cssd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.ctssd’ on ‘jin1’
CRS-2676: Start of ‘ora.ctssd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.asm’ on ‘jin1’
CRS-2676: Start of ‘ora.asm’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.crsd’ on ‘jin1’
CRS-2676: Start of ‘ora.crsd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.evmd’ on ‘jin1’
CRS-2676: Start of ‘ora.evmd’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.asm’ on ‘jin1’
CRS-2676: Start of ‘ora.asm’ on ‘jin1’ succeeded
CRS-2672: Attempting to start ‘ora.DATA.dg’ on ‘jin1’
CRS-2676: Start of ‘ora.DATA.dg’ on ‘jin1’ succeeded
/apps/11.2.0/grid/bin/srvctl start nodeapps -n jin1 … failed
Preparing packages for installation…
cvuqdisk-1.0.7-1
Configure Oracle Grid Infrastructure for a Cluster … failed
Updating inventory properties for clusterware
Starting Oracle Universal Installer…

Checking swap space: must be greater than 500 MB. Actual 1575 MB Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /apps/oraInventory
‘UpdateNodeList’ was successful.

Click on the OK button to continue

Created by Charles Kim, Oracle ACE Director

Posted in ASM, RAC
Share this post, let the world know

Leave a Reply

Your email address will not be published. Required fields are marked *

*