Owner's Manual
52 Deployment Guide
Performance
and stability
Unknown interface
type warning
appears in Oracle
alert file.
Poor system
performance.
The public interface
is configured as
cluster
communications
(private interface).
Force cluster communications to the private interface
by performing the following steps
on
one node
:
1
Log in as
oracle
.
2
Ty p e
sqlplus "/ as sysdba"
at the command
prompt.
The
SQL>
prompt appears.
3
Enter the following lines at the
SQL>
prompt:
alter system set cluster_interconnects=<
private IP
address node1
>’ scope=spfile sid=’<
SID1
>’
alter system set cluster_interconnects=’<
private
IP address node2
>’ scope=spfile sid=’<
SID2
>’
Continue entering lines for each node in the cluster.
4
Restart the database on all nodes by typing the
following lines:
srvctl stop database –d <dbname>
srvctl start database –d <dbname>
5
Open the
/opt/oracle/admin/<
dbname
>/bdump/alert_<
SID
>.log
file and verify that the private IP addresses are being
used for all instances.
NETCA NETCA fails,
resulting in
database creation
errors.
The public network,
hostname, or virtual
IP is not listed in the
/etc/hosts.equiv file.
Before launching netca, ensure that a hostname is
assigned to the public network and that the public and
virtual IP addresses are listed in the /etc/hosts.equiv file.
NETCA NETCA cannot
configure remote
nodes or a RAW
device validation
error occurs while
running DBCA.
The /etc/hosts.equiv
file either does not
exist or does not
include the assigned
public or virtual IP
addresses.
Verify that the /etc/hosts.equiv file on each node
contains the correct public and virtual IP address. Try to
rsh to other public names and VIP addresses as oracle
user.
CRS CRS gives up
prematurely when
trying to start.
Due to Oracle bug
4698419. See the
Oracle Metalink
website at
metalink.oracle.com.
Apply patch 4698419 available on the Oracle Metalink
website at metalink.oracle.com.
CRS The Clusterware
installation
procedure fails.
EMC PowerPath
device names are not
uniform across the
nodes.
Before you install the Clusterware, restart PowerPath
and ensure that the PowerPath device names are
uniform across the nodes.
Table 1-9. Troubleshooting (continued)
Category Problem / Symptom Cause Recommended Corrective Action