Database Reference
In-Depth Information
Data file Online Move in Progress:
CDB1: Unknown
STDB1: No
Transport-Related Information:
Transport On: No
Gap Status: Unknown
Transport Lag: 1 hours 14 minutes 40 seconds
Transport Status: Success
Log Files Cleared:
CDB1 Standby Redo Log Files: Unknown
STDB1 Online Redo Log Files: Cleared
If you were desperate though you could initiate a failover operation at this point, but your data loss would be too
high at 1 hour 14 minutes 40 seconds. For most applications this is too much to be accepted. In such a situation you
need to double-check the monitoring to find out why the database could fall that far behind, and you should try and
salvage any redo logs from the primary you can get hold of and apply them to minimize the data loss.
If your primary was still running you could try enabling the archive destination and/or switch a log file. This is
normally enough to kick the log transport and apply mechanism back into gear after a transient failure.
Broker configuration can be renamed in place
Another nice feature is the ability to rename the configuration without having to drop it. If for example the name of
your configuration does not match the standards, or if the standards change, then you can implement the change of
name as shown in this example. Assume the configuration name is defined as “apress.”
DGMGRL> show configuration
Configuration - apress
Protection Mode: MaxPerformance
Databases:
CDB1 - Primary database
STDB1 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
Now change the configuration name to “DBAAS:”
DGMGRL> edit configuration rename to DBAAS;
Succeeded.
DGMGRL> show configuration
Search WWH ::
Custom Search