Database - RAC/Scalability (MOSC)

MOSC Banner

services started incorrectly on PHYSICAL_STANDBY, why ?

Hi,

I have primary RAC and standby RAC, databases are sboxcdbP and sboxcdbS, container databases are named SBOX

I used srvctl to configure services on both primary and standby rac:

Primary:

srvctl add service -db sboxcdbp -pdb sbox -service TEST -preferred sboxcdb1 -available sboxcdb2 -role PRIMARY -failback YES -drain_timeout 60

Standby:

srvctl add service -db sboxcdbs -pdb sbox -service TEST -preferred sboxcdb1 -available sboxcdb2 -role PRIMARY -failback YES -drain_timeout 60

(only database is different)

When I was configuring services about a year ago, I was running Oracle version 19.8

I did multiple tests for switching services, rebooting nodes etc. - everything worked as expected - service with above configuration was started only on PRIMARY.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center