Oracle 18c-Performing a Reinstate Failed Primary Database Using DBCS Console

Oracle 18c-Performing a Reinstate Failed Primary Database Using DBCS Console

Description:-

  • In this article we are going to see reinstate a failed primary database as a standby database after a failover.
  • After performing a failover to the standby database, you may be able to restore your original disaster-recovery solution by reinstating the failed primary database from 11.2.0.3 onwords.
  • After the failover Terabytes,warehouses or datamarts databases,Recreating the old Production as a Standby using RMAN duplicate it takes couple of days

Check the below related posts

Oracle 18c-Configure Data Guard On Oracle Cloud Service Here
Oracle 18c-Performing a Data Guard Switchover using DBCS Console Here
Oracle 18c-Performing a Data Guard Failover using DBCS Console Here
Oracle 18c-Performing a Data Guard Switchover using dbaascli Utility Here
Oracle 18c-Performing a Data Guard Failover Using DBaascli Utility Here

Let’s Start the Demo Using DBCS Console:-

Step1:-Check the status using DBCS Console

Step2:-Check Staus using Dbaascli Command

[oracle@chennai-dg01 ~]$ dbaascli dataguard status
DBAAS CLI version 1.0.0
Executing command dataguard status
SUCCESS : Dataguard is up and running
DETAILS:
Connected to “chennai_02”
Connected as SYSDBA.
Configuration – fsc
Protection Mode: MaxPerformance
Members:
chennai_02 – Primary database
chennai_01 – Physical standby database (disabled)
ORA-16661: the standby database needs to be reinstated
Properties:
FastStartFailoverThreshold = ’30’
OperationTimeout = ‘120’
TraceLevel = ‘USER’
FastStartFailoverLagLimit = ’30’
CommunicationTimeout = ‘180’
ObserverReconnect = ‘0’
FastStartFailoverAutoReinstate = ‘TRUE’
FastStartFailoverPmyShutdown = ‘TRUE’
BystandersFollowRoleChange = ‘ALL’
ObserverOverride = ‘FALSE’
ExternalDestination1 = ”
ExternalDestination2 = ”
PrimaryLostWriteAction = ‘CONTINUE’
ConfigurationWideServiceName = ‘chennai_CFG’
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Step3:-Check the Dataguard configuration status

dbaascli dataguard status –details yes

Step4:-Start the Reinstate using DBCS Console

Step5:-From the menu we need select the Reinstate button, and then confirm the action.

Step6:-Check Status using Dbaascli Command

[oracle@chennai-dg01 chennai]$ dbaascli dataguard status
DBAAS CLI version 1.0.0
Executing command dataguard status
SUCCESS : Dataguard is up and running
DETAILS:
Connected to “chennai_01″
Connected as SYSDBA.
Configuration – fsc
Protection Mode: MaxPerformance
Members:
chennai_02 – Primary database
chennai_01 – Physical standby database
Properties:
FastStartFailoverThreshold = ’30’
OperationTimeout = ‘120’
TraceLevel = ‘USER’
FastStartFailoverLagLimit = ’30’
CommunicationTimeout = ‘180’
ObserverReconnect = ‘0’
FastStartFailoverAutoReinstate = ‘TRUE’
FastStartFailoverPmyShutdown = ‘TRUE’
BystandersFollowRoleChange = ‘ALL’
ObserverOverride = ‘FALSE’
ExternalDestination1 = ”
ExternalDestination2 = ”
PrimaryLostWriteAction = ‘CONTINUE’
ConfigurationWideServiceName = ‘chennai_CFG’
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Step7:-Check Status using DBCS Console

Reference:-

https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/data-guard-reinstate-failed-primary.html

Catch Me On:- Hariprasath Rajaram

LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page: https://www.facebook.com/dbahariprasath/?
Twitter:  https://twitter.com/hariprasathdba

Oracle 18c-Performing a Reinstate Failed Primary Database Using DBaascli Utility

Oracle 18c-Performing a Reinstate Failed Primary Database Using DBaascli Utility

Description:-

  • In this article we are going to see reinstate a failed primary database as a standby database after a failover.
  • After performing a failover to the standby database, you may be able to restore your original disaster-recovery solution by reinstating the failed primary database from 11.2.0.3 onwords.
  • After the failover Terabytes,warehouses or datamarts database,Recreating the old Production as a Standby using RMAN duplicate it takes couple of days

Check the below related posts

Oracle 18c-Configure Data Guard On Oracle Cloud Service Here
Oracle 18c-Performing a Data Guard Switchover using DBCS Console Here
Oracle 18c-Performing a Data Guard Failover using DBCS Console Here
Oracle 18c-Performing a Data Guard Switchover using dbaascli Utility Here
Oracle 18c-Performing a Data Guard Failover Using DBaascli Utility Here

Let’s Start the Demo Using DBaascli Utility:-

Step1:-Check the status using DBCS Console

Step2:-Check Staus using Dbaascli Command

[oracle@chennai-dg01 ~]$ dbaascli dataguard status
DBAAS CLI version 1.0.0
Executing command dataguard status
SUCCESS : Dataguard is up and running
DETAILS:
Connected to “chennai_02”
Connected as SYSDBA.
Configuration – fsc
Protection Mode: MaxPerformance
Members:
chennai_02 – Primary database
chennai_01 – Physical standby database (disabled)
ORA-16661: the standby database needs to be reinstated
Properties:
FastStartFailoverThreshold = ’30’
OperationTimeout = ‘120’
TraceLevel = ‘USER’
FastStartFailoverLagLimit = ’30’
CommunicationTimeout = ‘180’
ObserverReconnect = ‘0’
FastStartFailoverAutoReinstate = ‘TRUE’
FastStartFailoverPmyShutdown = ‘TRUE’
BystandersFollowRoleChange = ‘ALL’
ObserverOverride = ‘FALSE’
ExternalDestination1 = ”
ExternalDestination2 = ”
PrimaryLostWriteAction = ‘CONTINUE’
ConfigurationWideServiceName = ‘chennai_CFG’
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Step3:-Check the Dataguard configuration status

dbaascli dataguard status –details yes

Step4:-Start the Reinstate using dbaascli Command

dbaascli dataguard reinstate

Step5:-Check Status using Dbaascli Command

[oracle@chennai-dg01 chennai]$ dbaascli dataguard status
DBAAS CLI version 1.0.0
Executing command dataguard status
SUCCESS : Dataguard is up and running
DETAILS:
Connected to “chennai_01″
Connected as SYSDBA.
Configuration – fsc
Protection Mode: MaxPerformance
Members:
chennai_02 – Primary database
chennai_01 – Physical standby database
Properties:
FastStartFailoverThreshold = ’30’
OperationTimeout = ‘120’
TraceLevel = ‘USER’
FastStartFailoverLagLimit = ’30’
CommunicationTimeout = ‘180’
ObserverReconnect = ‘0’
FastStartFailoverAutoReinstate = ‘TRUE’
FastStartFailoverPmyShutdown = ‘TRUE’
BystandersFollowRoleChange = ‘ALL’
ObserverOverride = ‘FALSE’
ExternalDestination1 = ”
ExternalDestination2 = ”
PrimaryLostWriteAction = ‘CONTINUE’
ConfigurationWideServiceName = ‘chennai_CFG’
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Step6:-Check Status using DBCS Console

 

Catch Me On:- Hariprasath Rajaram

LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page: https://www.facebook.com/dbahariprasath/?
Twitter:  https://twitter.com/hariprasathdba