Step-By-step Installation Guide RAC 12cR1 on Linux

8/16/2019 Step-By-step Installation Guide RAC 12cR1 on Linux

http://slidepdf.com/reader/full/step-by-step-installation-guide-rac-12cr1-on-linux 1/75

1

STEP BY STEP INSTALLATIONOF

ORACLE RAC 12cR1 (12.1.0.2)

ON LINUX X86-64

Oracle Global Customer Support - RAC / Scalability

Copyright © 1993, 2014, Oracle and/or its affiliates. All rights reserved





3

1. Introduction

1.1 Oracle Grid Infrastructure Installation Server Hardware Checklist

1.1.1 Server Hardware Checklist for Oracle Grid Infrastructure

Server hardware: server make, model, core architecture, and host bus adaptors (HBA) are supported

to run with Oracle RAC.

Network Switches:

• Public network switch, at least 1 GbE, connected to a public gateway.

• Private network switch, at least 1 GbE, with 10 GbE recommended, dedicated for use only

with other cluster member nodes. The interface must support the user datagram protocol

(UDP) using high-speed network adapters and switches that support TCP/IP. Alternatively, use

InfiniBand for the interconnect.

Runlevel: Servers should be either in runlevel 3 or runlevel 5.

Random Access Memory (RAM): At least 4 GB of RAM for Oracle Grid Infrastructure for a Cluster

installations, including installations where you plan to install Oracle RAC.

Temporary disk space allocation: At least 1 GB allocated to/tmp.

Storage hardware: Either Storage Area Network (SAN) or Network-Attached Storage (NAS).

Local Storage Space for Oracle Software

• At least 8 GB of space for the Oracle Grid Infrastructure for a cluster home (Grid home). Oracle

recommends that you allocate 100 GB to allow additional space for patches.

• At least 12 GB of space for the Oracle base of the Oracle Grid Infrastructure installation owner

(Grid user). The Oracle base includes Oracle Clusterware and Oracle ASM log files.

• For Linux x86-64 platforms, if you intend to install Oracle Database, then allocate 6.4 GB of

disk space for the Oracle home (the location for the Oracle Database software binaries).

1.1.2 Environment Configuration for Oracle Grid Infrastructure and Oracle RAC

Create Groups and Users. A user created to own only Oracle Grid Infrastructure software installations

is called the grid user. A user created to own either all Oracle installations, or only Oracle databaseinstallations, is called the oracle user.

Create mount point paths for the software binaries. Oracle recommends that you follow the

guidelines for an Optimal Flexible Architecture configuration.

Review Oracle Inventory (oraInventory) and OINSTALL Group Requirements. The Oracle Inventory

directory is the central inventory of Oracle software installed on your system. Users who have the

Oracle Inventory group as their primary group are granted the OINSTALL privilege to write to the

central inventory.

Ensure that the Grid home (the Oracle home path you select for Oracle Grid Infrastructure) uses

only ASCII characters



4

Unset Oracle software environment variables. If you have set ORA_CRS_HOME as an environment

variable, then unset it before starting an installation or upgrade. Do not use ORA_CRS_HOME as a

user environment variable.

If you have had an existing installation on your system, and you are using the same user account to

install this installation, then unset the following environment

variables: ORA_CRS_HOME;ORACLE_HOME; ORA_NLS10; TNS_ADMIN.

1.1.3 Network Configuration Tasks for Oracle Grid Infrastructure and Oracle RAC

Public Network Hardware:

• Public network switch (redundant switches recommended) connected to a public gateway and

to the public interface ports for each cluster member node.

• Ethernet interface card (redundant network cards recommended, bonded as one Ethernet

port name).

• The switches and network interfaces must be at least 1 GbE.

• The network protocol is TCP/IP.

Private Network Hardware for the Interconnect

• Private dedicated network switches (redundant switches recommended), connected to the

private interface ports for each cluster member node. NOTE: If you have more than one

private network interface card for each server, then Oracle Clusterware automatically

associates these interfaces for the private network using Grid Interprocess Communication

(GIPC) and Grid Infrastructure Redundant Interconnect, also known as Cluster High Availability

IP (HAIP).

• The switches and network interface adapters must be at least 1 GbE, with 10 GbE

recommended. Alternatively, use InfiniBand for the interconnect.

• The interconnect must support the user datagram protocol (UDP).

Oracle Flex ASM Network Hardware

• Oracle Flex ASM can use either the same private networks as Oracle Clusterware, or use its

own dedicated private networks. Each network can be classified PUBLIC or PRIVATE+ASM or

PRIVATE or ASM. ASM networks use the TCP protocol.

Cluster Names and Addresses: Determine and configure the following names and addresses for thecluster

• Cluster name: Decide a name for the cluster, and be prepared to enter it during installation.

The cluster name should have the following characteristics:

• Globally unique across all hosts, even across different DNS domains.

• At least one character long and less than or equal to 15 characters long.

• Grid Naming Service Virtual IP Address (GNS VIP): If you plan to use GNS, then configure a GNS

name and fixed address on the DNS for the GNS VIP, and configure a subdomain on your DNS

delegated to the GNS VIP for resolution of cluster addresses. GNS domain delegation is

mandatory with dynamic public networks (DHCP, autoconfiguration).





6

1. 2 Configuring Servers for Oracle Grid Infrastructure and Oracle RAC

1.2.1 Checking Server Hardware and Memory Configuration

Run the following commands to gather your current system information:

1. To determine the physical RAM size, enter the following command:

# grep MemTotal /proc/meminfo

If the size of the physical RAM installed in the system is less than the required size, then you must

install more memory before continuing.

2. To determine the size of the configured swap space, enter the following command:

# grep SwapTotal /proc/meminfo

If necessary, see your operating system documentation for information about how to configureadditional swap space.

3. To determine the amount of space available in the /tmp directory, enter the following

command:

# df -h /tmp

4. To determine the amount of free RAM and disk swap space on the system, enter the following

command:

# free

5. To determine if the system architecture can run the software, enter the following command:

# uname -m

Verify that the processor architecture matches the Oracle software release to install. For

example, you should see the following for a x86-64 bit system:

x86_64

If you do not see the expected output, then you cannot install the software on this system.

6. Verify that shared memory (/dev/shm) is mounted properly with sufficient size using the

following command:

# df -h /dev/shm



7

1.2.2 Server Storage Minimum Requirements

Each system must meet the following minimum storage requirements:

• 1 GB of space in the /tmp directory.

If the free space available in the /tmp directory is less than what is required, then complete

one of the following steps:

o Delete unnecessary files from the /tmp directory to make available the space required.

o Extend the file system that contains the /tmp directory. If necessary, contact your

system administrator for information about extending file systems.

• At least 8.0 GB of space for the Oracle Grid Infrastructure for a cluster home (Grid home).

Oracle recommends that you allocate 100 GB to allow additional space for patches.

• Upto 10 GB of additional space in the Oracle base directory of the Grid Infrastructureowner for diagnostic collections generated by Trace File Analyzer (TFA) Collector.

• At least 3.5 GB of space for the Oracle base of the Oracle Grid Infrastructure installation

owner (Grid user). The Oracle base includes Oracle Clusterware and Oracle ASM log files.

• For Oracle Solaris platforms, if you intend to install Oracle Database, then allocate 5.2 GB

of disk space for the Oracle home (the location for the Oracle Database software binaries).

1.2.3 64-bit System Memory Requirements

Each system must meet the following memory requirements:

• At least 4 GB of RAM for Oracle Grid Infrastructure for cluster installations, including

installations where you plan to install Oracle RAC.

• Swap space equivalent to the multiple of the available RAM, as indicated in the following table:

Available RAM Swap Space Required

Between 4 GB and 16 GB Equal to RAM

More than 16 GB 16 GB of RAM

1.3 Operating System Requirements for x86-64 Linux Platforms

The Linux distributions and packages listed in this section are supported for this release on x86-64. No

other Linux distributions are supported.

Identify operating system requirements for Oracle Grid Infrastructure, and identify additional

operating system requirements for Oracle Database and Oracle RAC installations.

• Supported Oracle Linux 7 and Red Hat Enterprise Linux 7 Distributions for x86-64


https://docs.oracle.com/database/121/LADBI/pre_install.htm#CIHHCIAB


https://docs.oracle.com/database/121/LADBI/pre_install.htm#BABHAEIA






8


• Supported SUSE Distributions for x86-64

1.3.1 Supported Oracle Linux 7 and Red Hat Enterprise Linux 7 Distributions for x86-64

Use the following information to check supported Oracle Linux 7 and Red Hat Linux 7 distributions:

Oracle Linux 7

Supported distributions:

• Oracle Linux 7 with the Unbreakable Enterprise kernel: 3.8.13-33.el7uek.x86_64 or later

• Oracle Linux 7 with the Red Hat Compatible kernel: 3.10.0-54.0.1.el7.x86_64 or later

Red Hat Enterprise Linux 7

Supported distribution:

• Red Hat Enterprise Linux 7: 3.10.0-54.0.1.el7.x86_64 or later

Packages for Oracle Linux 7 and Red Hat Enterprise Linux 7

binutils-2.23.52.0.1-12.el7.x86_64

compat-libcap1-1.10-3.el7.x86_64

gcc-4.8.2-3.el7.x86_64

gcc-c++-4.8.2-3.el7.x86_64

glibc-2.17-36.el7.i686

glibc-2.17-36.el7.x86_64

glibc-devel-2.17-36.el7.i686

glibc-devel-2.17-36.el7.x86_64

ksh

libaio-0.3.109-9.el7.i686

libaio-0.3.109-9.el7.x86_64

libaio-devel-0.3.109-9.el7.i686

libaio-devel-0.3.109-9.el7.x86_64

libgcc-4.8.2-3.el7.i686

libgcc-4.8.2-3.el7.x86_64libstdc++-4.8.2-3.el7.i686

libstdc++-4.8.2-3.el7.x86_64

libstdc++-devel-4.8.2-3.el7.i686

libstdc++-devel-4.8.2-3.el7.x86_64

libXi-1.7.2-1.el7.i686

libXi-1.7.2-1.el7.x86_64

libXtst-1.2.2-1.el7.i686

libXtst-1.2.2-1.el7.x86_64

make-3.82-19.el7.x86_64

sysstat-10.1.5-1.el7.x86_64

https://docs.oracle.com/database/121/LADBI/pre_install.htm#BABIBGGD


https://docs.oracle.com/database/121/LADBI/pre_install.htm#BABCGIJF








10

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)

1.3.3 Supported Oracle Linux 5 and Red Hat Enterprise Linux 5 Distributions for x86-64

Use the following information to check supported Oracle Linux 7 and Red Hat Linux 7 distributions:

Oracle Linux 5

Supported distributions:

• Oracle Linux 5 Update 6 with the Unbreakable Enterprise kernel: 2.6.32-100.0.19 or later

• Oracle Linux 5 Update 6 with the Red Hat compatible kernel: 2.6.18-238.0.0.0.1.el5 or later

Red Hat Enterprise Linux 5

Supported distribution:

• Red Hat Enterprise Linux 6: 2.6.18-238.0.0.0.1.el5 or later

Packages for Oracle Linux 5 and Red Hat Enterprise Linux 5

binutils-2.17.50.0.6

compat-libstdc++-33-3.2.3compat-libstdc++-33-3.2.3 (32 bit)

coreutils-5.97-23.el5_4.1

gcc-4.1.2

gcc-c++-4.1.2

glibc-2.5-58

glibc-2.5-58 (32 bit)

glibc-devel-2.5-58

glibc-devel-2.5-58 (32 bit)

ksh

libaio-0.3.106

libaio-0.3.106 (32 bit)

libaio-devel-0.3.106

libaio-devel-0.3.106 (32 bit)

libgcc-4.1.2

libgcc-4.1.2 (32 bit)

libstdc++-4.1.2

libstdc++-4.1.2 (32 bit)

libstdc++-devel 4.1.2

libXext-1.0.1

libXext-1.0.1 (32 bit)



11

libXtst-1.0.1

libXtst-1.0.1 (32 bit)

libX11-1.0.3

libX11-1.0.3 (32 bit)

libXau-1.0.1

libXau-1.0.1 (32 bit)

libXi-1.0.1

libXi-1.0.1 (32 bit)

make-3.81

sysstat-7.0.2

The following command can be run on the system to list the currently installed packages:

rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' binutils \

compat-libstdc++-33 \

elfutils-libelf \

elfutils-libelf-devel \gcc \

gcc-c++ \

glibc \

glibc-common \

glibc-devel \

glibc-headers \

ksh \

libaio \

libaio-devel \

libgcc \

libstdc++ \

libstdc++-devel \make \

sysstat \

unixODBC \

unixODBC-devel

Any missing RPM from the list above should be added using the "--aid" of "/bin/rpm" option to ensure

all dependent packages are resolved and installed as well.

NOTE: Be sure to check on all nodes that the Linux Firewall and SE Linux is disabled.



12

2. Prepare the cluster nodes for Oracle RAC

2.1. User Accounts

NOTE: We recommend different users for the installation of the Grid Infrastructure (GI) and the Oracle

RDBMS home. The GI will be installed in a separate Oracle base, owned by user 'grid.' After the gridinstall the GI home will be owned by root, and inaccessible to unauthorized users.

1. Create OS groups using the command below Enter commands as the root user:

#/usr/sbin/groupadd oinstall#/usr/sbin/groupadd dba#/usr/sbin/groupadd asmadmin#/usr/sbin/groupadd asmdba#/usr/sbin/groupadd asmoper

2. Create the users that will own the Oracle software using the commands:

#/usr/sbin/useradd -g oinstall -G asmadmin,asmdba,asmoper -d /home/grid -m grid#/usr/sbin/useradd -g oinstall -G dba,asmdba -d /home/oracle -m oracle

3. Set the password for the oracle account using the following command. Replace password with

your own password.

#passwd oracleChanging password for user oracle.

New UNIX password: passwordretype new UNIX password: password

passwd: all authentication tokens updated successfully.

#passwd gridChanging password for user oracle.

New UNIX password: passwordretype new UNIX password: password

passwd: all authentication tokens updated successfully

Repeat Step 1 through Step 3 on each node in your cluster.

OUI can setup passwordless SSH for you, if you want to configure this yourself, refer to Note. 300548.1

2.2 Networking

NOTE: This section is intended to be used for installations NOT using GNS.

Determine your cluster name. The cluster name should satisfy the following conditions:

• The cluster name is globally unique throughout your host domain.

• The cluster name is at least 1 character long and less than 15 characters long.

• The cluster name must consist of the same character set used for host names: single-byte

alphanumeric characters (a to z, A to Z, and 0 to 9) and hyphens (-).



13

Determine the public host name for each node in the cluster. For the public host name, use the

primary hostname of each node. In other words, use the name displayed by the hostname command

for example: racnode1.

Determine the public virtual hostname for each node in the cluster. The virtual host name is a public

node name that is used to reroute client requests sent to the node if the node is down. Oracle

recommends that you provide a name in the format <public hostname>-vip, for example: racnode1-

vip. The virtual hostname must meet the following requirements: -The virtual IP address and the

network name must not be currently in use.

• The virtual IP address must be on the same subnet as your public IP address.

• The virtual host name for each node should be registered with your DNS.

Determine the private hostname for each node in the cluster. This private hostname does not need to

be resolvable through DNS and should be entered in the /etc/hosts file. A common naming convention

for the private hostname is <public hostname>-pvt.

• The private IP should NOT be accessible to servers not participating in the local cluster.

• The private network should be on standalone dedicated switch(es).

• The private network should NOT be part of a larger overall network topology.

• The private network should be deployed on Gigabit Ethernet or better.

• It is recommended that redundant NICs are configured with the Linux bonding driver.

Active/passive is the preferred bonding method due to its simplistic configuration.

Define a SCAN DNS name for the cluster that resolves to three IP addresses (round-robin). SCAN VIPs

must NOT be in the /etc/hosts file, it must be resolved by DNS.

Even if you are using a DNS, Oracle recommends that you add lines to the /etc/hosts file on each node,

specifying the public IP, VIP and private addresses. Configure the /etc/hosts file so that it is similar to

the following example:

NOTE: The SCAN IPs MUST NOT be in the /etc/hosts file. This will result in only 1 SCAN IP for the entire

cluster.

[ oracl e@cehaovmsp145 ~] $ cat / et c/ host s# Cr eat ed by DB/ RAC OVM at Tue Aug 25 16: 59: 39 EDT 2015127. 0. 0. 1 l ocal host l ocal host . l ocal domai n l ocal host 4: : 1 l ocal host l ocal host . l ocal domai n l ocal host 6

10. 64. 146. 69 cehaovmsp145. us. oracl e. com cehaovmsp14510. 64. 131. 119 cehaovmsp145- i . us. oracl e. com cehaovmsp145- i10. 64. 146. 70 cehaovmsp145- v. us. oracl e. com cehaovmsp145- v

10. 64. 146. 92 cehaovmsp146. us. oracl e. com cehaovmsp14610. 64. 131. 120 cehaovmsp146- i . us. oracl e. com cehaovmsp146- i10. 64. 146. 93 cehaovmsp146- v. us. oracl e. com cehaovmsp146- v

# For r ef er ene: DNS I P i s 192. 135. 82. 132; SCAN Name i s cehaovmsp1- scan23



14

If you configured the IP addresses in a DNS server, then, as the root user, change the hosts search

order in /etc/nsswitch.conf on all nodes as shown here:

Old:hosts: files nis dns

New:hosts: dns files nis

After modifying the nsswitch.conf file, restart the nscd daemon on each node using the following

command:

# /sbin/service nscd restart

After you have completed the installation process, configure clients to use the SCAN to access the

cluster. Using the previous example, the clients would use docrac-scan to connect to the cluster.

The fully qualified SCAN for the cluster defaults to cluster_name-scan.GNS_subdomain_name, for

example

docrac-scan.example.com.

The short SCAN for the cluster is docrac-scan. You can use any name for the SCAN, as long as it is

unique within your network and conforms to the RFC 952 standard.

2.3. Synchronizing the Time on ALL Nodes

Ensure that the date and time settings on all nodes are set as closely as possible to the same date and

time. Time may be kept in sync with NTP with the -x option or by using Oracle Cluster Time

Synchronization Service (ctssd). Instructions on configuring NTP with the -x option can be found in My

Oracle Support Ext Note : 551704.1.

2.4 Installing the Oracle Preinstallation RPM with ULN support

Use the following procedure to subscribe to Unbreakable Linux Network (ULN) Oracle Linux channels,

and to add the Oracle Linux channel that distributes the Oracle Preinstallation RPM:

1. Register your server with Unbreakable Linux Network (ULN). By default, you are registered for

the Oracle Linux Latest channel for your operating system and hardware.

2. Log in to Unbreakable Linux Network:

https://linux.oracle.com Opens a new window

3. Click the Systems tab, and in the System Profiles list, select a registered server. The System

Details window opens and displays the subscriptions for the server.

4. Click Manage Subscriptions. The System Summary window opens.

https://linux.oracle.com/





15

5. From the Available Channels list, select the Linux installation media copy and update patch

channels corresponding to your Oracle Linux distribution. For example, if your distribution is Oracle

Linux 5 Update 6 for x86_64, then select the following:

Oracle Linux 5 Update 6 installation media copy (x86_64)

Oracle Linux 5 Update 6 Patch (x86_64)

6. Click Subscribe.

7. Start a terminal session and enter the following command as root, depending on your

platform. For example:

Oracle Linux 6:

# yum install oracle-rdbms-server-12cR1-preinstall

Oracle Linux 5:

# yum install oracle-validated

You should see output indicating that you have subscribed to the Oracle Linux channel, and that

packages are being installed. For example:

el5_u6_i386_base

el5_u6_x86_64_patch

Oracle Linux automatically creates a standard (not role-allocated) Oracle installation owner andgroups, and sets up other kernel configuration settings as required for Oracle installations.

Repeat steps 1 through 7 on all other servers in your cluster.

2.5 Configuring Kernel Parameters

Note:- This section can be ignored if you have setup the rpm using the previous steps

As the root user add the following kernel parameter settings to /etc/sysctl.conf. If any of the

parameters are already in the /etc/sysctl.conf file, the higher of the 2 values should be used.

kernel.shmmni = 4096kernel.sem = 250 32000 100 128

fs.file-max = 6553600net.ipv4.ip_local_port_range = 9000 65500net.core.rmem_default = 262144net.core.rmem_max = 4194304net.core.wmem_default = 262144net.core.wmem_max = 1048576

NOTE: The latest information on kernel parameter settings for Linux can be found in My Oracle

Support ExtNote:169706.1.

Run the following as the root user to allow the new kernel parameters to be put in place:



16

#/sbin/sysctl –p

Repeat the above steps on all cluster nodes.

NOTE: OUI checks the current settings for various kernel parameters to ensure they meet the

minimum requirements for deploying Oracle RAC.

2.6 Set shell limits for the oracle user

Note:- This section can be ignored if you have setup the rpm using the previous steps (2.4)

To improve the performance of the software on Linux systems, you must increase the shell limits for

the oracle user

1. Add the following lines to the /etc/security/limits.conf file:

grid soft nproc 2047grid hard nproc 16384grid soft nofile 1024grid hard nofile 65536oracle soft nproc 2047oracle hard nproc 16384oracle soft nofile 1024oracle hard nofile 65536

2. Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:

session required pam_limits.so

3. Make the following changes to the default shell startup file, add the following lines to the

/etc/profile file:

if [ $USER = "oracle" ] || [ $USER = "grid" ]; thenif [ $SHELL = "/bin/ksh" ]; thenulimit -p 16384ulimit -n 65536elseulimit -u 16384 -n 65536

fiumask 022

fi

For the C shell (csh or tcsh), add the following lines to the /etc/csh.login file:

if ( $USER = "oracle" || $USER = "grid" ) thenlimit maxproc 16384limit descriptors 65536endif

Repeat this procedure on all other nodes in the cluster.



17

2.7 Create the Oracle Inventory Directory

To create the Oracle Inventory directory, enter the following commands as the root user:

# mkdir -p /u01/app/oraInventory

# chown -R grid:oinstall /u01/app/oraInventory# chmod -R 775 /u01/app/oraInventory

2.7. Creating the Oracle Grid Infrastructure Home Directory

To create the Grid Infrastructure home directory, enter the following commands as the root user:

# mkdir -p /u01/app/12.1.0/grid# chown -R grid:oinstall //u01/app/12.1.0/grid# chmod -R 775 /u01/app/12.1.0/grid

2.8. Creating the Oracle Base Directory

To create the Oracle Base directory, enter the following commands as the root user:

# mkdir -p /u01/app/oracle# mkdir /u01/app/oracle/cfgtoollogs --needed to ensure that dbca is able to run after the rdbmsinstallation.# chown -R oracle:oinstall /u01/app/oracle# chmod -R 775 /u01/app/oracle

2.9. Creating the Oracle RDBMS Home Directory

To create the Oracle RDBMS Home directory, enter the following commands as the root user:

# mkdir -p /u01/app/oracle/product/12.1.0/db_1# chown -R oracle:oinstall /u01/app/oracle/product/12.1.0/db_1# chmod -R 775 /u01/app/oracle/product/12.1.0/db_1

2.10. Stage the Oracle Software

It is recommended that you stage the required software onto a local drive on Node 1 of your cluster.

Starting with the first patch set for Oracle Database 12c Release 1 (12.1.0.2), Oracle Database patch

sets are full installations of the Oracle Database software. In past releases, Oracle Database patch sets

consisted of sets of files that replaced files in an existing Oracle home.

Oracle Database 12c Release 1, patch sets are full (out-of-place) installations that replace existing

installations. This simplifies the installation since you may simply install the latest patch set (version).

You are no longer required to install the base release, and then apply the patch set.



18

3. Prepare the shared storage for Oracle RAC

This section describes how to prepare the shared storage for Oracle RAC

Each node in a cluster requires external shared disks for storing the Oracle Clusterware (Oracle Cluster

Registry and voting disk) files, and Oracle Database files. To ensure high availability of OracleClusterware files on Oracle ASM, you need to have at least 2 GB of disk space for Oracle Clusterware

files in three separate failure groups, with at least three physical disks. Each disk must have at least 1

GB capacity to ensure that there is sufficient space to create Oracle Clusterware files. Use the

following guidelines when identifying appropriate disk devices:

All of the devices in an Automatic Storage Management diskgroup should be the same size and have

the same performance characteristics.

A diskgroup should not contain more than one partition on a single physical disk device.

Using logical volumes as a device in an Automatic Storage Management diskgroup is not supportedwith Oracle RAC.

The user account with which you perform the installation (typically, 'oracle') must have write

permissions to create the files in the path that you specify.

3.1. Shared Storage

For this example installation we will be using ASM for Clusterware and Database storage on top of

SAN technology. The following Table shows the storage layout for this implementation:

3.1.1. Partition the Shared Disks

Once the LUNs have been presented from the SAN to ALL servers in the cluster, partition the LUNs

from one node only, run fdisk to create a single whole-disk partition with exactly 1 MB offset on each

LUN to be used as ASM Disk.

Tip: From the fdisk prompt, type "u" to switch the display unit from cylinder to sector. Then create a

single primary partition starting on sector 2048 (1MB offset assuming sectors of 512 bytes per unit).

See below:-

fdisk /dev/sda

Command (m for help): u

Changing display/entry units to sectorsCommand (m for help): nCommand actione extended

p primary partition (1-4) p

Partition number (1-4): 1

First sector (61-1048575, default 61): 2048

Last sector or +size or +sizeM or +sizeK (2048-1048575, default 1048575):Using default value 1048575

Command (m for help): wThe partition table has been altered!



19

Calling ioctl() to re-read partition table.Syncing disks.

2. Load the updated block device partition tables by running the following on ALL servers

participating in the cluster:

#/sbin/partprobe

3.1.2. Installing and Configuring ASMLib

The ASMLib is highly recommended for those systems that will be using ASM for shared storage within

the cluster due to the performance and manageability benefits that it provides. Perform the following

steps to install and configure ASMLib on the cluster nodes:

NOTE: ASMLib automatically provides LUN persistence, so when using ASMLib there is no need to

manually configure LUN persistence for the ASM devices on the system.

Download the following packages from the ASMLib OTN page, if you are an Enterprise Linux customeryou can obtain the software through the Unbreakable Linux network.

NOTE: The ASMLib kernel driver MUST match the kernel revision number, the kernel revision

number of your system can be identified by running the "uname -r" command. Also, be sure to

download the set of RPMs which pertain to your platform architecture, in our case this is x86_64.

oracleasm-support-2.1.3-1.el5x86_64.rpmoracleasmlib-2.0.4-1.el5.x86_64.rpmoracleasm-2.6.18-92.1.17.0.2.el5-2.0.5-1.el5.x86_64.rpm

Install the RPMs by running the following as the root user:

# rpm -ivh oracleasm-support-2.1.3-1.el5x86_64.rpm \oracleasmlib-2.0.4-1.el5.x86_64.rpm \oracleasm-2.6.18-92.1.17.0.2.el5-2.0.5-1.el5.x86_64.rpm

3. Configure ASMLib by running the following as the root user:

NOTE: If using user and group separation for the installation (as documented here), the ASMLib driver

interface owner is 'grid' and the group to own the driver interface is 'asmadmin'. These groups were

created in section 2.1. If a more simplistic installation using only the Oracle user is performed, the

owner will be 'oracle' and the group owner will be 'dba'.

#/etc/init.d/oracleasm configure

Configuring the Oracle ASM library driver.This will configure the on-boot properties of the Oracle ASM library driver. The following questionswill determine whether the driver is loaded on boot and what permissions it will have. The currentvalues will be shown in brackets ('[]'). Hitting <ENTER> without typing an answer will keep thatcurrent value. Ctrl-C will abort.

Default user to own the driver interface []: grid

Default group to own the driver interface []: asmadmin

Start Oracle ASM library driver on boot (y/n) [n]: yScan for Oracle ASM disks on boot (y/n) [y]: yWriting Oracle ASM library driver configuration: done

Initializing the Oracle ASMLib driver: [ OK ]Scanning the system for Oracle ASMLib disks: [ OK ]



20

4. Repeat steps 2 - 4 on ALL cluster nodes.

3.1.3. Using ASMLib to Mark the Shared Disks as Candidate Disks

To create ASM disks using ASMLib:

1. As the root user, use oracleasm to create ASM disks using the following syntax:

# /usr/sbin/oracleasm createdisk disk_name device_partition_name

In this command, disk_name is the name you choose for the ASM disk. The name you choose must

contain only ASCII capital letters, numbers, or underscores, and the disk name must start with a letter,

for example,DISK1 or VOL1, or RAC_FILE1. The name of the disk partition to mark as an ASM disk is the

device_partition_name. For example:

[root@cehaovmsp145 ~]# /usr/sbin/oracleasm createdisk OCR_VOTE01 /dev/xvdc1

Writing disk header: done Instantiating disk: done[root@cehaovmsp145 ~]# /usr/sbin/oracleasm createdisk OCR_VOTE02 /dev/xvdd1Writing disk header: done

Instantiating disk: done[root@cehaovmsp145 ~]# /usr/sbin/oracleasm createdisk DG01 /dev/xvde1Writing disk header: done

Instantiating disk: done[root@cehaovmsp145 ~]# /usr/sbin/oracleasm createdisk DG02 /dev/xvdf1Writing disk header: done

Instantiating disk: done[root@cehaovmsp145 ~]# /usr/sbin/oracleasm createdisk DG03 /dev/xvdg1

Writing disk header: done Instantiating disk: done

If you need to unmark a disk that was used in a createdisk command, you can use the following syntax

as the root user:

# /usr/sbin/oracleasm deletedisk disk_name

2. Repeat step 1 for each disk that will be used by Oracle ASM.

3. After you have created all the ASM disks for your cluster, use the listdisks command to verify their

availability:

[root@cehaovmsp145 ~]# /usr/sbin/oracleasm scandisks Reloading disk partitions: doneCleaning any stale ASM disks...Scanning system for ASM disks...[root@cehaovmsp145 ~]# /usr/sbin/oracleasm listdisks

DG01 DG02 DG03OCR_VOTE01OCR_VOTE02

[root@cehaovmsp145 ~]#



21

4. On all the other nodes in the cluster, use the scandisks command as the root user to pickup the

newly created ASM disks. You do not need to create the ASM disks on each node, only on one node in

the cluster.

[root@cehaovmsp146 ~]# /usr/sbin/oracleasm scandisks Reloading disk partitions: doneCleaning any stale ASM disks...Scanning system for ASM disks...

Instantiating disk "OCR_VOTE01" Instantiating disk "OCR_VOTE02" Instantiating disk "DG01" Instantiating disk "DG02" Instantiating disk "DG03"

5. After scanning for ASM disks, display the available ASM disks on each node to verify their

availability:

[root@cehaovmsp146 ~]# /usr/sbin/oracleasm listdisks DG01 DG02 DG03OCR_VOTE01OCR_VOTE02[root@cehaovmsp146 ~]#

3.2 Setting Disk I/O Scheduler on Linux

Disk I/O schedulers reorder, delay, or merge requests for disk I/O to achieve better throughput and

lower latency. Linux has multiple disk I/O schedulers available, including Deadline, Noop, Anticipatory,and Completely Fair Queuing (CFQ). For best performance for Oracle ASM, Oracle recommends that

you use the Deadline I/O Scheduler.

Enter the following command to ensure that the Deadline disk I/O scheduler is configured for use:

# echo deadline > /sys/block/${ASM_DISK}/queue/scheduler



22

4. Oracle Grid Infrastructure Install

Basic Grid Infrastructure Install (without GNS and IPMI)

As the grid user (Grid Infrastructure software owner) start the installer by running "runInstaller" from

the staged installation media.

NOTE: Be sure the installer is run as the intended software owner, the only supported method to

change the software owner is to reinstall.

#xhost +#su - grid

cd into the folder where you staged the Grid Infrastructure software

./runInstaller

Action:

Select radio button 'Install and Configure Grid Infrastructure for a Cluster' and click ' Next> '



23

Action:

Select radio button 'Advanced Installation' and click ' Next> '



24

Action:

Accept 'English' as language' and click ' Next> '



25

Action:

Specify your cluster name and the SCAN name you want to use and click ' Next> '

Note:

Make sure 'Configure GNS' is NOT selected.



26

Action:

Use the Edit and Add buttons to specify the node names and virtual IP addresses you configured

previously in your /etc/hosts file. Use the 'SSH Connectivity' button to configure/test the

passwordless SSH connectivity between your nodes.

ACTION:

Type in the OS password for the user 'grid' and press 'Setup'



27

After click ' OK '

Action:

Click on 'Interface Type' next to the Interfaces you want to use for your cluster and select the correctvalues for 'Public' and 'Private' and '. When finished click ' Next> '



28

Action:

Select radio button 'Automatic Storage Management (ASM) and click ' Next> '



29

Action:

Select the 'DiskGroup Name' specify the 'Redundancy' and tick the disks you want to use, when done

click ' Next> '

NOTE: The number of voting disks that will be created depend on the redundancy level you specify:

EXTERNAL will create 1 voting disk, NORMAL will create 3 voting disks, HIGH will create 5 voting disks.

NOTE: If you see an empty screen for your candidate disks it is likely that ASMLib has not been

properly configured. If you are sure that ASMLib has been properly configured click on 'Change

Discovery Path' and provide the correct destination.



30

Action:

Specify and conform the password you want to use and click ' Next> '



31

Action:

Select NOT to use IPMI and click ' Next> '



32

Action:

Select if you wish to Register with EM Cloud control and click ' Next> '



33

Action:

Assign the correct OS groups for OS authentication and click ' Next> '



34

Action:

Specify the locations for your ORACLE_BASE and for the Software location and click ' Next> '



35

Action:

Specify the locations for your Inventory directory and click ' Next> '



36

Action:

Specify the required credential if you wish to automatically run configuration scripts and click 'Next> '



37

Action:

Check that status of all checks is Succeeded and click ' Next> '

Note:

If you have failed checks marked as 'Fixable' click 'Fix & Check again'. This will bring up the window

Action:

Execute the runfixup.sh script as described on the screen as root user





39

Database Conf i gur at i on Assi st ant when a dat abase i s cr eat edFi ni shed r unni ng gener i c par t of r oot scri pt .Now pr oduct - speci f i c r oot act i ons wi l l be per f ormed.Usi ng conf i gur at i on par amet er f i l e: / u01/ app/ 12. 1. 0/ gr i d/ crs/ i nst al l / crsconf i g_par ams2015/ 09/ 12 20: 44: 44 CLSRSC- 4001: I nst al l i ng Or acl e Tr ace Fi l e Anal yzer ( TFA) Col l ect or.

2015/ 09/ 12 20: 45: 19 CLSRSC- 4002: Successf ul l y i nst al l ed Or acl e Trace Fi l e Anal yzer ( TFA)Col l ector.

2015/ 09/ 12 20: 45: 21 CLSRSC- 363: User i gnored pr erequi si t es dur i ng i nstal l ati on

OLR i ni t i al i zat i on - successfulroot wal l etroot wal l et cer tr oot cert expor tpeer wal l etprof i l e reader wal l etpa wal l etpeer wal l et keyspa wal l et keyspeer cert r equestpa cer t r equestpeer certpa cer t

peer r oot cer t TPpr ofi l e r eader r oot cer t TPpa r oot cert TPpeer pa cert TPpa peer cert TPpr of i l e r eader pa cer t TPpr of i l e r eader peer cer t TPpeer user certpa user cer t

2015/ 09/ 12 20: 46: 13 CLSRSC- 330: Addi ng Cl ust er war e ent r i es t o fi l e ' / et c/ i ni t t ab'

CRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: Or acl e Hi gh Avai l abi l i t y Servi ces has been st ar t ed.CRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: Or acl e Hi gh Avai l abi l i t y Servi ces has been st ar t ed.CRS- 2672: At t empt i ng t o st art ' ora. evmd' on ' cehaovmsp145'CRS- 2672: At t empt i ng t o st art ' ora. mdnsd' on ' cehaovmsp145'

CRS- 2676: Star t of ' ora. mdnsd' on ' cehaovmsp145' succeededCRS- 2676: Star t of ' ora. evmd' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng t o st art ' ora. gpnpd' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. gpnpd' on ' cehaovmsp145' succeededCRS- 2672: At t empti ng t o st art ' ora. cssdmoni t or' on ' cehaovmsp145'CRS- 2672: At t empti ng t o st art ' ora. gi pcd' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. cssdmoni t or ' on ' cehaovmsp145' succeededCRS- 2676: Star t of ' ora. gi pcd' on ' cehaovmsp145' succeededCRS- 2672: At t empti ng t o st art ' ora. cssd' on ' cehaovmsp145'CRS- 2672: At t empt i ng t o st art ' ora. di skmon' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. di skmon' on ' cehaovmsp145' succeededCRS- 2676: Star t of ' ora. cssd' on ' cehaovmsp145' succeeded

ASM cr eated and st art ed successf ul l y.

Di sk Gr oup OCRVD cr eat ed successf ul l y.

CRS- 2672: At t empti ng t o st art ' ora. cr f ' on ' cehaovmsp145'CRS- 2672: At t empti ng t o st art ' ora. st orage' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. st orage' on ' cehaovmsp145' succeededCRS- 2676: St art of ' ora. cr f ' on ' cehaovmsp145' succeededCRS- 2672: At t empti ng t o st art ' ora. cr sd' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. cr sd' on ' cehaovmsp145' succeededCRS- 4256: Updat i ng the pr of i l eSuccessf ul addi t i on of vot i ng di sk ae201939c23b4f 12bf57f ceabf 2ad60f .Successf ul l y repl aced vot i ng di sk gr oup wi t h +OCRVD.CRS- 4256: Updat i ng the pr of i l eCRS- 4266: Vot i ng f i l e( s) successf ul l y r epl aced## STATE Fi l e Uni ver sal I d Fi l e Name Di sk gr oup- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1. ONLI NE ae201939c23b4f 12bf 57f ceabf 2ad60f ( / dev/ oracl easm/ di sks / OCR_VOTE01) [ OCRVD]

Locat ed 1 vot i ng di sk(s) .CRS- 2791: St art i ng shutdown of Or acl e Hi gh Avai l abi l i t y Servi ces- managed r esour ces on' cehaovmsp145'CRS- 2673: At t empt i ng t o st op ' ora. cr sd' on ' cehaovmsp145'CRS-2677: Stop of ' ora. cr sd' on ' cehaovmsp145' succeeded



40

CRS- 2673: At t empt i ng t o st op ' ora. ct ssd' on ' cehaovmsp145'CRS-2673: At t empt i ng t o st op ' ora. evmd' on ' cehaovmsp145'CRS-2673: At t empt i ng t o st op ' ora. st orage' on ' cehaovmsp145'CRS-2673: At t empt i ng t o st op ' ora. mdnsd' on ' cehaovmsp145'CRS-2673: At t empt i ng t o st op ' ora. gpnpd' on ' cehaovmsp145'CRS- 2673: At t empt i ng t o stop ' ora. dri ver s. acf s' on ' cehaovmsp145'CRS-2677: Stop of ' ora. st orage' on ' cehaovmsp145' succeededCRS-2673: At t empt i ng t o st op ' ora. asm' on ' cehaovmsp145'

CRS- 2677: Stop of ' ora. dr i ver s. acf s' on ' cehaovmsp145' succeededCRS-2677: Stop of ' ora. ct ssd' on ' cehaovmsp145' succeededCRS- 2677: Stop of ' or a. evmd' on ' cehaovmsp145' succeededCRS- 2677: Stop of ' or a. mdnsd' on ' cehaovmsp145' succeededCRS- 2677: Stop of ' or a. gpnpd' on ' cehaovmsp145' succeededCRS- 2677: Stop of ' or a. asm' on ' cehaovmsp145' succeededCRS- 2673: Att empt i ng t o st op ' ora. cl ust er_ i nter connect. hai p' on ' cehaovmsp145'CRS- 2677: Stop of ' ora. cl uster _i nt erconnect. hai p' on ' cehaovmsp145' succeededCRS-2673: At t empt i ng t o st op ' ora. cssd' on ' cehaovmsp145'CRS-2677: Stop of ' ora. cssd' on ' cehaovmsp145' succeededCRS- 2673: At t empt i ng to st op ' ora. cr f ' on ' cehaovmsp145'CRS-2677: Stop of ' ora. cr f ' on ' cehaovmsp145' succeededCRS-2673: At t empt i ng t o st op ' ora. gi pcd' on ' cehaovmsp145'CRS-2677: Stop of ' ora. gi pcd' on ' cehaovmsp145' succeededCRS-2793: Shutdown of Or acl e Hi gh Avai l abi l i t y Ser vi ces- managed r esour ces on ' cehaovmsp145' hascompl et ed

CRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: St art i ng Or acl e Hi gh Avai l abi l i t y Servi ces- managed r esourcesCRS-2672: At t empt i ng t o st art ' ora. mdnsd' on ' cehaovmsp145'CRS-2672: At t empt i ng t o st art ' ora. evmd' on ' cehaovmsp145'CRS-2676: Start of ' ora. mdnsd' on ' cehaovmsp145' succeededCRS-2676: Start of ' ora. evmd' on ' cehaovmsp145' succeededCRS-2672: At t empt i ng t o st art ' ora. gpnpd' on ' cehaovmsp145'CRS-2676: Start of ' ora. gpnpd' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng to st art ' ora. gi pcd' on ' cehaovmsp145'CRS-2676: Start of ' ora. gi pcd' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng t o st art ' ora. cssdmoni t or' on ' cehaovmsp145'CRS-2676: Start of ' ora. cssdmoni t or ' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng to st art ' ora. cssd' on ' cehaovmsp145'CRS-2672: At t empt i ng t o st art ' ora. di skmon' on ' cehaovmsp145'CRS-2676: Start of ' ora. di skmon' on ' cehaovmsp145' succeededCRS-2676: Start of ' ora. cssd' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng t o st ar t ' ora. cl ust er_i nt erconnect . hai p' on ' cehaovmsp145'

CRS- 2672: At t empt i ng to st art ' ora. ct ssd' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. ct ssd' on ' cehaovmsp145' succeededCRS- 2676: St art of ' ora. cl ust er_ i nt erconnect . hai p' on ' cehaovmsp145' succeededCRS-2672: At t empt i ng t o st art ' ora. asm' on ' cehaovmsp145'CRS-2676: Start of ' ora. asm' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng to st art ' ora. st orage' on ' cehaovmsp145'CRS-2676: Start of ' ora. st orage' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng t o start ' ora. cr f ' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. cr f ' on ' cehaovmsp145' succeededCRS- 2672: At t empt i ng to st art ' ora. cr sd' on ' cehaovmsp145'CRS- 2676: Star t of ' ora. cr sd' on ' cehaovmsp145' succeededCRS-6023: Start i ng Or acl e Cl ust er Ready Servi ces- managed r esour cesCRS- 6017: Processi ng r esource aut o- st art f or servers: cehaovmsp145CRS- 6016: Resource aut o- st ar t has compl eted f or ser ver cehaovmsp145CRS-6024: Compl eted st art of Or acl e Cl ust er Ready Servi ces- managed r esour cesCRS- 4123: Or acl e Hi gh Avai l abi l i t y Servi ces has been star t ed.

2015/ 09/ 12 20: 51: 49 CLSRSC- 343: Successf ul l y st art ed Or acl e Cl ust erware st ack

CRS-2672: At t empt i ng t o st art ' ora. asm' on ' cehaovmsp145'CRS-2676: Start of ' ora. asm' on ' cehaovmsp145' succeededCRS-2672: At t empt i ng t o st art ' ora. OCRVD. dg' on ' cehaovmsp145'CRS-2676: Start of ' ora. OCRVD. dg' on ' cehaovmsp145' succeeded2015/09/12 20:53:00 CLSRSC-325: Configure Oracle Grid Infrastructure for a

Cluster ... succeeded

[ r oot @cehaovmsp146 ~] # / u01/ app/ oraI nvent ory/ orai nstRoot . sh

root.sh script output on Node 2

Changi ng permi ssi ons of / u01/ app/ oraI nvent ory.Addi ng read, wr i t e permi ssi ons f or gr oup.

Removi ng r ead, wr i t e, execut e per mi ssi ons f or worl d.Changi ng gr oupname of / u01/ app/ oraI nvent ory t o oi nstal l . The execut i on of t he scr i pt i s compl et e.



41

[ r oot @cehaovmsp146 ~] # / u01/ app/ 12. 1. 0/ gr i d/ r oot . shPer f ormi ng root user oper ati on.

The f ol l owi ng envi r onment var i abl es ar e set as:ORACLE_OWNER= gr i dORACLE_HOME= / u01/ app/ 12. 1. 0/ gri d

Ent er t he f ul l pat hname of t he l ocal bi n di rect ory: [ / usr/ l ocal / bi n] :

The cont ents of "dbhome" have not changed. No need t o overwr i t e. The cont ents of "or aenv" have not changed. No need t o overwr i t e. The cont ents of "cor aenv" have not changed. No need t o over wr i t e.

Creat i ng / etc/ oratab f i l e. . .Ent r i es wi l l be added t o the / et c/ orat ab fi l e as needed byDatabase Conf i gur at i on Assi st ant when a dat abase i s cr eat edFi ni shed r unni ng gener i c par t of r oot scri pt .Now pr oduct - speci f i c r oot act i ons wi l l be per f ormed.Usi ng conf i gur at i on par amet er f i l e: / u01/ app/ 12. 1. 0/ gr i d/ crs/ i nst al l / crsconf i g_par ams2015/ 09/ 12 21: 02: 53 CLSRSC- 4001: I nst al l i ng Or acl e Tr ace Fi l e Anal yzer ( TFA) Col l ect or.

2015/ 09/ 12 21: 03: 23 CLSRSC- 4002: Successf ul l y i nst al l ed Or acl e Trace Fi l e Anal yzer ( TFA)Col l ector.

2015/ 09/ 12 21: 03: 25 CLSRSC- 363: User i gnored pr erequi si t es dur i ng i nstal l ati on

OLR i ni t i al i zat i on - successful2015/ 09/ 12 21: 05: 12 CLSRSC- 330: Addi ng Cl ust er war e ent r i es t o fi l e ' / et c/ i ni t t ab'CRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: Or acl e Hi gh Avai l abi l i t y Servi ces has been st ar t ed.CRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: Or acl e Hi gh Avai l abi l i t y Servi ces has been st ar t ed.CRS- 2791: St art i ng shutdown of Or acl e Hi gh Avai l abi l i t y Servi ces- managed r esour ces on' cehaovmsp146'CRS- 2673: At t empti ng t o st op ' ora. dr i ver s. acf s' on ' cehaovmsp146'CRS- 2677: St op of ' ora. dr i ver s. acf s' on ' cehaovmsp146' succeededCRS- 2793: Shutdown of Or acl e Hi gh Avai l abi l i t y Ser vi ces- managed r esour ces on ' cehaovmsp146' hascompl et edCRS- 4133: Or acl e Hi gh Avai l abi l i t y Servi ces has been st opped.CRS- 4123: St art i ng Or acl e Hi gh Avai l abi l i t y Servi ces- managed r esourcesCRS- 2672: At t empt i ng t o st art ' ora. mdnsd' on ' cehaovmsp146'CRS- 2672: At t empt i ng t o st art ' ora. evmd' on ' cehaovmsp146'

CRS- 2676: Star t of ' ora. mdnsd' on ' cehaovmsp146' succeededCRS- 2676: Star t of ' ora. evmd' on ' cehaovmsp146' succeededCRS- 2672: At t empt i ng t o st art ' ora. gpnpd' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. gpnpd' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. gi pcd' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. gi pcd' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. cssdmoni t or' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. cssdmoni t or ' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. cssd' on ' cehaovmsp146'CRS- 2672: At t empt i ng t o st art ' ora. di skmon' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. di skmon' on ' cehaovmsp146' succeededCRS- 2676: Star t of ' ora. cssd' on ' cehaovmsp146' succeededCRS- 2672: At t empt i ng t o st ar t ' ora. cl ust er _i nt er connect . hai p' on ' cehaovmsp146'CRS- 2672: At t empti ng t o st art ' ora. ct ssd' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. ct ssd' on ' cehaovmsp146' succeededCRS- 2676: St art of ' ora. cl ust er_ i nter connect. hai p' on ' cehaovmsp146' succeeded

CRS- 2672: At t empt i ng t o st art ' ora. asm' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. asm' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. st orage' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. st orage' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. cr f ' on ' cehaovmsp146'CRS- 2676: St art of ' ora. cr f ' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. cr sd' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. cr sd' on ' cehaovmsp146' succeededCRS- 6017: Processi ng r esour ce aut o- st art f or servers: cehaovmsp146CRS- 2672: At t empti ng t o st art ' ora. net1. network' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. net 1. net work' on ' cehaovmsp146' succeededCRS- 2672: At t empti ng t o st art ' ora. ons' on ' cehaovmsp146'CRS- 2676: Star t of ' ora. ons' on ' cehaovmsp146' succeededCRS- 6016: Resource auto- st ar t has compl et ed f or ser ver cehaovmsp146CRS- 6024: Compl eted st art of Or acl e Cl ust er Ready Servi ces- managed r esour cesCRS- 4123: Or acl e Hi gh Avai l abi l i t y Ser vi ces has been star t ed.2015/ 09/ 12 21: 08: 43 CLSRSC- 343: Successf ul l y st art ed Or acl e Cl ust erware st ack

2015/09/12 21:09:00 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ...

succeeded



42

Action:

Wait for the OUI to finish the cluster configuration.



43

Action:

You should see the confirmation that installation of the Grid Infrastructure was successful. Click 'Close'

to finish the install.

[ r oot @cehaovmsp145 ~] # cr sct l st at r es - t- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Name Tar get St ate Server Stat e det ai l s- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Local Resour ces- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -ora. LI STENER. l snr

ONLI NE ONLI NE cehaovmsp145 STABLEONLI NE ONLI NE cehaovmsp146 STABLE

or a. OCRVD. dg

ONLI NE ONLI NE cehaovmsp145 STABLEONLI NE ONLI NE cehaovmsp146 STABLEor a. asm ONLI NE ONLI NE cehaovmsp145 STABLE

ONLI NE ONLI NE cehaovmsp146 St ar t ed, STABLEora. net 1. network

ONLI NE ONLI NE cehaovmsp145 STABLEONLI NE ONLI NE cehaovmsp146 STABLE

ora. onsONLI NE ONLI NE cehaovmsp145 STABLEONLI NE ONLI NE cehaovmsp146 STABLE



44

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Cl ust er Resour ces- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -ora. LI STENER_SCAN1. l snr

1 ONLI NE ONLI NE cehaovmsp145 STABLEor a. MGMTLSNR

1 ONLI NE ONLI NE cehaovmsp145 169. 254. 41. 177 10. 64. 131. 119, STABLE

or a. cehaovmsp145. vi p1 ONLI NE ONLI NE cehaovmsp145 STABLE

or a. cehaovmsp146. vi p1 ONLI NE ONLI NE cehaovmsp146 STABLE

ora. cvu1 ONLI NE ONLI NE cehaovmsp145 STABLE

or a. mgmt db1 ONLI NE ONLI NE cehaovmsp145 Open, STABLE

or a. oc4j1 ONLI NE ONLI NE cehaovmsp145 STABLE

or a. scan1. vi p1 ONLI NE ONLI NE cehaovmsp145 STABLE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -[ r oot @cehaovmsp145 ~] # ocr checkSt at us of Or acl e Cl ust er Regi st r y i s as f ol l ows :

Versi on : 4

Tot al space ( kbyt es) : 409568Used space ( kbyt es) : 1456Avai l abl e space ( kbyt es) : 408112I D : 1201040793Devi ce/ Fi l e Name : +OCRVD

Devi ce/ Fi l e i nt egr i t y check succeeded

Devi ce/ Fi l e not conf i gur ed




Cl ust er r egi st r y i nt egr i t y check succeeded

Logi cal corr upti on check succeeded

[ r oot @cehaovmsp145 ~] # cr sct l query css vot edi sk## STATE Fi l e Uni ver sal I d Fi l e Name Di sk group- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1. ONLI NE ae201939c23b4f 12bf 57f ceabf 2ad60f ( / dev/ or acl easm/ di sks / OCR_VOTE01) [OCRVD]

Locat ed 1 vot i ng di sk(s) .

[ r oot @cehaovmsp145 ~] # cr sct l check cl ust er - al l**************************************************************cehaovmsp145:CRS- 4537: Cl ust er Ready Servi ces i s onl i neCRS- 4529: Cl ust er Synchr oni zati on Ser vi ces i s onl i neCRS-4533: Event Manager i s onl i ne**************************************************************cehaovmsp146:

CRS- 4537: Cl ust er Ready Servi ces i s onl i neCRS- 4529: Cl ust er Synchr oni zati on Ser vi ces i s onl i neCRS-4533: Event Manager i s onl i ne**************************************************************



45

5. RDBMS Software Install

As the oracle user (rdbms software owner) start the installer by running "runInstaller" from the staged

installation media.

NOTE: Be sure the installer is run as the intended software owner, the only supported method tochange the software owner is to reinstall.

Change into the directory where you staged the RDBMS software

./runInstaller

Action:

Provide your e-mail address, tick the check box and provide your Oracle Support Password if you want

to receive Security Updates from Oracle Support and click ' Next> '



46

Action:

Select the option 'Install Database software only' and click ' Next> '



47

Action:

Select the option Oracle Real Application Clusters database Installation' and click ' Next> '



48

Action:

Select all nodes.

Use the 'SSH Connectivity' button to configure/test the passwordless SSH connectivity between your

nodes '

Type in the OS password for the oracle user and click 'Setup'



49

Action:

To confirm English as selected language click ' Next> '



50

Action:

Make sure radio button 'Enterprise Edition' is ticked, click ' Next> '



51

Action:

Specify path to your Oracle Base and below to the location where you want to store the software

(Oracle home). Click ' Next> '



52

Action:

Use the drop down menu to select the names of the Database Administrators and Database Operators

group and click ' Next> '



53

Action:

Check that the status of all checks is 'Succeeded' and click ' Next> '

Note:

If you are sure the unsuccessful checks can be ignored tick the box 'Ignore All' before you click ' Next> '



54

Action:

Perform last check that the information on the screen is correct before you click ' Finish '



55

Action:

Log in to a terminal window as root user and run the root.sh script on the first node. When finished do

the same for all other nodes in your cluster as well. When finished click 'OK'

NOTE: root.sh should be run on one node at a time.[ r oot @cehaovmsp145 ~] # / u01/ app/ oracl e/ product / 12. 1. 0/ db_1/ r oot. sh

Perf ormi ng root user oper ati on.

The f ol l owi ng envi r onment var i abl es are set as:

ORACLE_OWNER= or acl e

ORACLE_HOME= / u01/app/or acl e/ product / 12. 1. 0/db_1

Enter the f ul l pathname of t he l ocal bi n di rectory: [ / usr/ l ocal/ bin]:

The cont ents of "dbhome" have not changed. No need t o overwr i t e.

The cont ents of "oraenv" have not changed. No need t o overwr i t e.

The cont ents of " cor aenv" have not changed. No need t o overwr i t e.

Ent ri es wi l l be added to the /et c/ oratab fi l e as needed by

Database Conf i gur ati on Assi st ant when a dat abase i s cr eat ed

Fi ni shed runni ng generi c part of r oot scri pt.

Now product- speci f i c r oot acti ons wi l l be perf ormed.

[ r oot @cehaovmsp146 ~] # / u01/ app/ oracl e/ product / 12. 1. 0/ db_1/ r oot. sh

Perf ormi ng root user oper ati on.

The f ol l owi ng envi r onment var i abl es are set as:

ORACLE_OWNER= or acl e

ORACLE_HOME= / u01/app/or acl e/ product / 12. 1. 0/db_1

Enter the f ul l pathname of t he l ocal bi n di rectory: [ / usr/ l ocal/ bin]:

The cont ents of "dbhome" have not changed. No need t o overwr i t e.

The cont ents of "oraenv" have not changed. No need t o overwr i t e.

The cont ents of " cor aenv" have not changed. No need t o overwr i t e.

Ent ri es wi l l be added to the /et c/ oratab fi l e as needed by

Database Conf i gur ati on Assi st ant when a dat abase i s cr eat ed

Fi ni shed runni ng generi c part of r oot scri pt.

Now product- speci f i c root acti ons wi l l be perf ormed.



56

Action:

Click ' Close ' to finish the installation of the RDBMS Software.



57

6. ASMCA to create Diskgroups

As the grid user start the ASM Configuration Assistant (ASMCA)

$ cd /u01/app/12.1.0/grid/bin

./asmca

Action:

Click 'Create' to create a new diskgroup



58

Type in a name for the diskgroup, select the redundancy you want to provide and mark the tick box

for the disks you want to assign to the new diskgroup.



59

Action:

Click 'OK'

Note:

It is Oracle's Best Practice to have an OCR mirror stored in a second diskgroup. To follow these

recommendations add an OCR mirror. Mind that you can only have one OCR in a diskgroup.

Action:

1. To add OCR mirror to an Oracle ASM diskgroup, ensure that the Oracle Clusterware stack is running

and run the following command as root from the $GRID_HOME /bin directory:

2. # ocrconfig -add +DATA

3. # ocrcheck



60

7. Run DBCA to create the database

As the oracle user start the Database Configuration Assistant (DBCA)

cd /u01/app/oracle/product/12.1.0/db_1/bin

./dbca

Action:

Choose option 'Create a Database' and click 'Next'



61

Action:

Choose option 'Advanced Mode' and click 'Next >'



62

Action:

Select 'Oracle Real Application Clusters (RAC) database' and ‘Admin Managed’ click 'Next'



63

Action:

Type in the name you want to use for your database and select “Create As Container Database” click

'Next >'



64

Action:

Select all nodes before you click 'Next>'



65

Action:

Select the options you want to use to manage your database and click 'Next'



66

Action:

Type in the passwords you want to use and click 'Next'



67

Action:

Select the diskgroup you created for the database files, optionally select FRA & Enable Archiving if you

wish to configure. Click ‘Next >’



68

Action:

Select Appropriate option, if you wish to configure Database Vault & Label Security click 'Next >'



69

Action:

Review and change the settings for memory allocation, character sets etc. according to your needs

and click 'Next >'



70

Action:

Make sure the tick box 'Create Database' is ticked and Optionally you mayselct “Generate Database

Creation Scripts” and click 'Next >'



71

Action:

Review the validation Results, if you are convinced you can go with “Ignore All” option, Click ‘Next >’



72

Action:

Review the database configuration details again and click 'Finish >'



73

Action:

The database is now created, you can either change or unlock your passwords or just click Exit to finish

the database creation.



74

8. Applying Latest PSUs to GRID & RDBMS Homes

Please download the latest patch from MOS Doc ID 756671.1. When the document was written latest

PSU release was:-

Patch 20996835: GRID INFRASTRUCTURE PATCH SET UPDATE 12.1.0.2.4 (JUL2015)

The above patch contains both GI & RDBMS Patch and can be applied on a rolling manner.

Please note:-

1. Make sure that there are no active sqlplus sessions opened through putty.(ps -ef | grep sqlplus)

2. Make sure that emagent / em dbcontrol is stopped manually before you execute the patch steps

(ps -ef | grep em)

Steps for applying the patch=======================

1. Download the latest opatch (6880880) utility and replace the existing OPatch with the new one (it

will not allow you to replace, so you have to move with root user and change the ownership to

grid:oinstall)

https://updates.oracle.com/download/6880880.html

2. Create the OCM response file for silent installation of "opatch auto" features as a root user.

$ $GRI D_HOME/ OPatch/ ocm/ bi n/ emocmr sp - no_banner - output / t mp/ ocmconf . r sp

Provi de your emai l addr ess t o be i nf or med of secur i t y i ssues, i nst al l andi ni t i at e Or acl e Conf i gur at i on Manager . Easi er f or you i f you use your MyOr acl e Suppor t Emai l address/ User Name.Vi si t ht t p: / / www. or acl e. com/ suppor t / pol i c i es. ht ml f or det ai l s.Emai l address/ User Name:

<<<< Pr ess Ent er / Ret urn key and don' t provi de any i nput >>>>

You have not pr ovi ded an emai l address f or not i f i cat i on of secur i t y i ssues.Do you wi sh to remai n uni nf ormed of secur i t y i ssues ( [ Y]es, [ N] o) [ N] : Y <<< t ype

Y/ Yes >>> The OCM conf i gurat i on r esponse f i l e ( / t mp/ ocmconf . r sp) was success f ul l y cr eat ed. <<

3. Unzip the patch file by GRID software owner.

4. Apply the patch using below command as a root user:-

# cd $GRI D_HOME/ OPat ch

# . / opat chaut o appl y <UNZI PPED_PATCH_LOCATI ON>/ 20996835 - ocmr f / t mp/ ocmconf . r sp

Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these

steps on only one node.



Datapatch is run to complete the post-install SQL deployment for the PSU.

$ sql pl us / nol og

SQL> Connect / as sysdba

SQL> st ar t up ( i f not st ar t ed)

SQL> al t er pl uggabl e dat abase al l open;

SQL> qui t

$ cd $ORACLE_HOME/ OPat ch

$ . / dat apatch - ver bose

Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/20831110/<unique patch ID> for

errors:

20831110_appl y_<dat abase SI D>_<CDB name>_<t i mest amp>. l og

Please refer the readme.html file of the patch document for complete details.

Date post:	05-Jul-2018
Category:	Documents
Upload:	shaikali1980
View:	243 times
Download:	1 times

Step-By-step Installation Guide RAC 12cR1 on Linux

Documents