Re: How can I ensure a database service starts on the preferred node after a database restart?

Maybe you need to set up a FAN callout to relocate the service to the preferred nodes when they come online.

Link to documentation:
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/tdprc/managing-workloads-using-database-services.html#GUID-3D8A5870-E734-48CF-8DA7-338523BE69EE

On Wed, May 22, 2019 at 8:58 AM Redacted sender Jay.Miller for DMARC < dmarc-noreply_at_freelists.org> wrote:

> We have a number of database services which are only supposed to run on a
> single preferred node except in specific cases (down node, during patching,
> etc.). However when we use srvctl start database if that node doesn't come
> up first then the service will start up on the alternate node.
>
>
>
>
>
> We have three potential workarounds none of which are ideal so I was
> hoping someone had a better suggestion.
>
>
>
> 1. Simply restart the services after all the database instances are up.
> This is what we are doing now but it means that any apps which reconnect
> automatically will have connections to the alternate node.
>
>
>
> 2. Start the instances individually with the preferred node coming up
> first. This doesn't work for those databases which have multiple services
> each with a different preferred node. It also requires manual intervention
> to first check the preferred instance for each node.
>
>
>
> 3. Script the database startups to start the instances in the correct
> order. This still doesn't work for those databases which have multiple
> services as well as requiring a fair amount of work and education.
>
>
>
>
>
> Any ideas?
>
>
>
> Thanks,
>
> Jay
>
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l