Node1 and Node2
Production(orcl01 / orcl02) and Standby(orcldr01/orcldr02)
- Ensure the FRA is configured.
- Ensure the redo transport parameters for the primary and redo apply for the standby are configured:
- Ensure the standby redo log files are configured on the primary and standby database.
- Run the following query to pull information about the database on both Primary and standby
- Verifying That the Standby Has Received All Redo, you can carry your individual steps.
- Check the apply is caught up
- Verify there are no large Gaps
- Ensure Server Parameter File (SPFILE) is used on both Primary and standby database so that the broker can persistently reconcile values between broker properties and any related initialization parameter values:
- Verify value of the DG_BROKER_START initialization parameter is set to TRUE on both primary and standby DB.
- Verify DG_BROKER_CONFIG_FILEn initialization parameters files exists on shared disk for all databases in the Oracle RAC database configuration on Primary and standby:
- Check whether StaticConnectIdentifier is configured on ALL NODES
To enable DGMGRL to restart instances during the course of the switchover / conversion, a static service is required. This can be supplied by explicitly setting the Broker Instance Property StaticConnectIdentifier.
- Ensure Broker configuration is enabled and state of all members as intended is ONLINE
DGMRL> show database verbose orcl
- Verify remote_login_passwordfile is set to 'EXCLUSIVE' on both Primary and Standby:
- Converting a physical Standby to Snapshot Standby
- DGMGRL Convert to snapshot standby: Log onto dgmgrl from primary database server
- Convert back to Physical Standby
- Ensure Broker configuration is enabled and state of all members as intended is ONLINE:
Check the status of MRP
From this article we have learnt how to convert Physical standby database to Snapshot standby database using Data guard Broker method.