Re: RAC fail-over with an instance in MOUNT status

Hi Jerome,

also with a single instance you can work with services (service_names parameter). You can check the listener which services are known for a single instance database (lsnrctl serv <listenername>). You will notice that the service 'db_name.db_domain' is always registered with the listener. So this is default behaviour of oracle instances and not specific for RAC.
In clusterware you can define RAC services with some options (eg: preffered/available/not used and the TAF policy). This is actually a combination of the standard service_names parameter for the oracle instance and configurations in the cluster registry (OCR).

regards,
Tony van Esch

vitalis..._at_gmail.com schreef:
.
>
> Thanks a lot, Tony. I guess this is the solution. The cluster database
> was created with DBCA when only one node was up. And DBCA did not
> create any basic cluster service. Could you please confirm it creates
> a cluster service when more than one instance are configured at the
> time of the database creation?
>
> According to the doco : "DBCA creates a default service for your
> Oracle RAC database and this service is a special Oracle database
> service". Another reading would be that it creates the "standard"
> database service I see on this cluster. But that would mean that even
> with more than 1 node at database creation, the MOUNT problem can
> happen unless we configure a cluster service additionally.
Received on Tue Aug 07 2007 - 10:32:20 CDT