VMware vCenter Server is the centralized management tool that allows for the management of multiple ESXi servers and virtual machines (VMs) through a single console application. vCenter is a critical component in the VMware deployment. Lot of the feature/functionality are not available without vCenter. All of the well-known features in vSphere such as VMotion, Storage VMotion, Distributed Resource Scheduler (DRS), VMware High Availability (HA) and Fault Tolerance (FT) require vCenter Server.

In simplistic terms, VMware vCenter can be compared to Oracle’s Enterprise Manager 12c Cloud Control in the absence of Oracle VM in a physical server environments. For the DBAs who happen to be working on Oracle VM, vCenter is equivalent to Oracle VM Manager. At the time of writing this blog, the latest release of vCenter that was available was vCenter 5.1. News from the recent VMWorld conference, the next release of vCenter 5.5 will be available to the general public sometime in September 2013.

vCenter Server 5.1 provides a vCenter Server Simple Install option that installs vCenter Single Sign-On, Inventory Service, and vCenter Server for small VMware deployments on the virtual machine. If you prefer to customize the location and setup of each component, you can install the components separately by selecting the individual installation options in the following order:

  • vCenter Single Sign-On
  • Inventory Services
  • vCenter Server

Each of the components listed above can be installed in a different virtual machine.

Vcenter 1
Click on the option to perform the VMware vCenter simple install which will install vCenter Server, Single Sign On Server, and Inventory Service on the Windows server.

Vcenter 2

Click on OK because the vCenter server is not connected to an Active Directory domain

Then click on Next from the Single Sign On screen

Vcenter 3

When the Welcome screen appears, click Next to continue.

Vcenter 4

Select Next to accept the End-User Patent Agreement.

Vcenter 5

Please read the License Agreement; If you agree to the terms, select “I accept to the terms in the license agreement” and click on Next

Vcenter 6

Enter the password for the vCenter Single-Sign-On Admin user account

Click on Next

Vcenter 7

For the test environment, you can accept to Install a local Microsoft SQL Server 2008 R2 Express instance
For a production environment, you should install an Oracle Database with Standard or Enterprise edition

Click on Next

Vcenter 8

Enter the password for the RSA_DBA and RSA_USER database account

Click on Next

Vcenter 9

Click on OK

Click on Next

Vcenter 10

Accept the default directory path to install VMware vCenter

You can change the location if your corporate standards dictate an alternate location

Click on Next

Vcenter 11

Accept the default HTTPS Port

Click on Next

Vcenter 12

Click on the Install button to start the installation of vCenter

Vcenter 13

If you are performing just an evaluation term, click on the next button

Enter the License key for vCenter and click on Next

Vcenter 14

For the ODBC data source for vCenter Server, we will accept the default of 5 hosts and 50 virtual machines in our test environment

Click on Next

Vcenter 15

Either enter the fully qualified host.domain name or enter the IP address

Click on Next

Vcenter 16

Accept the acknowledgement for using an IP address instead of a fully qualified host name.

Click on OK

Vcenter 17

Either accept the default port assignments or modify the ports as needed and defined in the firewall rules

Click on Next

Vcenter 18

Since this is a test vCenter deployment, we will accept the default JVM Memory allocation of 1GB and click on Next

Vcenter 19

Click on the Install button to continue

Vcenter 20

Vcenter 21

Click on the Finish button

Vcenter 22

Click on OK

Login as windows administrator: administrator / password to access vCenter from the vSphere client


Book Title:
Successfully Virtualize Business Critical Oracle Databases

VMware iBook Cover

Here’s the book Description:
Written by VMware vExperts (Charles Kim (VCP), Viscosity North America, and George Trujillo (VCI), HortonWorks) and leading experts within VMware VCI and Learning Specialist (Steve Jones) and Chief Database Architect in EMC’s Global IT organization (Darryl Smith), this book will provide critical instructions for deploying Oracle Standalone and Real Application Cluster (RAC) on VMware enterprise virtualized platforms. You will learn how to setup an Oracle ecosystem within a virtualized infrastructure for enterprise deployments. We will share industry best practices to install and configure Linux, and to deploy Oracle Grid Infrastructure and Databases in a matter of hours. Whether you are deploying a 4 node RAC cluster or deploying a single standalone database, we will lead you to the foundation which will allow you to rapidly provision database-as-a-service. We will disseminate key details on creating golden image templates from the virtual machine to the Oracle binaries and databases. You will learn from industry experts how to troubleshoot production Oracle database servers running in VMware virtual infrastructures.

Audience:
Database Admins/Architects, VMware Admins, System Admins/Architects, Project Architects
This book designed for Oracle DBAs and VMware administrators needing to learn the art of virtualizing Oracle.


Recent events enabled Red Hat and Oracle to work together, and Oracle is now officially supporting ASMlib on Red Hat Enterprise Linux 6.4 and newer.

The knowledge base article which was updated in early May indicates that now we have ‘kmod-oracleasm’,’oracleasmlib’ and ‘oracleasm-support’ packages that need to be installed on the system:
https://access.redhat.com/site/solutions/315643

kmod-oracleasm is available from the Red Hat Network (RHN) and can be installed from the RHEL Server Supplementary (v. 6 64-bit x86_64) channel. oracleasmlib and oracleasm-support packages are available for download at this location.

Here’s what the installation steps look like in RHEL 6.4. It does not look any different than before except we are playing with a new player kmod-oracleasm from Red Hat instead of Oracle:

[root@rh64a ~]# ls -l *oracleasm*
-rw-r--r-- 1 root root 35044 Aug 22 20:41 kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm
-rw-r--r-- 1 root root 13300 Aug 22 20:45 oracleasmlib-2.0.4-1.el6.x86_64.rpm
-rw-r--r-- 1 root root 74984 Aug 22 20:56 oracleasm-support-2.1.8-1.el6.x86_64.rpm

Installation is done with a simple rpm -ihv command on each of the RPMs that we downloaded. There does not seem to be any dependencies between any of the RPMs. In this example, we will install the kmod-oracleasm RPM, followed by oracleasmlib, followed by oracle-support RPMs.

[root@rh64a ~]# rpm -ihv kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm
warning: kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Preparing...                ########################################### [100%]
   1:kmod-oracleasm         ########################################### [100%]

[root@rh64a ~]# rpm -ihv oracleasmlib-2.0.4-1.el6.x86_64.rpm
warning: oracleasmlib-2.0.4-1.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
Preparing...                ########################################### [100%]
   1:oracleasmlib           ########################################### [100%]

[root@rh64a ~]# rpm -ihv oracleasm-support-2.1.8-1.el6.x86_64.rpm
warning: oracleasm-support-2.1.8-1.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
Preparing...                ########################################### [100%]
   1:oracleasm-support      ########################################### [100%]

Next we will configure oracleasm. To configure oracleasm interactively, we have to prefix the command with the service syntax first:

[root@rh64a ~]# service oracleasm configure
Configuring the Oracle ASM library driver.

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

Default user to own the driver interface []: oracle    
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [  OK  ]
Scanning the system for Oracle ASMLib disks: [  OK  ]

[root@rh64a ~]# oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=oracle
ORACLEASM_GID=dba
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=""
ORACLEASM_SCANEXCLUDE=""
ORACLEASM_USE_LOGICAL_BLOCK_SIZE="false"

Posted by Charles Kim, Oracle ACE Director and VMware vExpert


5stars
ASM 12c Book

We desperately needed an update to Nitin Vengurlekar’s ASM book by Oracle Press. This book essentially covers all the aspects for Oracle Database 11gR2 ASM, 12c ASM plus ACFS and pulls it all together in the context of Private Database Cloud and consolidation. I particularly like the Appendix section that covers the best practices of building a Private Database Cloud. I also like Chapter 14: ASM 12c: the New Frontier which covers 12c ASM at a high level. The ASM instance chapter is worth the price of the book itself!!

This book is a MUST read for anyone managing RAC/ASM environments.

This book is broken down to 14 chapters and an appendix and targeted to DBAs, technical managers, storage architects, linux administrators, and consultants who are involved with RAC and ASM implementations. Here’s the breakdown of the chapters:
1. Automatic Storage Management in a Cloud World
2. ASM and Grid Infrastructure Stack
3. ASM Instances
4. ASM Disks and Disk Groups
5. Managing Databases in ASM
6. ASMLIB Concepts and Overview
7. ASM Files, Aliases, and Security
8. ASM Space Allocation and Rebalance
9. ASM Operations
10. ACFS Design and Deployment
11. ACFS Data Services
12. ASM Optimizations in Oracle Engineered Systems
13. ASM Tools and Utilities
14. ASM 12c: The New Frontier
Appendix: Best Practices for Database Consolidation in Private Clouds


Maintenance on the Grid Infrastructure environment requires root privileges. You may need to unlock the Grid Home for cloning or patching purposes. You may need to deconfig a failed root.sh cluster configuration to clean up all the scattered files and then to re-execute root.sh. The following examples are tested at Viscosity Lab on Oracle Database 12c on an 8 node RAC.

To Unlock the Grid Infrastructure environment:

# cd $GRID_HOME/crs/install
# ./rootcrs.pl -unlock

Using configuration parameter file: ./crsconfig_params
2013/08/12 07:20:52 CLSRSC-347: Successfully unlock /u01/app/12.1.0/grid

To lock the Grid Infrastructure environment:

# cd $GRID_HOME/crs/install
# ./rootcrs.pl -patch
Using configuration parameter file: ./crsconfig_params
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'rh64a'
CRS-2672: Attempting to start 'ora.evmd' on 'rh64a'
CRS-2676: Start of 'ora.mdnsd' on 'rh64a' succeeded
CRS-2676: Start of 'ora.evmd' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'rh64a'
CRS-2676: Start of 'ora.gpnpd' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'rh64a'
CRS-2676: Start of 'ora.gipcd' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'rh64a'
CRS-2676: Start of 'ora.cssdmonitor' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'rh64a'
CRS-2672: Attempting to start 'ora.diskmon' on 'rh64a'
CRS-2676: Start of 'ora.diskmon' on 'rh64a' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'rh64a'
CRS-2676: Start of 'ora.cssd' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'rh64a'
CRS-2672: Attempting to start 'ora.ctssd' on 'rh64a'
CRS-2676: Start of 'ora.ctssd' on 'rh64a' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'rh64a'
CRS-2676: Start of 'ora.asm' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'rh64a'
CRS-2676: Start of 'ora.storage' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.crf' on 'rh64a'
CRS-2676: Start of 'ora.crf' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'rh64a'
CRS-2676: Start of 'ora.crsd' on 'rh64a' succeeded
CRS-6017: Processing resource auto-start for servers: rh64a
CRS-2673: Attempting to stop 'ora.rh64a.vip' on 'rh64d'
CRS-2672: Attempting to start 'ora.ons' on 'rh64a'
CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64a'
CRS-2672: Attempting to start 'ora.proxy_advm' on 'rh64a'
CRS-2677: Stop of 'ora.rh64a.vip' on 'rh64d' succeeded
CRS-2672: Attempting to start 'ora.rh64a.vip' on 'rh64a'
CRS-2676: Start of 'ora.rh64a.vip' on 'rh64a' succeeded
CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'rh64a'
CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64a' succeeded
CRS-2676: Start of 'ora.ons' on 'rh64a' succeeded
CRS-2676: Start of 'ora.LISTENER.lsnr' on 'rh64a' succeeded
CRS-2676: Start of 'ora.proxy_advm' on 'rh64a' succeeded
CRS-6016: Resource auto-start has completed for server rh64a
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].

To deconfig the Grid Infrastructure environment execute the following on each of the RAC nodes:

# cd $GRID_HOME/crs/install
# ./rootcrs.pl -deconfig -verbose -force
Using configuration parameter file: ./crsconfig_params
Network 1 exists
Subnet IPv4: 10.0.0.0/255.255.255.0/eth1, static
Subnet IPv6: 
VIP exists: network number 1, hosting node rh64a
VIP Name: rh64a-vip
VIP IPv4 Address: 10.0.0.50
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64b
VIP Name: rh64b-vip
VIP IPv4 Address: 10.0.0.51
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64c
VIP Name: rh64c-vip
VIP IPv4 Address: 10.0.0.52
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64d
VIP Name: rh64d-vip
VIP IPv4 Address: 10.0.0.53
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64e
VIP Name: rh64e-vip
VIP IPv4 Address: 10.0.0.54
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64g
VIP Name: rh64g-vip
VIP IPv4 Address: 10.0.0.56
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64h
VIP Name: rh64h-vip
VIP IPv4 Address: 10.0.0.57
VIP IPv6 Address: 
ONS exists: Local port 6100, remote port 6200, EM port 2016
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'rh64a'
CRS-2673: Attempting to stop 'ora.crsd' on 'rh64a'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'rh64a'
CRS-2673: Attempting to stop 'ora.proxy_advm' on 'rh64a'
CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64a'
CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.proxy_advm' on 'rh64a' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'rh64a' has completed
CRS-2677: Stop of 'ora.crsd' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.gpnpd' on 'rh64a'
CRS-2673: Attempting to stop 'ora.ctssd' on 'rh64a'
CRS-2673: Attempting to stop 'ora.evmd' on 'rh64a'
CRS-2673: Attempting to stop 'ora.storage' on 'rh64a'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'rh64a'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'rh64a'
CRS-2677: Stop of 'ora.storage' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'rh64a'
CRS-2677: Stop of 'ora.drivers.acfs' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.evmd' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.asm' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'rh64a'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'rh64a' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'rh64a'
CRS-2677: Stop of 'ora.cssd' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.crf' on 'rh64a'
CRS-2677: Stop of 'ora.crf' on 'rh64a' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'rh64a'
CRS-2677: Stop of 'ora.gipcd' on 'rh64a' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'rh64a' has completed
CRS-4133: Oracle High Availability Services has been stopped.
2013/08/12 12:33:24 CLSRSC-336: Successfully deconfigured Oracle clusterware stack on this node

To complete the reconfiguration process, execute the following on the last node:

# cd $ORACLE_HOME/crs/install
# ./rootcrs.pl -deconfig -verbose -force -lastnode
Using configuration parameter file: ./crsconfig_params
2013/08/12 12:58:41 CLSRSC-332: CRS resources for listeners are still configured

Network 1 exists
Subnet IPv4: 10.0.0.0/255.255.255.0/eth1, static
Subnet IPv6: 
VIP exists: network number 1, hosting node rh64g
VIP Name: rh64g-vip
VIP IPv4 Address: 10.0.0.56
VIP IPv6 Address: 
VIP exists: network number 1, hosting node rh64h
VIP Name: rh64h-vip
VIP IPv4 Address: 10.0.0.57
VIP IPv6 Address: 
ONS exists: Local port 6100, remote port 6200, EM port 2016
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'rh64h'
CRS-2673: Attempting to stop 'ora.crsd' on 'rh64h'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'rh64h'
CRS-2673: Attempting to stop 'ora.proxy_advm' on 'rh64h'
CRS-2673: Attempting to stop 'ora.OCRVOTE.dg' on 'rh64h'
CRS-2677: Stop of 'ora.proxy_advm' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.OCRVOTE.dg' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'rh64h'
CRS-2673: Attempting to stop 'ora.FRA.dg' on 'rh64h'
CRS-2677: Stop of 'ora.DATA.dg' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.FRA.dg' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'rh64h'
CRS-2677: Stop of 'ora.asm' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64h'
CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'rh64h' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'rh64h' has completed
CRS-2677: Stop of 'ora.crsd' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.crf' on 'rh64h'
CRS-2673: Attempting to stop 'ora.storage' on 'rh64h'
CRS-2673: Attempting to stop 'ora.ctssd' on 'rh64h'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'rh64h'
CRS-2673: Attempting to stop 'ora.gpnpd' on 'rh64h'
CRS-2673: Attempting to stop 'ora.evmd' on 'rh64h'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'rh64h'
CRS-2677: Stop of 'ora.drivers.acfs' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.storage' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'rh64h'
CRS-2677: Stop of 'ora.crf' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.evmd' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'rh64h' succeeded
CRS-2677: Stop of 'ora.asm' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'rh64h'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'rh64h'
CRS-2677: Stop of 'ora.cssd' on 'rh64h' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'rh64h'
CRS-2677: Stop of 'ora.gipcd' on 'rh64h' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'rh64h' has completed
CRS-4133: Oracle High Availability Services has been stopped.
2013/08/12 13:03:20 CLSRSC-336: Successfully deconfigured Oracle clusterware stack on this node

Posted by Charles Kim, Oracle ACE Director, VMware vExpert


There are several options when it comes to configuring parameters for shared storage and access. Today, let’s take some time to cover how to leverage the vSphere 5.x Client to add the required parameters.

From the Options Tab, Click on the General line, and click on the Configuration Parameters button
General configuration

Click on the Add Rows button at the bottom right of the screen:

Multi writer Flag

As part of our RAC configuration for shared storage, we can setup udev rules for device persistency and permissions. You will choose this option if you are opting out of Oracle ASMLIB.

Note:
Lot of customers went forward with setting up udev rules on Red Hat 6 because Oracle and Red Hat released de-support of ASMLIB when Red Hat 6 went GA. When Red Hat 6.4 came out, Red Hat announced support for ASMLIB. This section will assume that the customers have opted out of ASMLIB and chose to stick with udev rules.

Doing this with the GUI and repeating the steps is extremely painful. We passionately promote automating mundane tasks like this. Look for upcoming post on how to do all this with PowerCLI.

Also, by default, the UUID (Unique Device Identifier) of the disks will not be available to the Linux VM when you probe with the scsi_id command. To allow the scsi_id to retrieve the unique SCSI identifier, you must set the following parameter to true on each VM:

disk.EnableUUID = “TRUE”


In my lab environments, I setup user equivalence even for the root user as I push files such as the udev rules for storage devices, resolv.conf and nsswitch.conf files to all the RAC nodes in an automated fashion.

Here’s what the ssh setup looks like on a 7 node RAC cluster. You will be prompted to type in the password twice for each node.

[root@rh64a sshsetup]# ./sshUserSetup.sh -user root -hosts "rh64a rh64b rh64c rh64d rh64e rh64f rh64g" -noPromptPassphrase -advanced -exverify
The output of this script is also logged into /tmp/sshUserSetup_2013-08-08-06-41-46.log
Hosts are rh64a rh64b rh64c rh64d rh64e rh64f rh64g
user is root
Platform:- Linux 
Checking if the remote hosts are reachable
PING rh64a (10.0.0.40) 56(84) bytes of data.
64 bytes from rh64a (10.0.0.40): icmp_seq=1 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=4 ttl=64 time=0.030 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=5 ttl=64 time=0.026 ms

--- rh64a ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.026/0.028/0.030/0.006 ms
PING rh64b (10.0.0.41) 56(84) bytes of data.
64 bytes from rh64b (10.0.0.41): icmp_seq=1 ttl=64 time=0.122 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=2 ttl=64 time=0.172 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=3 ttl=64 time=0.188 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=4 ttl=64 time=0.175 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=5 ttl=64 time=0.163 ms

--- rh64b ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.122/0.164/0.188/0.022 ms
PING rh64c (10.0.0.42) 56(84) bytes of data.
64 bytes from rh64c (10.0.0.42): icmp_seq=1 ttl=64 time=0.815 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=2 ttl=64 time=0.169 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=3 ttl=64 time=0.184 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=4 ttl=64 time=0.161 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=5 ttl=64 time=0.160 ms

--- rh64c ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.160/0.297/0.815/0.259 ms
PING rh64d (10.0.0.43) 56(84) bytes of data.
64 bytes from rh64d (10.0.0.43): icmp_seq=1 ttl=64 time=0.851 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=2 ttl=64 time=0.172 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=3 ttl=64 time=0.192 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=4 ttl=64 time=0.215 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=5 ttl=64 time=0.170 ms

--- rh64d ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.170/0.320/0.851/0.265 ms
PING rh64e (10.0.0.44) 56(84) bytes of data.
64 bytes from rh64e (10.0.0.44): icmp_seq=1 ttl=64 time=0.543 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=2 ttl=64 time=0.170 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=3 ttl=64 time=0.129 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=4 ttl=64 time=0.154 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=5 ttl=64 time=0.166 ms

--- rh64e ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.129/0.232/0.543/0.156 ms
PING rh64f (10.0.0.45) 56(84) bytes of data.
64 bytes from rh64f (10.0.0.45): icmp_seq=1 ttl=64 time=0.792 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=2 ttl=64 time=0.160 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=3 ttl=64 time=0.190 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=4 ttl=64 time=0.164 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=5 ttl=64 time=0.173 ms

--- rh64f ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.160/0.295/0.792/0.249 ms
PING rh64g (10.0.0.46) 56(84) bytes of data.
64 bytes from rh64g (10.0.0.46): icmp_seq=1 ttl=64 time=0.841 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=2 ttl=64 time=0.144 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=3 ttl=64 time=0.171 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=4 ttl=64 time=0.162 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=5 ttl=64 time=0.191 ms

--- rh64g ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.144/0.301/0.841/0.270 ms
Remote host reachability check succeeded.
The following hosts are reachable: rh64a rh64b rh64c rh64d rh64e rh64f rh64g.
The following hosts are not reachable: .
All hosts are reachable. Proceeding further...
firsthost rh64a
numhosts 7
The script will setup SSH connectivity from the host rh64a to all
the remote hosts. After the script is executed, the user can use SSH to run
commands on the remote hosts or copy files between this host rh64a
and the remote hosts without being prompted for passwords or confirmations.

NOTE 1:
As part of the setup procedure, this script will use ssh and scp to copy
files between the local host and the remote hosts. Since the script does not
store passwords, you may be prompted for the passwords during the execution of
the script whenever ssh or scp is invoked.

NOTE 2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE
directories.

Do you want to continue and let the script make the above mentioned changes (yes/no)?
yes

The user chose yes
User chose to skip passphrase related questions.
Creating .ssh directory on local host, if not present already
Creating authorized_keys file on local host
Changing permissions on authorized_keys to 644 on local host
Creating known_hosts file on local host
Changing permissions on known_hosts to 644 on local host
Creating config file on local host
If a config file exists already at /root/.ssh/config, it would be backed up to /root/.ssh/config.backup.
Removing old private/public keys on local host
Running SSH keygen on local host with empty passphrase
Generating public/private rsa key pair.
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
f1:fb:5e:da:7e:04:5b:c1:27:5e:26:1c:4f:a0:e7:ed root@rh64a
The key's randomart image is:
+--[ RSA 1024]----+
|             .+o.|
|             .+=+|
|        .   ...=+|
|         o   oo..|
|        S .   .+.|
|           .  ...|
|          .   ..E|
|           . +  .|
|           .+.o. |
+-----------------+
Creating .ssh directory and setting permissions on remote host rh64a
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64a. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64a.
Warning: Permanently added 'rh64a,10.0.0.40' (RSA) to the list of known hosts.
root@rh64a's password: 
Done with creating .ssh directory and setting permissions on remote host rh64a.
Creating .ssh directory and setting permissions on remote host rh64b
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64b. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64b.
Warning: Permanently added 'rh64b,10.0.0.41' (RSA) to the list of known hosts.
root@rh64b's password: 
Done with creating .ssh directory and setting permissions on remote host rh64b.
Creating .ssh directory and setting permissions on remote host rh64c
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64c. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64c.
Warning: Permanently added 'rh64c,10.0.0.42' (RSA) to the list of known hosts.
root@rh64c's password: 
Done with creating .ssh directory and setting permissions on remote host rh64c.
Creating .ssh directory and setting permissions on remote host rh64d
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64d. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64d.
Warning: Permanently added 'rh64d,10.0.0.43' (RSA) to the list of known hosts.
root@rh64d's password: 
Done with creating .ssh directory and setting permissions on remote host rh64d.
Creating .ssh directory and setting permissions on remote host rh64e
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64e. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64e.
Warning: Permanently added 'rh64e,10.0.0.44' (RSA) to the list of known hosts.
root@rh64e's password: 
Done with creating .ssh directory and setting permissions on remote host rh64e.
Creating .ssh directory and setting permissions on remote host rh64f
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64f. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64f.
Warning: Permanently added 'rh64f,10.0.0.45' (RSA) to the list of known hosts.
root@rh64f's password: 
Done with creating .ssh directory and setting permissions on remote host rh64f.
Creating .ssh directory and setting permissions on remote host rh64g
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64g. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64g.
Warning: Permanently added 'rh64g,10.0.0.46' (RSA) to the list of known hosts.
root@rh64g's password: 
Done with creating .ssh directory and setting permissions on remote host rh64g.
Copying local host public key to the remote host rh64a
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64a.
root@rh64a's password: 
Done copying local host public key to the remote host rh64a
Copying local host public key to the remote host rh64b
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64b.
root@rh64b's password: 
Done copying local host public key to the remote host rh64b
Copying local host public key to the remote host rh64c
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64c.
root@rh64c's password: 
Done copying local host public key to the remote host rh64c
Copying local host public key to the remote host rh64d
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64d.
root@rh64d's password: 
Done copying local host public key to the remote host rh64d
Copying local host public key to the remote host rh64e
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64e.
root@rh64e's password: 
Done copying local host public key to the remote host rh64e
Copying local host public key to the remote host rh64f
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64f.
root@rh64f's password: 
Done copying local host public key to the remote host rh64f
Copying local host public key to the remote host rh64g
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64g.
root@rh64g's password: 
Done copying local host public key to the remote host rh64g
Creating keys on remote host rh64a if they do not exist already. This is required to setup SSH on host rh64a.

Creating keys on remote host rh64b if they do not exist already. This is required to setup SSH on host rh64b.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
84:07:79:b1:07:35:cd:b0:44:d7:a0:bf:0d:2e:e1:af root@rh64b
The key's randomart image is:
+--[ RSA 1024]----+
|      ..o+*+oo   |
|      .o.+ =o .  |
|      ..+ +      |
|       o . .     |
|        S . o    |
|         . o +   |
|          o o .  |
|           o     |
|          E..    |
+-----------------+
Creating keys on remote host rh64c if they do not exist already. This is required to setup SSH on host rh64c.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
3e:7f:3c:b7:f5:c7:fa:78:7e:c5:6a:b9:fc:2f:47:92 root@rh64c
The key's randomart image is:
+--[ RSA 1024]----+
|                 |
|                 |
|                 |
|                 |
|        S      o |
|       .      E +|
|        o  .   *o|
|         o  +.*oB|
|          .. +*@X|
+-----------------+
Creating keys on remote host rh64d if they do not exist already. This is required to setup SSH on host rh64d.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
e9:d7:f8:f0:46:c5:7c:5e:c1:25:ec:a1:50:72:b1:8a root@rh64d
The key's randomart image is:
+--[ RSA 1024]----+
|          ..+oo o|
|          .o .o+ |
|           ..= ..|
|         o .. = o|
|        E .  . o.|
|       .   o.   .|
|        . +..    |
|         . +.    |
|           .o    |
+-----------------+
Creating keys on remote host rh64e if they do not exist already. This is required to setup SSH on host rh64e.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
cc:b2:0c:6d:4b:99:20:70:61:41:27:f5:6e:c8:33:8f root@rh64e
The key's randomart image is:
+--[ RSA 1024]----+
|..B+o            |
| + o .           |
|  . . .          |
|   o = =         |
|    * X S        |
|     @ +         |
|    E =          |
|                 |
|                 |
+-----------------+
Creating keys on remote host rh64f if they do not exist already. This is required to setup SSH on host rh64f.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
41:60:7e:f4:21:87:77:97:23:c3:c1:e8:2b:96:9f:c7 root@rh64f
The key's randomart image is:
+--[ RSA 1024]----+
|      o.+.o+.. . |
|     o o.+o.* +  |
|      . oo.. + . |
|       . ..      |
|        S. .     |
|        + .      |
|       . o o     |
|          o E    |
|           .     |
+-----------------+
Creating keys on remote host rh64g if they do not exist already. This is required to setup SSH on host rh64g.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
93:aa:49:22:6f:cb:ae:87:0a:ff:38:e0:ea:a0:fb:b1 root@rh64a
The key's randomart image is:
+--[ RSA 1024]----+
|                 |
|                 |
|                 |
|         .       |
|        S        |
|.      . .       |
|=oo . .          |
|=*+* o           |
|XOE++            |
+-----------------+
Updating authorized_keys file on remote host rh64a
Updating known_hosts file on remote host rh64a
Updating authorized_keys file on remote host rh64b
Updating known_hosts file on remote host rh64b
Updating authorized_keys file on remote host rh64c
Updating known_hosts file on remote host rh64c
Updating authorized_keys file on remote host rh64d
Updating known_hosts file on remote host rh64d
Updating authorized_keys file on remote host rh64e
Updating known_hosts file on remote host rh64e
Updating authorized_keys file on remote host rh64f
Updating known_hosts file on remote host rh64f
Updating authorized_keys file on remote host rh64g
Updating known_hosts file on remote host rh64g
cat: /root/.ssh/known_hosts.tmp: No such file or directory
cat: /root/.ssh/authorized_keys.tmp: No such file or directory
SSH setup is complete.

------------------------------------------------------------------------
Verifying SSH setup
===================
The script will now run the date command on the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are prompted for the
password, ssh is not setup correctly and you will need to resolve the
issue and set up ssh again.
The possible causes for failure could be:
1. The server settings in /etc/ssh/sshd_config file do not allow ssh
for user root.
2. The server may have disabled public key based authentication.
3. The client public key on the server may be outdated.
4. ~root or ~root/.ssh on the remote host may not be owned by root.
5. User may not have passed -shared option for shared remote users or
may be passing the -shared option for non-shared remote users.
6. If there is output in addition to the date, but no password is asked,
it may be a security alert shown as part of company policy. Append the
additional text to the <OMS HOME>/sysman/prov/resources/ignoreMessages.txt file.
------------------------------------------------------------------------
--rh64a:--
Running /usr/bin/ssh -x -l root rh64a date to verify SSH connectivity has been setup from local host to rh64a.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64b:--
Running /usr/bin/ssh -x -l root rh64b date to verify SSH connectivity has been setup from local host to rh64b.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64c:--
Running /usr/bin/ssh -x -l root rh64c date to verify SSH connectivity has been setup from local host to rh64c.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64d:--
Running /usr/bin/ssh -x -l root rh64d date to verify SSH connectivity has been setup from local host to rh64d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64e:--
Running /usr/bin/ssh -x -l root rh64e date to verify SSH connectivity has been setup from local host to rh64e.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
--rh64f:--
Running /usr/bin/ssh -x -l root rh64f date to verify SSH connectivity has been setup from local host to rh64f.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
--rh64g:--
Running /usr/bin/ssh -x -l root rh64g date to verify SSH connectivity has been setup from local host to rh64g.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
-Verification from rh64a complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
-Verification from rh64b complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
-Verification from rh64c complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
-Verification from rh64d complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
-Verification from rh64e complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
-Verification from rh64f complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
-Verification from rh64g complete-
SSH verification complete.

I also run a simple test to confirm that I can login to all the RAC nodes without being prompted for a password by executing hostname and date commands together:

[root@rh64a ~]# cat ssh_setup_test.ksh
ssh rh64a "hostname; date"
ssh rh64b "hostname; date"
ssh rh64c "hostname; date"
ssh rh64d "hostname; date"
ssh rh64e "hostname; date"
ssh rh64f "hostname; date"
ssh rh64g "hostname; date"

[root@rh64a ~]# ./ssh_setup_test.ksh 
rh64a
Thu Aug  8 06:48:35 CDT 2013
rh64b
Thu Aug  8 06:48:35 CDT 2013
rh64c
Thu Aug  8 06:48:35 CDT 2013
rh64d
Thu Aug  8 06:48:35 CDT 2013
rh64e
Thu Aug  8 06:48:36 CDT 2013
rh64f
Thu Aug  8 06:48:35 CDT 2013
rh64a
Thu Aug  8 06:48:36 CDT 2013
Posted in RAC

Here’s a super easy and fast way of setting up a Yum Repository for all your Linux based infrastructure. You can leverage NFS and effectively have a Yum Repository in matter of minutes.

First, mount the Red Hat 6 media distribution from an ISO or from the DVD media. Next, copy the the entire contents of the DVD to a location on the NAS or a local file system that you wish to be exported to other servers.

On the Red Hat media, look for a file called .discinfo on the root directory of the media. In my example, here’s what the contents of .discinfo looks like:

[root@rh64a yum.repos.d]# cat "/media/RHEL_6.4 x86_64 Disc 1"/.discinfo
1359576196.686790
Red Hat Enterprise Linux 6.4
x86_64
1

The line that you are interested in is the first line with all the numbers: 1359576196.686790

We will need that number to build our repository definition file: /etc/yum.repos.d/viscosity.repo
In this file, we will add the full numeric value for our mediaaid line. The other tidbit of information that you need to provide is the root file system location for the Red Hat media where you copied everything to. In our example, we copied the entire media to the /shared/rhel64.dvd directory. We will fill out the baseurl value with this location.

# cat /etc/yum.repos.d/viscosity.repo
[viscosity]
mediaid=1359576196.686790
name=Local Viscosity Repo
baseurl=file:///nfs/rhel64.dvd/
enabled=1
gpgcheck=no

From the server that will act as our Yum Repository, add the entries to /etc/exports:

[root@rh64b yum.repos.d]# cat /etc/exports
/nfs *(rw,sync) 

You can selective qualify the list of servers that you want to present the share to for added security. You may need to start the NFS service with the “service hfs start” or restart the NFS service with the “service nfs restart” command.

On the target server where you wish to mount the /nfs share, you will issue the mount command with the -nfs option. In this example, we will mount the share from the rh64b server on the rh64a server. rh64b will serve as our utility server that will house the Yum Repository, DNS server, etc.

mount -t nfs rh64b:/nfs /nfs

The yum package manager does not discriminate between a network or local file system. From rh64a server, let’s take a test drive and install the screen RPM over NFS.

[root@rh64a Server]# yum install screen
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
viscosity                                                                                  | 3.9 kB     00:00 ... 
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package screen.x86_64 0:4.0.3-16.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==================================================================================================================
 Package                 Arch                    Version                         Repository                  Size
==================================================================================================================
Installing:
 screen                  x86_64                  4.0.3-16.el6                    viscosity                  494 k

Transaction Summary
==================================================================================================================
Install       1 Package(s)

Total download size: 494 k
Installed size: 795 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : screen-4.0.3-16.el6.x86_64                                                                     1/1 
  Verifying  : screen-4.0.3-16.el6.x86_64                                                                     1/1 

Installed:
  screen.x86_64 0:4.0.3-16.el6                                                                                    

Complete!

Automation is what we our end goal is. We want to automate RPM package installations. To automatically answer “Y” to the “Is this ok [y/N]:” question, we can pass the -y flag to our yum install command:

[root@rh64d ~]# yum -y install ksh
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
viscosity                                                                                               | 3.9 kB     00:00 ... 
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package ksh.x86_64 0:20100621-19.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================
 Package                 Arch                       Version                                Repository                     Size
===============================================================================================================================
Installing:
 ksh                     x86_64                     20100621-19.el6                        viscosity                     686 k

Transaction Summary
===============================================================================================================================
Install       1 Package(s)

Total download size: 686 k
Installed size: 1.5 M
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : ksh-20100621-19.el6.x86_64                                                                                  1/1 
  Verifying  : ksh-20100621-19.el6.x86_64                                                                                  1/1 

Installed:
  ksh.x86_64 0:20100621-19.el6                                                                                                 

Complete!

Before I begin, the source of truth for the the requirements for Installing Oracle Database 12.1 on RHEL6 or OL6 64-bit (x86-64) is Doc ID 1529864.1.

This blog post will provide the Linux RPM requirements to install Oracle Database 12c on Red Hat 5x and 6.x.
For Red Hat Linux 6 Compatible with Oracle 12c

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)

Customers wishing to install the Oracle Database 12.1 32-bit Client software should also install the 32-bit packages.

For Red Hat Linux 5 Compatible with Oracle 12c

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
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)
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

At Viscosity, I heavily promote automation our database builds for our clients. It allows our consultants to create databases that are consistent and reliable every time we build them.

In this example, I will walk you through the command line options of the database configuration assistant (dbca) for Oracle Database 12c.

$ cat dbca.sh
cd /u01/app/oracle/product/12.1.0/dbhome_1/bin
./dbca -silent \
 -createDatabase \
 -templateName General_Purpose.dbc \
 -gdbName TEST \
 -sid TEST     \
 -SysPassword oracle123 \
 -createAsContainerDatabase true \
    -numberofPDBs 2 \
    -pdbName VNA \
 -SystemPassword oracle123 \
 -emConfiguration DBEXPRESS  \
 -redoLogFileSize 100   \
 -recoveryAreaDestination FRA \
 -storageType ASM             \
   -asmsnmpPassword oracle123 \
   -asmSysPassword oracle123  \
   -diskGroupName DATA \
 -listeners LISTENER   \
 -registerWithDirService false \
 -characterSet AL32UTF8 \
 -nationalCharacterSet AL16UTF16 \
 -databaseType MULTIPURPOSE \
 -nodelist ol59a,ol59b \
 -initparams audit_file_dest='/u01/app/oracle/admin/TEST/adump' \
     -initparams compatible='12.1.0.0' \
     -initparams db_create_file_dest='+DATA' \
     -initparams db_create_online_log_dest_1='+DATA' \
     -initparams db_create_online_log_dest_2='+FRA' \
     -initparams db_recovery_file_dest='+FRA' \
     -initparams pga_aggregate_target=100M \
     -initparams diagnostic_dest='/u01/app/oracle' \
     -initparams parallel_max_servers=8 \
     -initparams processes=400 \
     -initparams sga_target=524288000 \
     -initparams db_recovery_file_dest_size=4322230272

Unfortunately, the parameter for the PDBAdmin password does not exist in the dbca -silent option. This will make automation of this part little more difficult. Additional parameters such as createAsContainerDatabase, numberofPDBs, pdbName, and registerWithService are new to Oracle Database 12c. Additional option for emConfiguation for DBEXPRESS is also new to Oracle Database 12c.

In this database creation script, I also embedded relevant initialization parameters. You can opt to include additional parameters that are enterprise standards for your corporation.

$ ./dbca.sh
Enter PDBADMIN User Password:

Copying database files
1% complete
2% complete
23% complete
Creating and starting Oracle instance
24% complete
27% complete
28% complete
29% complete
32% complete
35% complete
36% complete
38% complete
Creating cluster database views
40% complete
54% complete
Completing Database Creation
56% complete
58% complete
65% complete
67% complete
74% complete
77% complete
Creating Pluggable Databases
81% complete
86% complete
100% complete
Look at the log file "/u01/app/oracle/cfgtoollogs/dbca/TEST/TEST1.log" for further details.

We should always review the log file generated from dbca to confirm there are no relevant warning or error messages. As you can see from the example output below, the cluster verification utility was executed against novelist defined in our dbca database creation script.

$ cat /u01/app/oracle/cfgtoollogs/dbca/TEST/TEST1.log

Cluster Verification check "Node Connectivity" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether connectivity exists amongst all the nodes. The connectivity is being tested for the subnets "192.168.1.0,10.0.0.0"
Cluster Verification check "Multicast check" succeeded on nodes: ol59a,ol59b.
This task checks that network interfaces in subnet are able to communicate over multicast IP address
Cluster Verification Check "Physical Memory" succeeded on node "ol59a", expected value: 1GB (1048576.0KB) actual value: 2.9461GB (3089208.0KB).
Cluster Verification Check "Physical Memory" succeeded on node "ol59b", expected value: 1GB (1048576.0KB) actual value: 2.9461GB (3089208.0KB).
Cluster Verification check "Physical Memory" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has at least 1GB (1048576.0KB) of total physical memory.
Cluster Verification Check "Available Physical Memory" succeeded on node "ol59a", expected value: 50MB (51200.0KB) actual value: 2.3107GB (2422936.0KB).
Cluster Verification Check "Available Physical Memory" succeeded on node "ol59b", expected value: 50MB (51200.0KB) actual value: 2.3824GB (2498168.0KB).
Cluster Verification check "Available Physical Memory" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has at least 50MB (51200.0KB) of available physical memory.
Cluster Verification Check "Swap Size" succeeded on node "ol59b", expected value: 2.9461GB (3089208.0KB) actual value: 3.9062GB (4095996.0KB).
Cluster Verification Check "Swap Size" failed on node "ol59a", expected value: 2.9461GB (3089208.0KB) actual value: 1.9687GB (2064380.0KB).
PRVF-7573 : Sufficient swap size is not available on node "ol59a" [Required = 2.9461GB (3089208.0KB) ; Found = 1.9687GB (2064380.0KB)]
Cluster Verification check failed on nodes: ol59a.
This is a prerequisite condition to test whether sufficient total swap space is available on the system.
Cluster Verification Check "Free Space: ol59b:/tmp" succeeded on node "ol59b", expected value: 1GB  actual value: 2.4834GB .
Cluster Verification check "Free Space: ol59b:/tmp" succeeded on nodes: ol59b.
This is a prerequisite condition to test whether sufficient free space is available in the file system.
Cluster Verification Check "Free Space: ol59a:/tmp" succeeded on node "ol59a", expected value: 1GB  actual value: 3.9453GB .
Cluster Verification check "Free Space: ol59a:/tmp" succeeded on nodes: ol59a.
This is a prerequisite condition to test whether sufficient free space is available in the file system.
Cluster Verification check "User Existence: oracle" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether user "oracle" exists on the system.
Cluster Verification Check "Run Level" succeeded on node "ol59a", expected value: 3,5 actual value: 5.
Cluster Verification Check "Run Level" succeeded on node "ol59b", expected value: 3,5 actual value: 5.
Cluster Verification check "Run Level" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system is running with proper run level.
Cluster Verification Check "Hard Limit: maximum open file descriptors" succeeded on node "ol59a", expected value: 65536 actual value: 131072.
Cluster Verification Check "Hard Limit: maximum open file descriptors" succeeded on node "ol59b", expected value: 65536 actual value: 65536.
Cluster Verification check "Hard Limit: maximum open file descriptors" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the hard limit for "maximum open file descriptors" is set correctly.
Cluster Verification Check "Soft Limit: maximum open file descriptors" succeeded on node "ol59a", expected value: 1024 actual value: 131072.
Cluster Verification Check "Soft Limit: maximum open file descriptors" succeeded on node "ol59b", expected value: 1024 actual value: 1024.
Cluster Verification check "Soft Limit: maximum open file descriptors" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the soft limit for "maximum open file descriptors" is set correctly.
Cluster Verification Check "Hard Limit: maximum user processes" succeeded on node "ol59a", expected value: 16384 actual value: 131072.
Cluster Verification Check "Hard Limit: maximum user processes" succeeded on node "ol59b", expected value: 16384 actual value: 16384.
Cluster Verification check "Hard Limit: maximum user processes" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the hard limit for "maximum user processes" is set correctly.
Cluster Verification Check "Soft Limit: maximum user processes" succeeded on node "ol59a", expected value: 2047 actual value: 131072.
Cluster Verification Check "Soft Limit: maximum user processes" succeeded on node "ol59b", expected value: 2047 actual value: 16384.
Cluster Verification check "Soft Limit: maximum user processes" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the soft limit for "maximum user processes" is set correctly.
Cluster Verification Check "Architecture" succeeded on node "ol59a", expected value: x86_64 actual value: x86_64.
Cluster Verification Check "Architecture" succeeded on node "ol59b", expected value: x86_64 actual value: x86_64.
Cluster Verification check "Architecture" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has a certified architecture.
Cluster Verification Check "OS Kernel Version" succeeded on node "ol59a", expected value: 2.6.18 actual value: 2.6.39-400.109.4.el5uek.
Cluster Verification Check "OS Kernel Version" succeeded on node "ol59b", expected value: 2.6.18 actual value: 2.6.39-400.109.4.el5uek.
Cluster Verification check "OS Kernel Version" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system kernel version is at least "2.6.18".
Cluster Verification Check "OS Kernel Parameter: semmsl" succeeded on node "ol59a", expected value: 250 actual value: Current=250; Configured=250.
Cluster Verification Check "OS Kernel Parameter: semmsl" succeeded on node "ol59b", expected value: 250 actual value: Current=250; Configured=250.
Cluster Verification check "OS Kernel Parameter: semmsl" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmsl" is properly set.
Cluster Verification Check "OS Kernel Parameter: semmns" succeeded on node "ol59a", expected value: 32000 actual value: Current=32000; Configured=32000.
Cluster Verification Check "OS Kernel Parameter: semmns" succeeded on node "ol59b", expected value: 32000 actual value: Current=32000; Configured=32000.
Cluster Verification check "OS Kernel Parameter: semmns" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmns" is properly set.
Cluster Verification Check "OS Kernel Parameter: semopm" succeeded on node "ol59a", expected value: 100 actual value: Current=100; Configured=100.
Cluster Verification Check "OS Kernel Parameter: semopm" succeeded on node "ol59b", expected value: 100 actual value: Current=100; Configured=100.
Cluster Verification check "OS Kernel Parameter: semopm" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semopm" is properly set.
Cluster Verification Check "OS Kernel Parameter: semmni" succeeded on node "ol59a", expected value: 128 actual value: Current=142; Configured=142.
Cluster Verification Check "OS Kernel Parameter: semmni" succeeded on node "ol59b", expected value: 128 actual value: Current=128; Configured=128.
Cluster Verification check "OS Kernel Parameter: semmni" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmni" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmmax" succeeded on node "ol59a", expected value: 1581674496 actual value: Current=4398046511104; Configured=4398046511104.
Cluster Verification Check "OS Kernel Parameter: shmmax" succeeded on node "ol59b", expected value: 1581674496 actual value: Current=68719476736; Configured=68719476736.
Cluster Verification check "OS Kernel Parameter: shmmax" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmmax" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmmni" succeeded on node "ol59a", expected value: 4096 actual value: Current=4096; Configured=4096.
Cluster Verification Check "OS Kernel Parameter: shmmni" succeeded on node "ol59b", expected value: 4096 actual value: Current=4096; Configured=4096.
Cluster Verification check "OS Kernel Parameter: shmmni" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmmni" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmall" succeeded on node "ol59a", expected value: 308920 actual value: Current=1073741824; Configured=1073741824.
Cluster Verification Check "OS Kernel Parameter: shmall" succeeded on node "ol59b", expected value: 308920 actual value: Current=4294967296; Configured=4294967296.
Cluster Verification check "OS Kernel Parameter: shmall" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmall" is properly set.
Cluster Verification Check "OS Kernel Parameter: file-max" succeeded on node "ol59a", expected value: 6815744 actual value: Current=6815744; Configured=6815744.
Cluster Verification Check "OS Kernel Parameter: file-max" succeeded on node "ol59b", expected value: 6815744 actual value: Current=6815744; Configured=6815744.
Cluster Verification check "OS Kernel Parameter: file-max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "file-max" is properly set.
Cluster Verification Check "OS Kernel Parameter: ip_local_port_range" succeeded on node "ol59a", expected value: between 9000 & 65535 actual value: Current=between 9000 & 65500; Configured=between 9000 & 65500.
Cluster Verification Check "OS Kernel Parameter: ip_local_port_range" succeeded on node "ol59b", expected value: between 9000 & 65535 actual value: Current=between 9000 & 65535; Configured=between 9000 & 65535.
Cluster Verification check "OS Kernel Parameter: ip_local_port_range" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "ip_local_port_range" is properly set.
Cluster Verification Check "OS Kernel Parameter: rmem_default" succeeded on node "ol59a", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification Check "OS Kernel Parameter: rmem_default" succeeded on node "ol59b", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification check "OS Kernel Parameter: rmem_default" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "rmem_default" is properly set.
Cluster Verification Check "OS Kernel Parameter: rmem_max" succeeded on node "ol59a", expected value: 4194304 actual value: Current=4194304; Configured=4194304.
Cluster Verification Check "OS Kernel Parameter: rmem_max" succeeded on node "ol59b", expected value: 4194304 actual value: Current=4194304; Configured=4194304.
Cluster Verification check "OS Kernel Parameter: rmem_max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "rmem_max" is properly set.
Cluster Verification Check "OS Kernel Parameter: wmem_default" succeeded on node "ol59a", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification Check "OS Kernel Parameter: wmem_default" succeeded on node "ol59b", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification check "OS Kernel Parameter: wmem_default" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "wmem_default" is properly set.
Cluster Verification Check "OS Kernel Parameter: wmem_max" succeeded on node "ol59a", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification Check "OS Kernel Parameter: wmem_max" succeeded on node "ol59b", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification check "OS Kernel Parameter: wmem_max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "wmem_max" is properly set.
Cluster Verification Check "OS Kernel Parameter: aio-max-nr" succeeded on node "ol59a", expected value: 1048576 actual value: Current=3145728; Configured=3145728.
Cluster Verification Check "OS Kernel Parameter: aio-max-nr" succeeded on node "ol59b", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification check "OS Kernel Parameter: aio-max-nr" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "aio-max-nr" is properly set.
Cluster Verification Check "Package: make-3.81" succeeded on node "ol59a", expected value: make-3.81 actual value: make-3.81-3.el5.
Cluster Verification Check "Package: make-3.81" succeeded on node "ol59b", expected value: make-3.81 actual value: make-3.81-3.el5.
Cluster Verification check "Package: make-3.81" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "make-3.81" is available on the system.
Cluster Verification Check "Package: binutils-2.17.50.0.6" succeeded on node "ol59a", expected value: binutils-2.17.50.0.6 actual value: binutils-2.17.50.0.6-20.el5_8.3.
Cluster Verification Check "Package: binutils-2.17.50.0.6" succeeded on node "ol59b", expected value: binutils-2.17.50.0.6 actual value: binutils-2.17.50.0.6-20.el5_8.3.
Cluster Verification check "Package: binutils-2.17.50.0.6" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "binutils-2.17.50.0.6" is available on the system.
Cluster Verification Check "Package: gcc-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: gcc(x86_64)-4.1.2 actual value: gcc(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: gcc-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: gcc(x86_64)-4.1.2 actual value: gcc(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: gcc-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "gcc-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libaio-0.3.106 (x86_64)" succeeded on node "ol59a", expected value: libaio(x86_64)-0.3.106 actual value: libaio(x86_64)-0.3.106-5.
Cluster Verification Check "Package: libaio-0.3.106 (x86_64)" succeeded on node "ol59b", expected value: libaio(x86_64)-0.3.106 actual value: libaio(x86_64)-0.3.106-5.
Cluster Verification check "Package: libaio-0.3.106 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libaio-0.3.106 (x86_64)" is available on the system.
Cluster Verification Check "Package: glibc-2.5-58 (x86_64)" succeeded on node "ol59a", expected value: glibc(x86_64)-2.5-58 actual value: glibc(x86_64)-2.5-107.
Cluster Verification Check "Package: glibc-2.5-58 (x86_64)" succeeded on node "ol59b", expected value: glibc(x86_64)-2.5-58 actual value: glibc(x86_64)-2.5-107.
Cluster Verification check "Package: glibc-2.5-58 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "glibc-2.5-58 (x86_64)" is available on the system.
Cluster Verification Check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on node "ol59a", expected value: compat-libstdc++-33(x86_64)-3.2.3 actual value: compat-libstdc++-33(x86_64)-3.2.3-61.
Cluster Verification Check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on node "ol59b", expected value: compat-libstdc++-33(x86_64)-3.2.3 actual value: compat-libstdc++-33(x86_64)-3.2.3-61.
Cluster Verification check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "compat-libstdc++-33-3.2.3 (x86_64)" is available on the system.
Cluster Verification Check "Package: glibc-devel-2.5 (x86_64)" succeeded on node "ol59a", expected value: glibc-devel(x86_64)-2.5 actual value: glibc-devel(x86_64)-2.5-107.
Cluster Verification Check "Package: glibc-devel-2.5 (x86_64)" succeeded on node "ol59b", expected value: glibc-devel(x86_64)-2.5 actual value: glibc-devel(x86_64)-2.5-107.
Cluster Verification check "Package: glibc-devel-2.5 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "glibc-devel-2.5 (x86_64)" is available on the system.
Cluster Verification Check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: gcc-c++(x86_64)-4.1.2 actual value: gcc-c++(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: gcc-c++(x86_64)-4.1.2 actual value: gcc-c++(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "gcc-c++-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on node "ol59a", expected value: libaio-devel(x86_64)-0.3.106 actual value: libaio-devel(x86_64)-0.3.106-5.
Cluster Verification Check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on node "ol59b", expected value: libaio-devel(x86_64)-0.3.106 actual value: libaio-devel(x86_64)-0.3.106-5.
Cluster Verification check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libaio-devel-0.3.106 (x86_64)" is available on the system.
Cluster Verification Check "Package: libgcc-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libgcc(x86_64)-4.1.2 actual value: libgcc(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libgcc-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libgcc(x86_64)-4.1.2 actual value: libgcc(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libgcc-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libgcc-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libstdc++-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libstdc++(x86_64)-4.1.2 actual value: libstdc++(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libstdc++-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libstdc++(x86_64)-4.1.2 actual value: libstdc++(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libstdc++-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libstdc++-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libstdc++-devel(x86_64)-4.1.2 actual value: libstdc++-devel(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libstdc++-devel(x86_64)-4.1.2 actual value: libstdc++-devel(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libstdc++-devel-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: sysstat-7.0.2" succeeded on node "ol59a", expected value: sysstat-7.0.2 actual value: sysstat-7.0.2-12.0.1.el5.
Cluster Verification Check "Package: sysstat-7.0.2" succeeded on node "ol59b", expected value: sysstat-7.0.2 actual value: sysstat-7.0.2-12.0.1.el5.
Cluster Verification check "Package: sysstat-7.0.2" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "sysstat-7.0.2" is available on the system.
Cluster Verification Check "Package: ksh-..." succeeded on node "ol59a", expected value: ksh-... actual value: ksh-20100621-12.el5.
Cluster Verification Check "Package: ksh-..." succeeded on node "ol59b", expected value: ksh-... actual value: ksh-20100621-12.el5.
Cluster Verification check "Package: ksh-..." succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "ksh-..." is available on the system.
Cluster Verification check "Users With Same UID" succeeded on nodes: ol59a,ol59b.
This test checks that multiple users do not exist with user id as "0".
Cluster Verification check "Current Group ID" succeeded on nodes: ol59a,ol59b.
This test verifies that the user is currently logged in to the user's primary group.
Cluster Verification check "Root user consistency" succeeded on nodes: ol59a,ol59b.
This test checks the consistency of the primary group of the root user across the cluster nodes
Cluster Verification check "CRS Integrity" succeeded on nodes: ol59a,ol59b.
This test checks the integrity of Oracle Clusterware stack across the cluster nodes.
Cluster Verification check "Node Application Existence" succeeded on nodes: ol59a,ol59b.
This test checks the existence of Node Applications on the system.
Cluster Verification check "Time zone consistency" succeeded on nodes: ol59a,ol59b.
This task checks for the consistency of time zones across systems.

Cluster Verification check "Node Connectivity" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether connectivity exists amongst all the nodes. The connectivity is being tested for the subnets "192.168.1.0,10.0.0.0"
Cluster Verification check "Multicast check" succeeded on nodes: ol59a,ol59b.
This task checks that network interfaces in subnet are able to communicate over multicast IP address
Cluster Verification Check "Physical Memory" succeeded on node "ol59a", expected value: 1GB (1048576.0KB) actual value: 2.9461GB (3089208.0KB).
Cluster Verification Check "Physical Memory" succeeded on node "ol59b", expected value: 1GB (1048576.0KB) actual value: 2.9461GB (3089208.0KB).
Cluster Verification check "Physical Memory" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has at least 1GB (1048576.0KB) of total physical memory.
Cluster Verification Check "Available Physical Memory" succeeded on node "ol59a", expected value: 50MB (51200.0KB) actual value: 2.3107GB (2422936.0KB).
Cluster Verification Check "Available Physical Memory" succeeded on node "ol59b", expected value: 50MB (51200.0KB) actual value: 2.3824GB (2498168.0KB).
Cluster Verification check "Available Physical Memory" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has at least 50MB (51200.0KB) of available physical memory.
Cluster Verification Check "Swap Size" succeeded on node "ol59b", expected value: 2.9461GB (3089208.0KB) actual value: 3.9062GB (4095996.0KB).
Cluster Verification Check "Swap Size" failed on node "ol59a", expected value: 2.9461GB (3089208.0KB) actual value: 1.9687GB (2064380.0KB).
PRVF-7573 : Sufficient swap size is not available on node "ol59a" [Required = 2.9461GB (3089208.0KB) ; Found = 1.9687GB (2064380.0KB)]
Cluster Verification check failed on nodes: ol59a.
This is a prerequisite condition to test whether sufficient total swap space is available on the system.
Cluster Verification Check "Free Space: ol59b:/tmp" succeeded on node "ol59b", expected value: 1GB  actual value: 2.4834GB .
Cluster Verification check "Free Space: ol59b:/tmp" succeeded on nodes: ol59b.
This is a prerequisite condition to test whether sufficient free space is available in the file system.
Cluster Verification Check "Free Space: ol59a:/tmp" succeeded on node "ol59a", expected value: 1GB  actual value: 3.9453GB .
Cluster Verification check "Free Space: ol59a:/tmp" succeeded on nodes: ol59a.
This is a prerequisite condition to test whether sufficient free space is available in the file system.
Cluster Verification check "User Existence: oracle" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether user "oracle" exists on the system.
Cluster Verification Check "Run Level" succeeded on node "ol59a", expected value: 3,5 actual value: 5.
Cluster Verification Check "Run Level" succeeded on node "ol59b", expected value: 3,5 actual value: 5.
Cluster Verification check "Run Level" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system is running with proper run level.
Cluster Verification Check "Hard Limit: maximum open file descriptors" succeeded on node "ol59a", expected value: 65536 actual value: 131072.
Cluster Verification Check "Hard Limit: maximum open file descriptors" succeeded on node "ol59b", expected value: 65536 actual value: 65536.
Cluster Verification check "Hard Limit: maximum open file descriptors" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the hard limit for "maximum open file descriptors" is set correctly.
Cluster Verification Check "Soft Limit: maximum open file descriptors" succeeded on node "ol59a", expected value: 1024 actual value: 131072.
Cluster Verification Check "Soft Limit: maximum open file descriptors" succeeded on node "ol59b", expected value: 1024 actual value: 1024.
Cluster Verification check "Soft Limit: maximum open file descriptors" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the soft limit for "maximum open file descriptors" is set correctly.
Cluster Verification Check "Hard Limit: maximum user processes" succeeded on node "ol59a", expected value: 16384 actual value: 131072.
Cluster Verification Check "Hard Limit: maximum user processes" succeeded on node "ol59b", expected value: 16384 actual value: 16384.
Cluster Verification check "Hard Limit: maximum user processes" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the hard limit for "maximum user processes" is set correctly.
Cluster Verification Check "Soft Limit: maximum user processes" succeeded on node "ol59a", expected value: 2047 actual value: 131072.
Cluster Verification Check "Soft Limit: maximum user processes" succeeded on node "ol59b", expected value: 2047 actual value: 16384.
Cluster Verification check "Soft Limit: maximum user processes" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the soft limit for "maximum user processes" is set correctly.
Cluster Verification Check "Architecture" succeeded on node "ol59a", expected value: x86_64 actual value: x86_64.
Cluster Verification Check "Architecture" succeeded on node "ol59b", expected value: x86_64 actual value: x86_64.
Cluster Verification check "Architecture" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system has a certified architecture.
Cluster Verification Check "OS Kernel Version" succeeded on node "ol59a", expected value: 2.6.18 actual value: 2.6.39-400.109.4.el5uek.
Cluster Verification Check "OS Kernel Version" succeeded on node "ol59b", expected value: 2.6.18 actual value: 2.6.39-400.109.4.el5uek.
Cluster Verification check "OS Kernel Version" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the system kernel version is at least "2.6.18".
Cluster Verification Check "OS Kernel Parameter: semmsl" succeeded on node "ol59a", expected value: 250 actual value: Current=250; Configured=250.
Cluster Verification Check "OS Kernel Parameter: semmsl" succeeded on node "ol59b", expected value: 250 actual value: Current=250; Configured=250.
Cluster Verification check "OS Kernel Parameter: semmsl" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmsl" is properly set.
Cluster Verification Check "OS Kernel Parameter: semmns" succeeded on node "ol59a", expected value: 32000 actual value: Current=32000; Configured=32000.
Cluster Verification Check "OS Kernel Parameter: semmns" succeeded on node "ol59b", expected value: 32000 actual value: Current=32000; Configured=32000.
Cluster Verification check "OS Kernel Parameter: semmns" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmns" is properly set.
Cluster Verification Check "OS Kernel Parameter: semopm" succeeded on node "ol59a", expected value: 100 actual value: Current=100; Configured=100.
Cluster Verification Check "OS Kernel Parameter: semopm" succeeded on node "ol59b", expected value: 100 actual value: Current=100; Configured=100.
Cluster Verification check "OS Kernel Parameter: semopm" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semopm" is properly set.
Cluster Verification Check "OS Kernel Parameter: semmni" succeeded on node "ol59a", expected value: 128 actual value: Current=142; Configured=142.
Cluster Verification Check "OS Kernel Parameter: semmni" succeeded on node "ol59b", expected value: 128 actual value: Current=128; Configured=128.
Cluster Verification check "OS Kernel Parameter: semmni" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "semmni" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmmax" succeeded on node "ol59a", expected value: 1581674496 actual value: Current=4398046511104; Configured=4398046511104.
Cluster Verification Check "OS Kernel Parameter: shmmax" succeeded on node "ol59b", expected value: 1581674496 actual value: Current=68719476736; Configured=68719476736.
Cluster Verification check "OS Kernel Parameter: shmmax" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmmax" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmmni" succeeded on node "ol59a", expected value: 4096 actual value: Current=4096; Configured=4096.
Cluster Verification Check "OS Kernel Parameter: shmmni" succeeded on node "ol59b", expected value: 4096 actual value: Current=4096; Configured=4096.
Cluster Verification check "OS Kernel Parameter: shmmni" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmmni" is properly set.
Cluster Verification Check "OS Kernel Parameter: shmall" succeeded on node "ol59a", expected value: 308920 actual value: Current=1073741824; Configured=1073741824.
Cluster Verification Check "OS Kernel Parameter: shmall" succeeded on node "ol59b", expected value: 308920 actual value: Current=4294967296; Configured=4294967296.
Cluster Verification check "OS Kernel Parameter: shmall" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "shmall" is properly set.
Cluster Verification Check "OS Kernel Parameter: file-max" succeeded on node "ol59a", expected value: 6815744 actual value: Current=6815744; Configured=6815744.
Cluster Verification Check "OS Kernel Parameter: file-max" succeeded on node "ol59b", expected value: 6815744 actual value: Current=6815744; Configured=6815744.
Cluster Verification check "OS Kernel Parameter: file-max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "file-max" is properly set.
Cluster Verification Check "OS Kernel Parameter: ip_local_port_range" succeeded on node "ol59a", expected value: between 9000 & 65535 actual value: Current=between 9000 & 65500; Configured=between 9000 & 65500.
Cluster Verification Check "OS Kernel Parameter: ip_local_port_range" succeeded on node "ol59b", expected value: between 9000 & 65535 actual value: Current=between 9000 & 65535; Configured=between 9000 & 65535.
Cluster Verification check "OS Kernel Parameter: ip_local_port_range" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "ip_local_port_range" is properly set.
Cluster Verification Check "OS Kernel Parameter: rmem_default" succeeded on node "ol59a", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification Check "OS Kernel Parameter: rmem_default" succeeded on node "ol59b", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification check "OS Kernel Parameter: rmem_default" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "rmem_default" is properly set.
Cluster Verification Check "OS Kernel Parameter: rmem_max" succeeded on node "ol59a", expected value: 4194304 actual value: Current=4194304; Configured=4194304.
Cluster Verification Check "OS Kernel Parameter: rmem_max" succeeded on node "ol59b", expected value: 4194304 actual value: Current=4194304; Configured=4194304.
Cluster Verification check "OS Kernel Parameter: rmem_max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "rmem_max" is properly set.
Cluster Verification Check "OS Kernel Parameter: wmem_default" succeeded on node "ol59a", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification Check "OS Kernel Parameter: wmem_default" succeeded on node "ol59b", expected value: 262144 actual value: Current=262144; Configured=262144.
Cluster Verification check "OS Kernel Parameter: wmem_default" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "wmem_default" is properly set.
Cluster Verification Check "OS Kernel Parameter: wmem_max" succeeded on node "ol59a", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification Check "OS Kernel Parameter: wmem_max" succeeded on node "ol59b", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification check "OS Kernel Parameter: wmem_max" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "wmem_max" is properly set.
Cluster Verification Check "OS Kernel Parameter: aio-max-nr" succeeded on node "ol59a", expected value: 1048576 actual value: Current=3145728; Configured=3145728.
Cluster Verification Check "OS Kernel Parameter: aio-max-nr" succeeded on node "ol59b", expected value: 1048576 actual value: Current=1048576; Configured=1048576.
Cluster Verification check "OS Kernel Parameter: aio-max-nr" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the OS kernel parameter "aio-max-nr" is properly set.
Cluster Verification Check "Package: make-3.81" succeeded on node "ol59a", expected value: make-3.81 actual value: make-3.81-3.el5.
Cluster Verification Check "Package: make-3.81" succeeded on node "ol59b", expected value: make-3.81 actual value: make-3.81-3.el5.
Cluster Verification check "Package: make-3.81" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "make-3.81" is available on the system.
Cluster Verification Check "Package: binutils-2.17.50.0.6" succeeded on node "ol59a", expected value: binutils-2.17.50.0.6 actual value: binutils-2.17.50.0.6-20.el5_8.3.
Cluster Verification Check "Package: binutils-2.17.50.0.6" succeeded on node "ol59b", expected value: binutils-2.17.50.0.6 actual value: binutils-2.17.50.0.6-20.el5_8.3.
Cluster Verification check "Package: binutils-2.17.50.0.6" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "binutils-2.17.50.0.6" is available on the system.
Cluster Verification Check "Package: gcc-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: gcc(x86_64)-4.1.2 actual value: gcc(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: gcc-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: gcc(x86_64)-4.1.2 actual value: gcc(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: gcc-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "gcc-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libaio-0.3.106 (x86_64)" succeeded on node "ol59a", expected value: libaio(x86_64)-0.3.106 actual value: libaio(x86_64)-0.3.106-5.
Cluster Verification Check "Package: libaio-0.3.106 (x86_64)" succeeded on node "ol59b", expected value: libaio(x86_64)-0.3.106 actual value: libaio(x86_64)-0.3.106-5.
Cluster Verification check "Package: libaio-0.3.106 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libaio-0.3.106 (x86_64)" is available on the system.
Cluster Verification Check "Package: glibc-2.5-58 (x86_64)" succeeded on node "ol59a", expected value: glibc(x86_64)-2.5-58 actual value: glibc(x86_64)-2.5-107.
Cluster Verification Check "Package: glibc-2.5-58 (x86_64)" succeeded on node "ol59b", expected value: glibc(x86_64)-2.5-58 actual value: glibc(x86_64)-2.5-107.
Cluster Verification check "Package: glibc-2.5-58 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "glibc-2.5-58 (x86_64)" is available on the system.
Cluster Verification Check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on node "ol59a", expected value: compat-libstdc++-33(x86_64)-3.2.3 actual value: compat-libstdc++-33(x86_64)-3.2.3-61.
Cluster Verification Check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on node "ol59b", expected value: compat-libstdc++-33(x86_64)-3.2.3 actual value: compat-libstdc++-33(x86_64)-3.2.3-61.
Cluster Verification check "Package: compat-libstdc++-33-3.2.3 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "compat-libstdc++-33-3.2.3 (x86_64)" is available on the system.
Cluster Verification Check "Package: glibc-devel-2.5 (x86_64)" succeeded on node "ol59a", expected value: glibc-devel(x86_64)-2.5 actual value: glibc-devel(x86_64)-2.5-107.
Cluster Verification Check "Package: glibc-devel-2.5 (x86_64)" succeeded on node "ol59b", expected value: glibc-devel(x86_64)-2.5 actual value: glibc-devel(x86_64)-2.5-107.
Cluster Verification check "Package: glibc-devel-2.5 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "glibc-devel-2.5 (x86_64)" is available on the system.
Cluster Verification Check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: gcc-c++(x86_64)-4.1.2 actual value: gcc-c++(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: gcc-c++(x86_64)-4.1.2 actual value: gcc-c++(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: gcc-c++-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "gcc-c++-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on node "ol59a", expected value: libaio-devel(x86_64)-0.3.106 actual value: libaio-devel(x86_64)-0.3.106-5.
Cluster Verification Check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on node "ol59b", expected value: libaio-devel(x86_64)-0.3.106 actual value: libaio-devel(x86_64)-0.3.106-5.
Cluster Verification check "Package: libaio-devel-0.3.106 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libaio-devel-0.3.106 (x86_64)" is available on the system.
Cluster Verification Check "Package: libgcc-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libgcc(x86_64)-4.1.2 actual value: libgcc(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libgcc-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libgcc(x86_64)-4.1.2 actual value: libgcc(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libgcc-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libgcc-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libstdc++-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libstdc++(x86_64)-4.1.2 actual value: libstdc++(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libstdc++-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libstdc++(x86_64)-4.1.2 actual value: libstdc++(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libstdc++-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libstdc++-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on node "ol59a", expected value: libstdc++-devel(x86_64)-4.1.2 actual value: libstdc++-devel(x86_64)-4.1.2-54.el5.
Cluster Verification Check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on node "ol59b", expected value: libstdc++-devel(x86_64)-4.1.2 actual value: libstdc++-devel(x86_64)-4.1.2-54.el5.
Cluster Verification check "Package: libstdc++-devel-4.1.2 (x86_64)" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "libstdc++-devel-4.1.2 (x86_64)" is available on the system.
Cluster Verification Check "Package: sysstat-7.0.2" succeeded on node "ol59a", expected value: sysstat-7.0.2 actual value: sysstat-7.0.2-12.0.1.el5.
Cluster Verification Check "Package: sysstat-7.0.2" succeeded on node "ol59b", expected value: sysstat-7.0.2 actual value: sysstat-7.0.2-12.0.1.el5.
Cluster Verification check "Package: sysstat-7.0.2" succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "sysstat-7.0.2" is available on the system.
Cluster Verification Check "Package: ksh-..." succeeded on node "ol59a", expected value: ksh-... actual value: ksh-20100621-12.el5.
Cluster Verification Check "Package: ksh-..." succeeded on node "ol59b", expected value: ksh-... actual value: ksh-20100621-12.el5.
Cluster Verification check "Package: ksh-..." succeeded on nodes: ol59a,ol59b.
This is a prerequisite condition to test whether the package "ksh-..." is available on the system.
Cluster Verification check "Users With Same UID" succeeded on nodes: ol59a,ol59b.
This test checks that multiple users do not exist with user id as "0".
Cluster Verification check "Current Group ID" succeeded on nodes: ol59a,ol59b.
This test verifies that the user is currently logged in to the user's primary group.
Cluster Verification check "Root user consistency" succeeded on nodes: ol59a,ol59b.
This test checks the consistency of the primary group of the root user across the cluster nodes
Cluster Verification check "CRS Integrity" succeeded on nodes: ol59a,ol59b.
This test checks the integrity of Oracle Clusterware stack across the cluster nodes.
Cluster Verification check "Node Application Existence" succeeded on nodes: ol59a,ol59b.
This test checks the existence of Node Applications on the system.
Cluster Verification check "Time zone consistency" succeeded on nodes: ol59a,ol59b.
This task checks for the consistency of time zones across systems.

Unique database identifier check passed.
Validation of server pool succeeded.
Default listener validation succeeded.
Scan listener validation succeeded.

+DATA is  shared across the cluster nodes.
+FRA is  shared across the cluster nodes.
+FRA has enough space. Required space is 5625 MB , available space is 7628 MB.
+DATA has enough space. Required space is 4645 MB , available space is 27912 MB.
File Validations Successful.
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 2%
DBCA_PROGRESS : 23%
Creating and starting Oracle instance
DBCA_PROGRESS : 24%
DBCA_PROGRESS : 27%
DBCA_PROGRESS : 28%
DBCA_PROGRESS : 29%
DBCA_PROGRESS : 32%
DBCA_PROGRESS : 35%
DBCA_PROGRESS : 36%
DBCA_PROGRESS : 38%
Creating cluster database views
DBCA_PROGRESS : 40%
DBCA_PROGRESS : 54%
Completing Database Creation
DBCA_PROGRESS : 56%
DBCA_PROGRESS : 58%
DBCA_PROGRESS : 65%
DBCA_PROGRESS : 67%
DBCA_PROGRESS : 74%
DBCA_PROGRESS : 77%
Creating Pluggable Databases
DBCA_PROGRESS : 81%
DBCA_PROGRESS : 86%
DBCA_PROGRESS : 100%
Database creation complete. For details check the logfiles at:
 /u01/app/oracle/cfgtoollogs/dbca/TEST.
Database Information:
Global Database Name:TEST
System Identifier(SID) Prefix:TEST