After converting your physical standby database to a logical database, you get an error:
DGMGRL> show configuration
Configuration- proddg
Protection Mode: MaxPerformance
Databases:
prod-Primary datatabse
prodsby-Physical standby database
Error: ORA-16810 multiple errors or warnings detected for database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
How can you rectify the error?
A.
Add a logical standby database PRODSBY and enable it, thereby replacing the physical standby database
metadata in the broker configuration.
B.
Remove the physical standby database PRODSBY from the broker configuration, add a logical standby
database PRODSBY to the broker configuration and enable it.
C.
Reinstate the physical standby database PRODSBY as a logical standby, thereby replacing the physical
standby database metadata in the broker configuration.
D.
Reinstate both the primary and physical standby databases. The broker will automatically detect thatPRODSBY is a logical standby update to the metadata.
Explanation:
You can reenable the standby database or reset the primary database state to ONLINE to fix the
inconsistencies.
https://docs.oracle.com/cd/B19306_01/server.102/b14230/cli.htm
Correct Ans: B
You can only convert physical standby to snapshot standby or snapshot to physical using DGMGRL.
Converting physical to logical has to be done outside the broker using SQL statements. When such a change happened outside of Broker it cannot reinstate the database so only way to fix such situation is:
1. REMOVE DATABASE ‘PRODSBY’; <– Remove old physical standby from broker
2. ADD DATABASE 'PRODSBY' AS CONNECT IDENTIFIER IS PRODSBY; <– Broker recognizes it as logical standby
3. ENABLE DATABASE 'PRDSBY'; <– Enable new logical standby database
B