RE: Oracle/RAC installation problem
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <spikey.mcmarbles@xxxxxxxxx>, "'ORACLE-L'" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 29 Jan 2009 18:45:06 -0500
cluvfy should tell you what is wrong.
If that comes up clean, check that the crs and voting disks are accessible
from all nodes.
Which listener is being used?
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Greg Norris
Sent: Thursday, January 29, 2009 2:56 PM
To: ORACLE-L
Subject: Oracle/RAC installation problem
My advance apologies for the vagueness, but the DBA team doesn't handle
Oracle software installations in our shop, so I haven't actually seen the
specific error messages (and apparently no logfiles were produced).
I'll start by describing the environment. We have a 4-node Sun cluster,
which is currently running an all-Oracle stack (no 3rd-party clusterware).
* CRS: 11.1.0.7 (upgraded several months ago from 10.2.0.3)
* ASM: 10.2.0.3 (11.1.0.7 was installed a few weeks ago, but that
upgrade has not yet occurred)
* DBMS: 10.2.0.3
All components were installed into separate ORACLE_HOMEs.
Now we're trying to install Oracle 10.2.0.4 for DBMS use (once ASM is
upgraded), and only 2 out of the 4 nodes are recognized as valid
candidates... apparently the others are listed, but can't be selected. I'm
told that both the 10gR2 and 11gR1 versions of the installer were tried, and
that each exhibited this behavior. No such issues were encountered when
installing 11.1.0.7 for ASM recently, however.
Does this sound familiar to anyone? Suggestions on were and/or how to begin
troubleshooting this sort of issue would be most welcome.
Thanx!
--
Boldly going forward, because we simply can't find reverse...
Other related posts:
