This chapter describes the system configuration tasks that you must complete before you start Oracle Universal Installer (OUI) to install Oracle Grid Infrastructure for a cluster, and that you may need to complete if you intend to install Oracle Real Application Clusters (Oracle RAC) on the cluster.
This chapter contains the following topics:
Reviewing Operating System and Software Upgrade Best Practices
Operating System Requirements for IBM AIX on POWER Systems (64-Bit)
Additional Drivers and Software Packages for IBM AIX on POWER Systems (64-Bit)
Setting Network Time Protocol for Cluster Time Synchronization
Review the following information regarding upgrades:
If you have an existing Oracle installation, then do the following:
Caution:
Always create a backup of existing databases before starting any configuration change.Record the version numbers, patches, and other configuration information
Review upgrade procedures for your existing installation
Review Oracle upgrade documentation before proceeding with installation, to decide how you want to proceed
To find the most recent software updates, and to find best practices recommendations about preupgrade, postupgrade, compatibility, and interoperability, see Oracle 12c Upgrade Companion (My Oracle Support Note 1462240.1):
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1462240.1
Be aware of the following issues regarding Oracle ASM upgrades:
You can upgrade Oracle Automatic Storage Management (Oracle ASM) 11g Release 1 (11.1) and later without shutting down an Oracle RAC database by performing a rolling upgrade either of individual nodes, or of a set of nodes in the cluster. However, if you have a standalone database on a cluster that uses Oracle ASM, then you must shut down the standalone database before upgrading. If you are upgrading from Oracle ASM 10g, then you must shut down the entire Oracle ASM cluster to perform the upgrade.
The location of the Oracle ASM home changed in Oracle Grid Infrastructure 11g Release 2 (11.2) so that Oracle ASM is installed with Oracle Clusterware in the Oracle Grid Infrastructure home (Grid home).
If you have an existing Oracle ASM home from a previous release, then it should be owned by the same user that you plan to use to upgrade Oracle Clusterware.
Be aware of the following information regarding rolling upgrades:
During rolling upgrades of the operating system, Oracle supports using different operating system binaries when both versions of the operating system are certified with the Oracle Database release you are using.
Using mixed operating system versions is supported during upgrade only.
Be aware that mixed operating systems are supported only supported for the duration of an upgrade, over the period of a few hours.
Oracle Clusterware does not support nodes that have processors with different instruction set architectures (ISAs) in the same cluster. Each node must be binary compatible with the other nodes in the cluster.
For example, you cannot have one node using an Intel 64 processor and another node using an IA-64 (Itanium) processor in the same cluster. You could have one node using an Intel 64 processor and another node using an AMD64 processor in the same cluster because the processors use the same x86-64 ISA and run the same binary version of Oracle software.
Secure operating systems are an important basis for general system security. Ensure that your operating system deployment is in compliance with common security practices as described in your operating system vendor security guide.
Oracle Universal Installer (OUI) detects when the minimum requirements for an installation are not met, and creates shell scripts, called Fixup scripts, to finish incomplete system configuration steps. If OUI detects an incomplete task, then it generates a Fixup script (runfixup.sh). You can run the script after you click Fix and Check Again.
You also can set CVU to generate Fixup scripts before installation.
See Also:
Oracle Clusterware Administration and Deployment Guide for information about using thecluvfy commandFixup scripts do the following:
If necessary, set kernel parameters to values required for successful installation, including:
Shared memory parameters.
Open file descriptor and UDP send/receive parameters.
Create and set permissions on the Oracle Inventory (central inventory) directory.
Create or reconfigure primary and secondary group memberships for the installation owner, if necessary, for the Oracle Inventory directory and the operating system privileges groups.
Set shell limits if necessary to required values.
If you have SSH configured between cluster member nodes for the user account that you will use for installation, then you can check your cluster configuration before installation and generate a fixup script to make operating system changes before starting the installation.
To do this, log in as the user account that will perform the installation, navigate to the staging area where the runcluvfy command is located, and use the following command syntax, where node is a comma-delimited list of nodes you want to make cluster members:
$ ./runcluvfy.sh stage -pre crsinst -n node -fixup -verbose
For example, if you intend to configure a two-node cluster with nodes node1 and node2, enter the following command:
$ ./runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose
During installation, you are required to perform tasks as root or as other users on remote terminals. Complete the following procedure for user accounts that you want to enable for remote display.
Note:
If you log in as another user (for example,oracle), then repeat this procedure for that user as well.To enable remote display, complete one of the following procedures:
If you are installing the software from an X Window System workstation or X terminal, then:
Start an X terminal session (xterm).
If you are installing the software on another system and using the system as an X11 display, then enter a command using the following syntax to enable remote hosts to display X applications on the local X server:
# xhost + RemoteHost
where RemoteHost is the fully qualified remote host name. For example:
# xhost + somehost.example.com somehost.example.com being added to the access control list
If you are not installing the software on the local system, then use the ssh command to connect to the system where you want to install the software:
# ssh -Y RemoteHost
where RemoteHost is the fully qualified remote host name. The -Y flag ("yes") enables remote X11 clients to have full access to the original X11 display.For example:
# ssh -Y somehost.example.com
If you are not logged in as the root user, then enter the following command to switch the user to root:
$ su - root password: #
If you are installing the software from a PC or other system with X server software installed, then:
Note:
If necessary, see your X Window System documentation for more information about completing this procedure. Depending on the X software that you are using, you may need to complete the tasks in a different order.Start the X Window System software.
Configure the security settings of the X Window System software to permit remote hosts to display X applications on the local system.
Connect to the remote system where you want to install the software as the Oracle Grid Infrastructure for a cluster software owner (grid, oracle) and start a terminal session on that system; for example, an X terminal (xterm).
Open another terminal on the remote system, and log in as the root user on the remote system, so you can run scripts as root when prompted.
Depending on the products that you intend to install, verify that you have the required operating system kernel and packages installed.
Requirements listed in this document are current as of the date listed on the title page. To obtain the most current information about kernel requirements, see the online version on the Oracle Technology Network at the following URL:
http://www.oracle.com/technetwork/indexes/documentation/index.html
OUI performs checks on your system to verify that it meets the listed operating system package requirements. To ensure that these checks complete successfully, verify the requirements before you start OUI.
The filesets and Authorized Problem Analysis Reports (APARs) listed in this section are supported on IBM AIX on POWER Systems (64-Bit) systems for Oracle Database and Oracle Grid Infrastructure 12c:
Use the following information to check the minimum supported IBM AIX 7.1 on POWER Systems (64-Bit) versions:
Table 3-1 IBM AIX 7.1 on POWER Systems (64-Bit) Minimum Operating System Requirements
| Item | Minimum Requirements |
|---|---|
|
AIX 7.1 Operating System |
AIX 7.1 Technology Level 1 Service Pack 3 ("7100-01-03-1207") or later, 64-bit kernel Note: You can install on AIX 7.1 Technology Level 1, but Oracle recommends that you install on AIX 7.1 Technology Level 3 or later. The latter includes all the APARs and operating system fixes listed in this table. |
|
AIX 7.1 Operating System Filesets |
The following operating system filesets are required:
|
|
AIX 7.1 APARs and Other Operating System Fixes |
The following, or later, patches are required: If you are using the minimum operating system TL level for AIX 7.1 listed above, then install all AIX 7.1 APARs for AIX 7.1 TL1 SP3, and the following AIX fixes:
The following, or later, patch is required if you use Oracle Automatic Storage Management Cluster File System (Oracle ACFS):
The following, or later, patch is also required if you use Oracle Automatic Storage Management Cluster File System (Oracle ACFS). At the time of this release, the patch is unavailable for TL7 so the APAR number refers to the base APAR:
Note:
|
Use the following information to check the minimum supported IBM AIX 6.1 on POWER Systems (64-Bit) versions:
Table 3-2 IBM AIX 6.1 on POWER Systems (64-Bit) Minimum Operating System Requirements
| Item | Minimum Requirements |
|---|---|
|
AIX 6.1 Operating System |
AIX 6.1 Technology Level 7 Service Pack 3 ("6100-07-03-1207") or later, 64-bit kernel Note: You can install on AIX 6.1 Technology Level 7, but Oracle recommends that you install on AIX 6.1 Technology Level 9 Service Pack 3 (6100-09-03-1415) or later. The latter includes all the APARs and operating system fixes listed in this table. |
|
AIX 6.1 Operating System Filesets |
The following operating system filesets are required:
|
|
AIX 6.1 APARs and Other Operating System Fixes |
The following, or later, patches are required: If you are using the minimum operating system TL level for AIX 6.1 listed above, then install all the following AIX APAR fixes:
The following, or later, patch is required if you use Oracle Automatic Storage Management Cluster File System (Oracle ACFS):
The following, or later, patch is also required if you use Oracle Automatic Storage Management Cluster File System (Oracle ACFS). At the time of this release, the patch is unavailable for TL7 so the APAR number refers to the base APAR:
Note:
|
You are not required to install additional drivers and packages, but you may choose to install or configure drivers and packages in the following list:
See Also:
"Oracle Application Express Installation Requirements" and "Recommended Pre-installation Tasks" in Oracle Application Express Installation GuideReview the following sections if you plan to install Open Database Connectivity (ODBC):
Open Database Connectivity (ODBC) is a set of database access APIs that connect to the database, prepare, and then run SQL statements on the database. An application that uses an ODBC driver can access non-uniform data sources, such as spreadsheets and comma-delimited files.
Oracle ODBC driver on IBM AIX is certified with ODBC Driver Manager 2.3.1. To use ODBC with Oracle Database, you must also install gcc 4.2.1 or later.
You do not require ODBC drivers for Oracle Clusterware or Oracle Database.
Download and install the ODBC Driver from the following website:
Review the following sections to install Oracle Messaging Gateway:
Oracle Messaging Gateway is a feature of the Oracle database. It enables communication between applications based on non-Oracle messaging systems and Oracle Streams Advanced Queuing.
Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with with applications based on WebSphere and TIBCO Rendezvous. For information on supported versions, see Oracle Database Advanced Queuing User's Guide.
Oracle Messaging Gateway is installed with Oracle Database.
For AIX7.1, check My Oracle Support Certification for current requirements:
https://support.oracle.com
If you require a CSD for IBM WebSphere MQ, then see the following website for download and installation information:
Review the following sections to install programming environments:
Oracle Database supports multiple programming languages for application development in different environments. Some languages require that you install additional compiler packages for the operating system.
Programming environments are options. They are not required for Oracle Database.
See Also :
Oracle Database Advanced Application Developer's Guide for an overview of programming environmentsEnsure that your system meets the requirements for the programming environment you want to configure:
Table 3-3 Requirements for Programming Environments for IBM AIX on POWER Systems (64-Bit)
| Programming Environments | Support Requirements |
|---|---|
|
Java Database Connectivity (JDBC) / Oracle Call Interface (OCI) |
JDK 6 (Java 6 64-bit 6.0.0.325 SR10 ) or later with the JNDI extension with Oracle Java Database Connectivity and Oracle Call Interface drivers. JDK 7 (Java 7 64-bit 7.0.0.0 ) or later with the JNDI extension with Oracle Java Database Connectivity and Oracle Call Interface drivers. JDK 1.6 is installed with this release. Note: These are not mandatory for the database installation. |
Oracle C++ Oracle C++ Call Interface Pro*C/C++ Oracle XML Developer's Kit (XDK) |
IBM XL C/C++ Enterprise Edition for AIX, V11.1 (11.1.0.9) January 2012 PTF. IBM XL C++ Runtime for AIX, V11.1 (11.1.0.4) November 2011. Download this software from the following URL: http://www-01.ibm.com/support/docview.wss?uid=swg24031864 http://www-01.ibm.com/support/docview.wss?uid=swg24031426 Note: Even if you do not install the IBM XL C/C++ compiler, you require the compiler for the AIX Runtime Environment component. The runtime environment file sets can be downloaded with no license requirements. The minimum recommended runtime environment for IBM AIX is IBM XL C/C++ for AIX V11.1.0.4 Runtime Environment. It is available at the following URL: http://www-01.ibm.com/support/docview.wss?uid=swg24031426 |
|
Pro*COBOL |
IBM COBOL for AIX Version 4.1.1 (March 2012 PTF) Micro Focus Server Express 5.1 |
|
Pro*FORTRAN |
IBM XL Fortran Runtime for AIX, Version 13.1, January 2012 PTF |
|
ADA |
OC Systems PowerAda 5.5 For more information about OC Systems and PowerAda, go to: http://www.ocsystems.com/prod_powerada.html |
|
Oracle RAC and HACMP |
High Availability Cluster Multi-Processing (HACMP) 7.1 Note: HACMP is required only if you want to use raw logical volumes for Oracle Clusterware or database file storage. However, it is supported for all installations. You cannot use raw devices for OCR or voting disk files. If you want to use HACMP or GPFS, then check My Oracle Support Certification for current requirements. Certifications are available at the following URL: https://support.oracle.com If you do not want to use HACMP, then you must not have HACMP installed on your system. If you want to use HACMP, then review patch sets to ensure that you have required patches. |
|
Oracle RAC and GPFS |
General Parallel File System (GPFS): AIX 7.1: GPFS 3.4.0.19 GPFS 3.5.0.8 AIX 6.1: GPFS 3.4.0.19 GPFS 3.5.0.8 Note: GPFS is not required. Install GPFS only if you want to use a cluster file system in addition to Oracle Clusterware. |
Web browsers are required only if you intend to use Oracle Enterprise Manager Database Express and Oracle Enterprise Manager Cloud Control. Web browsers must support Java Script, and the HTML 4.0 and CSS 1.0 standards. For a list of browsers that meet these requirements see the Enterprise Manager certification matrix on My Oracle Support:
https://support.oracle.com
See Also:
Oracle Enterprise Manager Cloud Control Basic Installation Guide for steps on how to access the Enterprise Manager certification matrixTo ensure that the system meets these requirements, follow these steps:
To determine the distribution and version of AIX installed, enter the following command:
# oslevel -s
If the operating system version is lower than what is listed in Section 3.6, "Operating System Requirements for IBM AIX on POWER Systems (64-Bit)", then upgrade your operating system accordingly to the currently supported or later version and level.
AIX maintenance packages are available from the following web site:
To determine if the required filesets are installed and committed, enter a command similar to the following:
# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \ bos.perf.libperfstat bos.perf.proctools
To determine the supported kernel mode, enter a command similar to the following:
# getconf KERNEL_BITMODE
Note:
The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.
Oracle Database supports 64-bit kernel and does not provide support for 32-bit kernel applications.
To determine if an APAR is installed, enter a command similar to the following:
# /usr/sbin/instfix -i -k "IV16716 IV20880 IV21128 IV28319"
If an APAR is not installed, then download it from the following Web site and install it:
If you require a CSD for WebSphere MQ, then refer to the following Web site for download and installation information:
Note:
Do not run therootpre.sh script if you have a later release of the Oracle Database software already installed on this system.Run the rootpre.sh script:
Switch user to root:
$ su - root
Complete one of the following steps, depending on the location of the installation
If the installation files are on disc, enter a command similar to the following, where directory_path is the disc mount point directory or the path of the database directory on the DVD:
# /directory_path/rootpre.sh
If the installation files are on the hard disk, change directory to the Disk1 directory and enter the following command:
# ./rootpre.sh
Exit from the root account:
# exit
Repeat steps 1 through 3 on all nodes of the cluster.
Note:
Do not run therootpre.sh script if you have a later release of Oracle Database software already installed on this system.On IBM AIX on POWER Systems (64-Bit), enable I/O completion ports (IOCP) to ensure successful database and grid infrastructure installation.
To check if the IOCP module is enabled, run the lsdev command:
$ lsdev | grep iocp
The following sample output shows the IOCP status is set to Defined and hence not enabled:
iocp0 Defined I/O Completion Ports
By default, IOCP is set to Defined. To enable IOCP, set IOCP to Available using the following procedure:
Log in as root and run the following command:
# smitty iocp
Select Change / Show Characteristics of I/O Completion Ports.
Change configured state at system restart from Defined to Available.
Run the lsdev command to confirm the IOCP status is set to Available:
$ lsdev | grep iocp iocp0 Available I/O Completion Ports
Perform a system restart to make the changes permanent.
On AIX platforms, the /etc/security/login.cfg file controls and limits resources for users on the system. On login, control and limit resources should be set for users on the system so that authentication is carried out through the pam.conf file, to prevent denial of service attacks.
By default, resource limits are set to std_auth for AIX operating systems. Edit the file /etc/security/login.cfg file to change auth_type under the usw stanza from std_auth to pam_auth.
To ensure that these resource limits are honored, confirm that the line login session required /usr/lib/security/pam_aix is set in /etc/pam.conf. For example:
dtsession auth required /usr/lib/security/pam_aix dtlogin session required /usr/lib/security/pam_aix ftp session required /usr/lib/security/pam_aix imap session required /usr/lib/security/pam_aix login session required /usr/lib/security/pam_aix rexec session required /usr/lib/security/pam_aix rlogin session required /usr/lib/security/pam_aix rsh session required /usr/lib/security/pam_aix snapp session required /usr/lib/security/pam_aix su session required /usr/lib/security/pam_aix swrole session required /usr/lib/security/pam_aix telnet session required /usr/lib/security/pam_aix xdm session required /usr/lib/security/pam_aix OTHER session required /usr/lib/security/pam_prohibit websm_rlogin session required /usr/lib/security/pam_aix websm_su session required /usr/lib/security/pam_aix wbem session required /usr/lib/security/pam_aix
Perform the following system tuning and configuration all cluster nodes.
Note:
The parameter and shell limit values shown in this section are recommended values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. See your operating system documentation for more information about tuning kernel parameters.Oracle recommends that you use the vmo command to tune virtual memory using the following values:
Table 3-4 Recommended Values for Virtual Memory Manager
| Parameter | Value |
|---|---|
|
minperm% |
3 |
|
maxperm% |
90 |
|
maxclient% = 90 |
90 |
|
lru_file_repage |
0 |
|
strict_maxclient |
1 |
|
strict_maxperm |
0 |
For example:
vmo -p -o minperm%=3 vmo -p -o maxperm%=90 vmo -p -o maxclient%=90 vmo -p -o lru_file_repage=0 vmo -p -o strict_maxclient=1 vmo -p -o strict_maxperm=0
You must restart the system for these changes to take effect.
Oracle recommends that you increase the space allocated for ARG/ENV list to 128. The size is specified by number of 4K blocks.
For example:
/usr/sbin/chdev -l sys0 -a ncargs='1024'
On AIX systems, the OpenSSH parameter LoginGraceTime by default is commented out, and the default behavior of OpenSSH on AIX can sometimes result in timeout errors. To avoid these errors, complete the following procedure:
Log in as root.
Using a text editor, open the OpenSSH configuration file /etc/ssh/sshd_config.
Locate the comment line #LoginGraceTime 2m.
Uncomment the line, and change the value to 0 (unlimited). For example:
LoginGraceTime 0
Save /etc/ssh/sshd_config.
Restart SSH.
Verify that the maximum number of processes allowed for each user is set to 16384 or greater:
Note:
For production systems, this value should be at least 128 plus the sum of thePROCESSES and PARALLEL_MAX_SERVERS initialization parameters for each database running on the system.Enter the following command:
# smit chgsys
Verify that the value shown for Maximum number of PROCESSES allowed for each user is greater than or equal to 16384.
If necessary, edit the existing value.
When you have finished making changes, press Enter, then Esc+0 (Exit) to exit.
Verify that the network tuning parameters shown in the following table are set to the values shown or higher values. The procedure following the table describes how to verify and set the values.
| Network Tuning Parameter | Recommended Value |
|---|---|
| ipqmaxlen | 512 |
| rfc1323 | 1 |
| sb_max | 4194304 |
| tcp_recvspace | 65536 |
| tcp_sendspace | 65536 |
| udp_recvspace | 655360
Note: The recommended value of this parameter is 10 times the value of the udp_sendspace parameter. The value must be less than the value of the sb_max parameter. |
| udp_sendspace | 65536
Note: This value is suitable for a default database installation. For production databases, the minimum value for this parameter is 4 KB plus the value of the database ( |
To view the current value specified for these parameters, and to change them if necessary:
To check the current values of the network tuning parameters, enter commands similar to the following:
# no -a | more
If you must change the value of any parameter, then enter the following command to determine whether the system is running in compatibility mode:
# lsattr -E -l sys0 -a pre520tune
If the system is running in compatibility mode, then the output is similar to the following, showing that the value of the pre520tune attribute is enabled:
pre520tune enable Pre-520 tuning compatibility mode True
If the system is running in compatibility mode, then follow these steps to change the parameter values:
Enter commands similar to the following to change the value of each parameter:
# no -o parameter_name=value
For example:
# no -o udp_recvspace=655360
Add entries similar to the following to the /etc/rc.net file for each parameter that you changed in the previous step:
if [ -f /usr/sbin/no ] ; then /usr/sbin/no -o udp_sendspace=65536 /usr/sbin/no -o udp_recvspace=655360 /usr/sbin/no -o tcp_sendspace=65536 /usr/sbin/no -o tcp_recvspace=65536 /usr/sbin/no -o rfc1323=1 /usr/sbin/no -o sb_max=4194304 /usr/sbin/no -o ipqmaxlen=512 fi
By adding these lines to the /etc/rc.net file, the values persist when the system restarts.
You can also use the chdev command to change the characteristics of a device or interface. For example, set the RFC1323 value for the network interface en5 without restarting the system as follows:
chdev -l en5 -a rfc1323=1
If the system is not running in compatibility mode, then enter commands similar to the following to change the parameter values:
ipqmaxlen parameter:
/usr/sbin/no -r -o ipqmaxlen=512
Other parameter:
/usr/sbin/no -p -o parameter=value
Note:
If you modify theipqmaxlen parameter, then you must restart the system.These commands modify the /etc/tunables/nextboot file, causing the attribute values to persist when the system restarts.
If you need to change parameters, and you do not restart your system, then use the ifconfig command to check each network parameter after you change the no global setting.
For example:
# ifconfig en0
en0:
flags=1e080863,2c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,6
4BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN,MONITOR>
inet 192.0.2.1 netmask 0xfffff800 broadcast 192.0.2.0
inet 192.0.2.2 netmask 0xfffff800 broadcast 192.0.2.0
inet 192.0.2.3 netmask 0xfffff800 broadcast 192.0.2.0
inet 192.0.2.4 netmask 0xfffff800 broadcast 192.0.2.0
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
For the ISNO parameter tcp_sendspace, use the following command to set it:
# ifconfig en0 tcp_sendspace 65536
See Also:
The IBM documentation for more information about tuning AIX parameters for your system.Oracle Clusterware requires the same time zone setting on all cluster nodes. During installation, the installation process picks up the time zone setting of the Grid installation owner on the node where OUI runs, and uses that on all nodes as the default TZ setting for all processes managed by Oracle Clusterware. This default is used for databases, Oracle ASM, and any other managed processes.
You have two options for time synchronization: an operating system configured network time protocol (NTP), or Oracle Cluster Time Synchronization Service. Oracle Cluster Time Synchronization Service is designed for organizations whose cluster servers are unable to access NTP services. If you use NTP, then the Oracle Cluster Time Synchronization daemon (ctssd) starts up in observer mode. If you do not have NTP daemons, then ctssd starts up in active mode and synchronizes time among cluster members without contacting an external time server.
Note:
Before starting the installation of Oracle Grid Infrastructure, Oracle recommends that you ensure the clocks on all nodes are set to the same time.If you have NTP daemons on your server but you cannot configure them to synchronize time with a time server, and you want to use Cluster Time Synchronization Service to provide synchronization service in the cluster, then deactivate and deinstall the NTP.
To disable the NTP service, run the following command as the root user
# stopsrc -s xntpd
When the installer finds that the NTP protocol is not active, the Cluster Time Synchronization Service is installed in active mode and synchronizes the time across the nodes. If NTP is found configured, then the Cluster Time Synchronization Service is started in observer mode, and no active time synchronization is performed by Oracle Clusterware within the cluster.
To confirm that ctssd is active after installation, enter the following command as the Grid installation owner:
$ crsctl stat resource ora.ctssd -t -init
To install Oracle software, Secure Shell (SSH) connectivity should be set up between all cluster member nodes. OUI uses the ssh and scp commands during installation to run remote commands on and copy files to the other cluster nodes. You must configure SSH so that these commands do not prompt for a password.
Note:
SSH is used by Oracle configuration assistants for configuration operations from local to remote nodes. It is also used by Oracle Enterprise Manager.You can configure SSH from the Oracle Universal Installer (OUI) interface during installation for the user account running the installation. The automatic configuration creates passwordless SSH connectivity between all cluster member nodes. Oracle recommends that you use the automatic procedure if possible.
To enable the script to run, you must remove stty commands from the profiles of any Oracle software installation owners, and remove other security measures that are triggered during a login, and that generate messages to the terminal. These messages, mail checks, and other displays prevent Oracle software installation owners from using the SSH configuration script that is built into the Oracle Universal Installer. If they are not disabled, then SSH must be configured manually before an installation can be run.
See Also:
Section 5.2.5, "Preventing Installation Errors Caused by Terminal Output Commands" for information about how to remove stty commands in user profiles