Some advanced management case studies of ORACLE11GDataGuard
After setting up ORACLE 11G dataguard, I also conducted a Role Switching experiment. switchover has failover, and I feel a lot of benefits. Then I continue to study some of the advanced management functions of dataguard, ORACLE is profound and profound at the tip of the iceberg. The summary record is as follows:
1. Advanced Management of ORACLE 11G elastic uard
1.1 enable physical STANDBY in read only/WRITE mode
There are two cases:
1) if the standby database is in the shutdown state, you can directly start up and directly open it to the open state. Make sure that the database status is as follows:
SQL> select open_mode, database_role from v $ database;
2) The standby database is in the redo application state.
1.2. If you want to switch from the open state to the redo application state, you do not need to shut down the application and enable the redo application directly. For example:
SQL> select status from v $ instance;
2. affects the standby primary database event
Alter database enable | disable thread statement; (this statement is mainly used in the rac environment and is currently basically obsolete, because the ENABLE | disable instance clause can fully implement similar functions)
2.1. Modify and delete data files or tablespaces on primary.
3. Set standby_file_management to auto to add and delete tablespaces and data files.
Check the value of standby_file on the standby database first.
3.1 Add a tablespace for testing
3.2 Delete table space test
4. Set STANDBY_FILE_MANAGEMENT to MANUAL to add and delete tablespaces and data files.
4.1. New tablespace is added.
4.3 Delete table space test
5. Rename the data file
The name has been switched over. OK.
6. add or delete Online redo logs
The operation process is very simple (it will never be complicated to add or delete data files). Note that you must set STANDBY_FILE_MANAGEMENT to MANUAL before standby does the operation.