Database Reference
In-Depth Information
In this example, managed recovery aborted due to a problem. The database is
not
ready for any role transition,
as shown in the “Ready for Switchover” and “Ready for Failover” rows.
DGMGRL> validate database "STDB1"
Database Role: Physical standby database
Primary Database: CDB1
Ready for Switchover: No
Ready for Failover: No (Primary Running)
Standby Apply-Related Information:
Apply State: Not Running
Apply Lag: 505 days 18 hours 55 minutes 28 seconds
Apply Delay: 0 minutes
Current Log File Groups Configuration:
Thread # Online Redo Log Groups Standby Redo Log Groups
(CDB1) (STDB1)
1 3 2
Future Log File Groups Configuration:
Thread # Online Redo Log Groups Standby Redo Log Groups
(STDB1) (CDB1)
1 3 2
Automatic Diagnostic Repository Errors:
Error CDB1 STDB1
System data file missing NO YES
A crucial system data file is missing. Failing over at this stage would cause a lot of chaos.
Another example is shown here. The database is not ready for a switchover, because it is out of sync with the
primary. Remember that a switchover is a no-data-loss operation, and only when all redo has been applied on the
target standby will it switch over and reverse roles.
DGMGRL> validate database "STDB1"
Database Role: Physical standby database
Primary Database: CDB1
Warning: primary database was not reachable
Ready for Switchover: No
Ready for Failover: Yes (Primary Not Running)
Temporary Tablespace File Information:
CDB1 TEMP Files: Unknown
STDB1 TEMP Files: 3
Flashback Database Status:
CDB1: Unknown
STDB1: On
Search WWH ::
Custom Search