Oracle11g‑uard physical standby Database Configuration series documents oracle11g‑uard physical standby database configuration (1) Create oracle11g‑uard physical standby database configuration (2) active‑uar ..
Oracle11g‑uard physical standby Database Configuration series documents oracle11g‑uard physical standby database configuration (1) Create oracle11g‑uard physical standby database configuration (2) active‑uar ..
Oracle 11g slave uard physical standby Database Configuration documents
Oracle 11g slave uard physical standby database configuration (5) broker switchover Test
Oracle 11g slave uard physical standby database configuration (6) broker fastfailover Test
Oracle 11g replicuard configuration learning Summary
This article uses Oracle 11g middleware uard broker fastfailover for testing
Oracle 11g elastic uard fast failover configuration, Hong Kong Server rental, You need to enable the flash back function for the master and slave databases, the flash back function to enable this article skipped.
When flash back is enabled and needs to be started to the mount status, do not disable the monitoring of the master and slave databases.
1. Check the status of the Master/Slave database in dgmgrl
$ Dgmgrl sys/oracle
DGMGRL for Linux: Version 11.2.0.3.0-64bit Production
Copyright (c) 2000,200 9, Oracle. All rights reserved.
Welcome to DGMGRL. For more information, enter "help ".
Connected.
DGMGRL> show configuration;
Configuration-dgorcldb
Protection Mode: MaxPerformance
Database:
Orcl-primary database
Slave-physical backup database
Fast Start failover: DISABLED
Configuration status:
SUCCESS
# Quick Start failover is unavailable.
# Check the Failover status. The VM and DISABLED are not enabled.
DGMGRL> show fast_start failover
Fast Start failover: DISABLED
Threshold: 30 seconds
Objective: (none)
Observation program: (none)
Latency limit: 30 seconds
Disable the primary database: TRUE
Automatic Recovery: TRUE
Configurable failover Conditions
Health status:
Corrupted Controlfile YES
Specified upted Dictionary YES
Inaccessible Logfile NO
Stuck Archiver NO
Datafile Offline YES
Oracle error conditions:
(None)
2. Start Quick Start failover
DGMGRL> enable fast_start failover;
3. Start the fast start of the Failover observer observation program
DGMGRL> start observer;
Note: After you start the observer, the program will not run in the background and will be displayed on the foreground.
In actual use, it must be started independently on the server. It runs automatically on the background and cannot be closed. Otherwise, the master and slave databases cannot automatically monitor the running status.
You cannot use the Quick Start failover function.
4. Run the following command in another window:
$ Dgmgrl sys/oracle
DGMGRL> show fast_start failover;
Quick Start failover: ENABLED
Threshold: 30 seconds
Target: slave
Observation program: master
Latency limit: 45 seconds
Disable the primary database: TRUE
Automatic Recovery: TRUE
Configurable failover Conditions
Health status:
Corrupted Controlfile YES
Specified upted Dictionary YES
Inaccessible Logfile NO
Stuck Archiver NO
Datafile Offline YES
Oracle error conditions:
(None)
DGMGRL> show configuration
Configuration-dgorcldb
Protection Mode: MaxPerformance
Database:
Slave-master database
Orcl-(*) Physical standby Database
Quick Start failover: ENABLED
Configuration status:
SUCCESS
Now the fast_start failover configured for dgmgrl has been configured. The failover process is simulated below.
We can use shutdown abort to simulate unexpected database crashes in Hong Kong Space,
NOTE 1: The master database shutdown immediate does not start the fast start failover function.
NOTE 2: oracle 11g slave uard fast start failover switchover does not require the master and slave databases to run in the maximum available mode.
5. Unexpected crash of the master database during simulated testing
1) on the master database:
$ Sqlplus/as sysdba;
SQL> shutdown abort;
The observer displays logs: displays the active/standby switchover process.