Oracle Database Oracle Clusterware Installation Guide for HP-UX

Verifying Oracle Clusterware Requirements with CVU
If ssh is in a location other than the default, /usr/bin, then Cluster Verification
Utility reports a user equivalence check failure. To avoid this error, navigate to the
directory $CV_HOME/cv/admin, open the file cvu_config with a text editor,
and add or update the key ORACLE_SRVM_REMOTESHELL to indicate the ssh path
location on your system. For example:
# Locations for ssh and scp commands
ORACLE_SRVM_REMOTESHELL=/usr/local/bin/ssh
ORACLE_SRVM_REMOTECOPY=/usr/local/bin/scp
Note the following rules for modifying the cvu_config file:
■ Key entries have the syntax name=value
■ Each key entry and the value assigned to the key defines one property only
■ Lines beginning with the number sign (#) are comment lines, and are ignored
■ Lines that do not follow the syntax name=value are ignored
When you have changed the path configuration, run Cluster Verification Utility
again. If ssh is in another location than the default, then you also need to start OUI
with additional arguments to specify a different location for the remote shell and
remote copy commands. Enter runInstaller -help to obtain information
about how to use these arguments.
Note: When you or OUI run ssh or rsh commands, including any
login or other shell scripts they start, you may see errors about invalid
arguments or standard input if the scripts generate any output. You
should correct the cause of these errors.
To stop the errors, remove all commands from the oracle user's login
scripts that generate output when you run ssh or rsh commands.
If you see messages about X11 forwarding, then complete the task
"Setting Display and X11 Forwarding Configuration" on page 2-25 to
resolve this issue.
If you see errors similar to the following:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
These errors are produced if hidden files on the system (for example,
.cshrc) contain stty commands. If you see these errors, then refer
to Chapter 2, "Preventing Oracle Clusterware Installation Errors
Caused by stty Commands" on page 2-26 to correct the cause of these
errors.
Node Reachability Check or Node Connectivity Check Failed
Cause: One or more nodes in the cluster cannot be reached using TCP/IP
protocol, through either the public or private interconnects.
Action: Use the command /usr/sbin/ping address to check each node
address. When you find an address that cannot be reached, check your list of
public and private addresses to make sure that you have them correctly
configured. If you use vendor clusterware, then refer to the vendor documentation
for assistance. Ensure that the public and private network interfaces have the same
interface names on each node of your cluster.
Installing Oracle Clusterware 6-3