Oracle 12c Grid Infrastructure Installation on Oracle Linux 6.4

Oracle 12c Grid Infrastructure Installation on Oracle Linux 6.4

The document describes the installation of oracle 12cR1 Grid Infrastructure on Linux 6.4(64-bit) on oracle virtualbox-4.2.18 with latest virtualbox extension pack. Note:- Oracle 12c Grid Infrastructure and RAC cannot be installed on 32bit systems as this is desupported in 12c and might not be available for future release as well.

The oracle software will be downloaded from MOS using valid CSI. The installation steps mentioned here is used for 12.1.0. The virtualbox software can be downloaded from www.virtualbox.org,

The virtualbox can provide you with the flexibility to run multiple machines on single physical server. It also allows you to setup, configure and use the virtual shared storage.

Typical Diagram.


Requirement:- Before kicking off the installation, consider the following bullets,

  • ·         Be ready with host machine running with two virtual machines on VM.
  • ·         Consider you have sufficient memory and CPU available, Minimum requirement are 4G physical memory on each guest machine, but recommendation is to use minimum of 6G on each guest. otherwise system will go crazy.
  • ·         Add the 3-SCAN ip's in DNS or GNS, if you have no plan to use the DNS or GNS, than single SCAN ip will be added into /etc/hosts on all the nodes.
  • ·         The public and virtual ip must be on same subnet including SCAN. The private ip must be on different network. Do not use 169.254.* series of IP as private or public because the series are reserved for HAIP.
  • ·         This installation uses the 64bit Linux guest host with 4G of physical RAM each and 3-shared virtual disk for ASM storage.
Software::

  • ·         Download virtualbox with extension pack and install
  • ·         Oracle Enterprise Linux 6.4.
  • ·         Oracle Software with Grid Infrastructure (Disk1, Disk2 and Disk3)
  Guest Machine setup and configuration.  The guest machine setup and configuration are same as explained in my earlier post for 11gR2 Grid Infrastructure (RAC) installation on Linux 5.4. Please follow the same steps to configure and setup the guest hosts on virtualbox.

Grid Infrastructure Installation Prerequisites:  The prerequisite can be setup by either manually or automatic. The Oracle Enterprise Linux comes with pre-installed oracle prerequisite with oracle-validated packages or oracle-rdbms-server-12cR1-preinstall-1.0-1.el6.x86_64.rpm. Selecting these during installation will install all the required packages and setup the kernel parameters and other configuration files. The oracle user are also created by default with oinstall and DBA as group. other automatic method is to install the oracle-validated packages(Linux 5 and Linux 4) from ULN. Note the internet connectivity is required for downloading the packages.  The instructions are available at http://public-yum.oracle.com to setup the oracle linux repository, and login as root and execute, 

[root@Node01~]# yum install oracle-validated  or
[root@Node01~]# yum install oracle-rdbms-server-12cR1-preinstall

Manual Method:: if you are not using OEL (Oracle Enterprise Linux) or have any challenge to install the prerequisite packages, follow the steps, download and install the below list of packages.

binutils-2.20.51.0.2-5.11.el6 (x86_64)
compat-libcap1-1.10-1 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (x86_64)
compat-libstdc++-33-3.2.3-69.el6.i686
gcc-4.4.4-13.el6 (x86_64)
gcc-c++-4.4.4-13.el6 (x86_64)
glibc-2.12-1.7.el6 (i686)
glibc-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6.i686
ksh
libgcc-4.4.4-13.el6 (i686)
libgcc-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6.i686
libstdc++-devel-4.4.4-13.el6 (x86_64)
libstdc++-devel-4.4.4-13.el6.i686
libaio-0.3.107-10.el6 (x86_64)
libaio-0.3.107-10.el6.i686
libaio-devel-0.3.107-10.el6 (x86_64)
libaio-devel-0.3.107-10.el6.i686
libXext-1.1 (x86_64)
libXext-1.1 (i686)
libXtst-1.0.99.2 (x86_64)
libXtst-1.0.99.2 (i686)
libX11-1.3 (x86_64)
libX11-1.3 (i686)
libXau-1.0.5 (x86_64)
libXau-1.0.5 (i686)
libxcb-1.5 (x86_64)
libxcb-1.5 (i686)
libXi-1.3 (x86_64)
libXi-1.3 (i686)
make-3.81-19.el6
sysstat-9.0.4-11.el6 (x86_64)

Add the following lines into "/etc/sysctl.conf" file and execute the following command as root to update the current kernel parameters.
fs.aio-max-nr = 1048576

fs.file-max = 6815744

kernel.shmall = 2097152

kernel.shmmax = 1054504960

kernel.shmmni = 4096

# semaphores: semmsl, semmns, semopm, semmni

kernel.sem = 250 32000 100 128

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default=262144

net.core.rmem_max=4194304

net.core.wmem_default=262144

net.core.wmem_max=1048586

[root@Node01~]# sysctl -p

Edit and add the below lines to the "/etc/security/limits.conf" file.
oracle               soft    nproc   2047

oracle               hard    nproc   16384

oracle               soft    nofile  1024

oracle               hard    nofile  65536

grid               soft    nproc   2047

grid               hard    nproc   16384

grid               soft    nofile  1024

grid               hard    nofile  65536

 Also add the lines to the "/etc/pam.d/login" file, if it does not exist.
     session    required     pam_limits.so

Create the users and groups as root on both the nodes (separate for grid infrastructure and oracle RDBMS), you can also use the same user for oracle and grid infrastructure. Note:- keep the guid same across all the nodes, otherwise user equivalence check will fail.
[root@Node1~]#groupadd -g 509 oinstall
[root@Node1~]#groupadd -g 511 asmadmin
[root@Node1~]#groupadd -g 513 asmdba
[root@Node1~]#groupadd -g 511 asmoper
[root@Node1~]#groupadd -g 510 dba
[root@Node1~]#useradd -u 509 -g oinstall -G asmadmin,asmoper,asmdba,dba grid
[root@Node1~]#useradd -u 510 -g oinstall -G dba,asmdba oracle
Create the desired directories and change the ownership to user oracle and grid, here i have created onde filesystem for grid and oracle software(/orasoft)
[root@Node1~]#mkdir -p  /orasoft/app/11.2.0/grid
[root@Node1~]#chown -R grid:oinstall /orasoft
[root@Node1~]#chmod -R 775 /orasoft/
[root@Node1~]#mkdir -p /orasoft/app/oracle/product/11.2.0/dbhome_1
[root@Node1~]#chown -R oracle:oinstall /orasoft
[root@Node1~]#chmod -R 775 /orasoft/

setup the passwords for grid and oracle user.
[root@Node1~]#passwd oracle
[root@Node1~]#passwd grid

setup the ip addresses as mentioned above in "/etc/hosts" and add the single IP for scan into it, if DNS is not available. (copy the same file on other nodes)
#Private Address
10.10.0.50    Node1-priv
10.10.0.51    Node2-priv
#Public Address
192.168.0.50    Node1
192.168.0.51    Node2
#VIP Address
192.168.0.55    Node1-vip
192.168.0.56    Node2-vip
#SCAN Address
192.168.0.60    node-scan

Install the clusterware specific package shipped with grid binaries on all the nodes as a root user.
[root@Node1~]#cd /tmp/grid/rpm
[root@Node1~]#export CVUQDISK_GRP=oinstall
[root@Node1~]#rpm -ivh cvuqdisk-1.0.9.1.rpm

Disable the SELINUX by commenting the below parameter into "/etc/selinux/config" file
SELINUX=enforcing to SELINUX=disabled or permissive.

Stop and disable the firewalls between nodes (execute on both the nodes),
[root@Node1~]#service iptables stop
[root@Node1~]#chkconfig iptables off

The time synchronization can be done by either NTP or CTSS, if you are not using NTP, then CTSS will synchronize the time between nodes. so stop and remove the NTPD configuration from all the nodes,
[root@Node1~]# service ntpd stop
Shutting down ntpd:                                        [  OK  ]
[root@Node1~]# chkconfig ntpd off
[root@Node1~]# mv /etc/ntp.conf /etc/ntp.conf.orig
[root@Node1~]# rm /var/run/ntpd.pid
or if you are planning to use NTP, then you must add the "-x" option into "/etc/sysconfig/ntpd" file and then restart the service.
OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid"
[root@Node1~]#service ntpd restart

SSH: Configure SSH for user equivalence on both the nodes (grid as well as oracle user), during installation OUI needs to copy files to and execute programs on the other nodes in the cluster. Configuring SSH on both the nodes means copying and executing the program on other nodes without prompting passwords.

Generate RSA/DSA Keys: login as grid and oracle user one by one and generate the keys on each node.
[grid@Node1~]$mkdir .ssh
[grid@Node1~]$chmod -R 700 .ssh
[grid@Node1~]$ssh-keygen -t rsa (press 3-times enter, generates two files)
[grid@Node1~]$ssh-keygen -t dsa (press 3-times enter, generate two files)
Generate authorized_keys: Generate the authorized_keys by copying RSA and DSA public keys from all the nodes.
[grid@Node1~]$ssh Node1 cat /home/grid/.ssh/id_rsa.pub >> authorized_keys
[grid@Node1~]$ssh Node1 cat /home/grid/.ssh/id_dsa.pub >> authorized_keys
[grid@Node1~]$ssh Node2 cat /home/grid/.ssh/id_rsa.pub >> authorized_keys
[grid@Node1~]$ssh Node2 cat /home/grid/.ssh/id_dsa.pub >> authorized_keys
[grid@Node1~]$ssh Node1 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys
[grid@Node1~]$ssh Node1 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys
[grid@Node1~]$ssh Node2 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys
[grid@Node1~]$ssh Node2 cat /home/oracle/.ssh/id_dsa.pub >> authorized_keys

Copy the generated authorized_keys & known_hosts to other nodes:
$scp authorized_keys known_hosts  Node2:/home/grid/.ssh
$scp authorized_keys known_hosts  Node2:/home/oracle/.ssh

Alternatively you can use the oracle provided utility available in software location e.g. /tmp/1120_grid/grid/sshsetup/sshUserSetup.sh or during installation using GUI prompt you for configuration. Make sure for silent installation, the ssh configured before proceeding for installation.
$/<your_sw_location>/grid/sshsetup/sshUserSetup.sh -user grid -hosts “Node1 Node2” -advanced -noPromptPassphrase

Adding shared storage:- The shared storage will be either allocated from SAN or NAS, but here we are using VM, follow the steps as explained in earlier post for 11gR2 Grid Infrastructure (RAC) Installation to create the shared storage. Good idea to reboot all the guest at this point because we did lots of changes.

Installation of Grid Infrastructure: Make sure all the machines are up and pingable from each other (Node1 and Node2). goto the software location and unzip the disk3, change the ownership of the software to grid:oinstall

[grid@Node1~]$ cd /orasoft/software/grid
First Window appears for 12c

select "Skip software updates" if you do not have MOS login credentials or internet connectivity. - Next

Select "Install and Configure Grid Infrastructure for a Cluster" option, then click the "Next" button.


Select type of cluster required. "Configure a Standard Cluster" option, then click the "Next" button.
 



Select "Typical Installation" option, then click the "Next" button.




Enter the SCAN name and then click the "Add" button to add the other node details and enter the public host name and vip name and hit "OK"

Next click on "Identify network interfaces" and select the correct interface configuration and hit "OK"

Now, click on the "ssh" tab to setup the ssh passwordless connectivity between two nodes if not done already. provide the correct os user and password in box and than click on "setup". once ssh setup is done test to to make sure its configured properly and click "Next"

In next window, Enter the "Oracle Base" "/orasoft/app/grid/grid" and "/orasoft/app/grid/12.1.0/grid" as the software location. select the "Automatic Storage Manager" for "cluster registry storage type" and enter the ASM password. Hit "Next" button.

Give the diskgroup name "DATA" or anyother (choice yours), Set the redundancy to "Normal". if the ASM disks are not displayed, click the "Change Discovery Path" button and enter "/dev/oracleasm/disks/*" and click the "OK" button. Select all 3 disks and click the "Next" button. you can also select the Allocation Unit size, of your choice.



 Accept the default oraInventory location and hit "Next" button. 

The next window will take you to "Root script execution configuration" where you can select "Automatically run configuration scripts" and check the button as per your convenient and supply the password. The same task you can also do when prompt for root.sh scripts execution manually. (Note the change here in 12c), i am using manual method for script execution and proceeding to next.

The next window will do the prerequisite checks and display the messages for any failures.
The above three warnings are reported because, i have allocated only 4G of memory to each hosts and the minimum required physical memory for grid infrastructure installation is 4G in 12c. The /dev/shm devices are mounted as tmpfs, in /etc/fstab and can be ignorable. The checks for ASM devices can also be ignored. (check the Ignore All box, if prerequisite are satisfied and hit "Next".

You might also get the warnings for CVUQDISK package, of not installed already. follow the below steps and install the package on all the nodes as root. The rpm is shipped with software in "/<your_sw_unzipped_location>/grid/rpm/cvuqdisk_1.0.9.1.rpm" available in grid software or you can also find the software in "/tmp/CVU_12.1.0.1.0_grid" after prerequisite checks on all the nodes.

The next, window will have the summary of, and if you are like the summary, hit the "Install" button.

The progressing window will be displayed and the installation take few minutes..meanwhile you can enjoy the "coffee".

During installation, prompted for the scripts to run as root, follow the sequence while executing the oraInstroot.sh and root.sh scripts. if not selected to execute automatically. Once done on all the nodes, hit "OK"
(Note:- Here its prompting Node1 for oraInstroot.sh scripts because the script for inventory already executed on other node before using that node into cluster.) follow the sequence.

root.sh script logs executed on Node1::
[root@Node1 etc]# /orasoft/app/grid/oraInventory/orainstRoot.sh
Changing permissions of /orasoft/app/grid/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.

Changing groupname of /orasoft/app/grid/oraInventory to oinstall.
The execution of the script is complete.
[root@Node1 etc]# /orasoft/app/grid/12.1.0/grid/root.sh
Performing root user operation for Oracle 12c

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /orasoft/app/grid/12.1.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 script.
Now product-specific root actions will be performed.
Using configuration parameter file: /orasoft/app/grid/12.1.0/grid/crs/install/crsconfig_params
2013/09/24 02:06:07 CLSRSC-363: User ignored prerequisites during installation
OLR initialization - 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
2013/09/24 02:07:36 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'node1'
CRS-2677: Stop of 'ora.drivers.acfs' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.evmd' on 'node1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'node1'
CRS-2676: Start of 'ora.mdnsd' on 'node1' succeeded
CRS-2676: Start of 'ora.evmd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'node1'
CRS-2676: Start of 'ora.gpnpd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'node1'
CRS-2672: Attempting to start 'ora.gipcd' on 'node1'
CRS-2676: Start of 'ora.cssdmonitor' on 'node1' succeeded
CRS-2676: Start of 'ora.gipcd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'node1'
CRS-2672: Attempting to start 'ora.diskmon' on 'node1'
CRS-2676: Start of 'ora.diskmon' on 'node1' succeeded
CRS-2676: Start of 'ora.cssd' on 'node1' succeeded

ASM created and started successfully.

Disk Group DATA created successfully.

CRS-2672: Attempting to start 'ora.storage' on 'node1'
CRS-2676: Start of 'ora.storage' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'node1'
CRS-2676: Start of 'ora.crsd' on 'node1' succeeded
CRS-4256: Updating the profile
Successful addition of voting disk 29b0979c12194fa4bfb17214bd6d1eb0.
Successful addition of voting disk c119fba168534f44bf8f65b266814b0b.
Successful addition of voting disk 6211ad644eab4f89bfb74db2801fd61b.
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   29b0979c12194fa4bfb17214bd6d1eb0 (/dev/oracleasm/disks/DISK1) [DATA]
 2. ONLINE   c119fba168534f44bf8f65b266814b0b (/dev/oracleasm/disks/DISK2) [DATA]
 3. ONLINE   6211ad644eab4f89bfb74db2801fd61b (/dev/oracleasm/disks/DISK3) [DATA]
Located 3 voting disk(s).
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'node1'
CRS-2673: Attempting to stop 'ora.crsd' on 'node1'
CRS-2677: Stop of 'ora.crsd' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.storage' on 'node1'
CRS-2673: Attempting to stop 'ora.gpnpd' on 'node1'
CRS-2673: Attempting to stop 'ora.ctssd' on 'node1'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'node1'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'node1'
CRS-2677: Stop of 'ora.storage' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'node1'
CRS-2677: Stop of 'ora.drivers.acfs' on 'node1' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'node1' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'node1' succeeded
CRS-2677: Stop of 'ora.asm' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'node1'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'node1' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.evmd' on 'node1'
CRS-2677: Stop of 'ora.evmd' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'node1'
CRS-2677: Stop of 'ora.cssd' on 'node1' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'node1'
CRS-2677: Stop of 'ora.gipcd' on 'node1' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'node1' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'node1'
CRS-2672: Attempting to start 'ora.evmd' on 'node1'
CRS-2676: Start of 'ora.mdnsd' on 'node1' succeeded
CRS-2676: Start of 'ora.evmd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'node1'
CRS-2676: Start of 'ora.gpnpd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'node1'
CRS-2676: Start of 'ora.gipcd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'node1'
CRS-2676: Start of 'ora.cssdmonitor' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'node1'
CRS-2672: Attempting to start 'ora.diskmon' on 'node1'
CRS-2676: Start of 'ora.diskmon' on 'node1' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'node1'
CRS-2676: Start of 'ora.cssd' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'node1'
CRS-2672: Attempting to start 'ora.ctssd' on 'node1'
CRS-2676: Start of 'ora.ctssd' on 'node1' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node1'
CRS-2676: Start of 'ora.asm' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'node1'
CRS-2676: Start of 'ora.storage' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'node1'
CRS-2676: Start of 'ora.crsd' on 'node1' succeeded
CRS-6023: Starting Oracle Cluster Ready Services-managed resources
CRS-6017: Processing resource auto-start for servers: node1
CRS-6016: Resource auto-start has completed for server node1
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
2013/09/24 02:17:16 CLSRSC-343: Successfully started Oracle clusterware stack

CRS-2672: Attempting to start 'ora.asm' on 'node1'
CRS-2676: Start of 'ora.asm' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.DATA.dg' on 'node1'
CRS-2676: Start of 'ora.DATA.dg' on 'node1' succeeded
2013/09/24 02:19:08 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded
[root@Node1 etc]#

root.sh logs from Node2::
[root@Node2 etc]# /orasoft/app/grid/12.1.0/grid/root.sh
Performing root user operation for Oracle 12c

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /orasoft/app/grid/12.1.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

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 script.
Now product-specific root actions will be performed.
Using configuration parameter file: /orasoft/app/grid/12.1.0/grid/crs/install/crsconfig_params
2013/09/24 02:20:03 CLSRSC-363: User ignored prerequisites during installation

OLR initialization - successful
2013/09/24 02:20:37 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'

CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'node2'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'node2'
CRS-2677: Stop of 'ora.drivers.acfs' on 'node2' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'node2' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'node2'
CRS-2672: Attempting to start 'ora.evmd' on 'node2'
CRS-2676: Start of 'ora.mdnsd' on 'node2' succeeded
CRS-2676: Start of 'ora.evmd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'node2'
CRS-2676: Start of 'ora.gpnpd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'node2'
CRS-2676: Start of 'ora.gipcd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'node2'
CRS-2676: Start of 'ora.cssdmonitor' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'node2'
CRS-2672: Attempting to start 'ora.diskmon' on 'node2'
CRS-2676: Start of 'ora.diskmon' on 'node2' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'node2'
CRS-2676: Start of 'ora.cssd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'node2'
CRS-2672: Attempting to start 'ora.ctssd' on 'node2'
CRS-2676: Start of 'ora.ctssd' on 'node2' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node2'
CRS-2676: Start of 'ora.asm' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'node2'
CRS-2676: Start of 'ora.storage' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'node2'
CRS-2676: Start of 'ora.crsd' on 'node2' succeeded
CRS-6017: Processing resource auto-start for servers: node2
CRS-2672: Attempting to start 'ora.ons' on 'node2'
CRS-2676: Start of 'ora.ons' on 'node2' succeeded
CRS-6016: Resource auto-start has completed for server node2
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
2013/09/24 02:27:28 CLSRSC-343: Successfully started Oracle clusterware stack
2013/09/24 02:28:05 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded
[root@Node2 etc]#

If you have any failure as mentioned below during "oracle Cluster Verification Utility" safe to skip, because the DNS is not configured for SCAN. "Skip" and hit "Next"
INFO: Checking Single Client Access Name (SCAN)...
INFO: Checking name resolution setup for "node-scan"...
INFO: ERROR:
INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "rac-scan"
INFO: ERROR:
INFO: PRVF-4657 : Name resolution setup check for "node-scan" (IP address: 192.168.0.70) failed
INFO: ERROR:
INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "rac-scan"
INFO: Verification of SCAN VIP and Listener setup failed




and finally, hit the "Close". (you have successfully installed the grid infrastructure 12c(12.1.0).


Finally, check the cluster stack status as below,

[grid@Node1 bin]$ ./crsctl stat res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details      
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE  ONLINE       node1                    STABLE
               ONLINE  ONLINE       node2                    STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       node1                    STABLE
               ONLINE  ONLINE       node2                    STABLE
ora.asm
               ONLINE  ONLINE       node1                    STABLE
               ONLINE  ONLINE       node2                    Started,STABLE
ora.net1.network
               ONLINE  ONLINE       node1                    STABLE
               ONLINE  ONLINE       node2                    STABLE
ora.ons
               ONLINE  ONLINE       node1                    STABLE
               ONLINE  ONLINE       node2                    STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
      1        ONLINE  ONLINE       node1                    STABLE
ora.cvu
      1        ONLINE  ONLINE       node1                    STABLE
ora.node1.vip
      1        ONLINE  ONLINE       node1                    STABLE
ora.node2.vip
      1        ONLINE  ONLINE       node2                    STABLE
ora.oc4j
      1        OFFLINE OFFLINE                               STABLE
ora.scan1.vip
      1        ONLINE  ONLINE       node1                    STABLE
--------------------------------------------------------------------------------
[grid@Node1 bin]$

RAC DATABASE INSTALLATION

We have finished the grid infrastructure installation part and now moving to RAC RDBMS installation. Make sure all the clustered machines are up and running. Unzip the Disk1 and Disk2 in same directory and change the ownership of software to "oracle" user.
login as "oracle" OS user and start the runInstaller from unzipped software,



[oracle@Node1~]$ ./runInstaller








uncheck the "security updates checkbox" as checked by default and hit "Next"

Select "Skip software updates" and hit the "Next" button,

Select "create and configure database" and hit "Next" button, you can also use "install database software only" if you wish to create the database later.

select the server class as database installation and creation. and hit "Next" button

Select the "Oracle Real Application Clusters Database Installations"  and hit "Next" button,

The next window will take you to select the "cluster database" and select the database type as per your need. We all worked on "Admin Managed" database in earlier releases as well so i am skipping that here and going with policy managed database. provide the server pool name and cardinality and hit next.

Make sure, you have pre-configured the "ssh" between nodes because you are not prompted for ssh setup for policy managed. If not done already, here are the workaround, select the "admin managed" and hit the "Next". The next window will prompt for the ssh setup, do the ssh setup and test it. if the setup succeeded. Click on the "Back" button and again select the "policy Managed" and proceed further.

Select "Typical Installation" and hit "Next" button.

Option to select the correct directory for software installation, provide the oracle base and software location. select Storage Type "Oracle Automatic Storage Management" and provide the diskgroup name which you want to use to store the database files. pass the Global database name and supply the passwords. hit "Next" button once done with this window.

The next window will do the prerequisite checks and report any prerequisite not met, fix them and proceed for next and if any prerequisite are not mandatory, you can check the "Ignore All" and proceed with "Next" button.

The above two warnings because of DNS and i am not using here, so can be safely ignorable by clicking "Ignore All". and proceed with "Next"

Now, next windows will be summary where you have the opportunity to revalidate and if you are happy with the summary, hit "Install" button to proceed for installation.

The next will be the progressing window and wait here because the installation take while, enjoy and relax with nice cup of cappuccino coffee break.

When prompted, execute the root.sh scripts on all the specified nodes in sequence.( This is difference between 11g and 12c where in 11g the scripts is prompted after database creation.)

execution done on all the nodes, hit "OK" to proceed further and the database configuration Assistant(DBCA) will invoke automatically,

The database creation finished the DBCA will prompt you with the password management window, where you can setup the password and also give you the link for "EM Database Express URL" Note: the database control is no more available in 12c and upper releases. Click "OK" to proceed further.

The next window will be the notification for successful installed components.

and finally hit "Close" to finish the RAC database installation and creation.

You are done with database installation and configuration successfully. Happy R&D further.


*******************************END***************************************


No comments:

Post a Comment

Subscribe to: Posts (Atom)