How to start the service on DR if it does not Auto start After reboot the server
Check the running services as
srvctl status service -d ABC_WDC
Service ABC_APP is running on instance(s) ABC2,ABC3
Service ABC_BATCH is running on instance(s) ABC2,ABC3
Service ABC_BKP is running on instance(s) ABC2,ABC3
Service ABC_INTR is running on instance(s) ABC2,ABC3
Service ABC_USER is running on instance(s) ABC2,ABC3
Check for the backup service since issue is with the backup did not auto triggered after reboot
> srvctl config service -d ABC_WDC -s ABC_BKP
Service name: ABC_BKP
Service is enabled
Server pool: ABC_WDC_ABC_BKP
Cardinality: 3
Disconnect: false
Service role: PRIMARY (This should not be primary this shuld be physical standby)
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Failover type: SESSION
Failover method: NONE
TAF failover retries: 0
TAF failover delay: 0
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: BASIC
Edition:
Preferred instances: ABC1,ABC2,ABC3
Available instances:
MWLDADM@twdrracancl01 - ABC1 - Linux - /home/oracle <<< DR >>>
> srvctl modify service -d ABC_WDC -s ABC_BKP -l PHYSICAL_STANDBY
MWLDADM@twdrracancl01 - ABC1 - Linux - /home/oracle <<< DR >>>
Now change the role from primary to physical standby with below command -
> srvctl config service -d ABC_WDC -s ABC_BKP
Service name: ABC_BKP
Service is enabled
Server pool: ABC_WDC_ABC_BKP
Cardinality: 3
Disconnect: false
Service role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Failover type: SESSION
Failover method: NONE
TAF failover retries: 0
TAF failover delay: 0
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: BASIC
Edition:
Preferred instances: ABC1,ABC2,ABC3
Available instances:
MWLDADM@twdrracancl01 - ABC1 - Linux - /home/oracle <<< DR >>>
>
No comments:
Post a Comment