physical DB Real Time Apply（RTA实时应用）

PS：这些DG实现都是建立在我之前DG博客的基础上的

此时备库是mount状态

1. 19:53:38 SYS @ gotime >select status from v$instance;
   
2. 
   
3. STATUS
   
4. ------------
   
5. MOUNTED
   
6. 
   
7. 1 row selected.
   
8. 
   
9. Elapsed: 00:00:00.01

备库打开至open，然后设置成RTA模式

1. 20:10:00 SYS @ gotime >alter database open;
   
2. 
   
3. Database altered.
   
4. 
   
5. Elapsed: 00:00:00.33
   
6. 20:10:09 SYS @ gotime >select status from v$instance;
   
7. 
   
8. STATUS
   
9. ------------
   
10. OPEN
    
11. 
    
12. 1 row selected.
    
13. 
    
14. Elapsed: 00:00:00.01
    
15. 20:10:23 SYS @ gotime >select name,open_mode,database_role,protection_mode from v$database;
    
16. 
    
17. NAME     OPEN_MODE     DATABASE_ROLE    PROTECTION_MODE
    
18. --------- -------------------- ---------------- --------------------
    
19. SLOW     READ ONLY     PHYSICAL STANDBY MAXIMUM AVAILABILITY
    
20. 
    
21. 1 row selected.
    
22. 
    
23. Elapsed: 00:00:00.01
    
24. 20:11:02 SYS @ gotime >recover managed standby database using current logfile disconnect;
    
25. Media recovery complete.

此时备库的告警日志信息 

1. Serial Media Recovery started
   
2. Managed Standby Recovery starting Real Time Apply
   
3. Waiting for all non-current ORLs to be archived...
   
4. All non-current ORLs have been archived.
   
5. Media Recovery Waiting for thread 1 sequence 35 (in transit)
   
6. Recovery of Online Redo Log: Thread 1 Group 4 Seq 35 Reading mem 0
   
7.   Mem# 0: /u01/app/oracle/oradata/gotime/standby04.log
   
8. Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect

主库上开始一些DML操作并提交，测试是否成功，备库能否能够在提交瞬间作出反应，立即同步呢？？

1. 20:13:05 SYS @ slow >select * from t2017;
   
2. 
   
3.     DEPTNO DNAME     LOC
   
4. ---------- -------------- -------------
   
5.     10 ACCOUNTING     NEW YORK
   
6.     20 RESEARCH     DALLAS
   
7.     30 SALES     CHICAGO
   
8.     40 OPERATIONS     BOSTON
   
9.     10 ACCOUNTING     NEW YORK
   
10.     20 RESEARCH     DALLAS
    
11.     30 SALES     CHICAGO
    
12.     40 OPERATIONS     BOSTON
    
13. 
    
14. 8 rows selected.
    
15. 
    
16. Elapsed: 00:00:00.00
    
17. 20:13:21 SYS @ slow >create table t2018 as select * from t2017 where deptno < 30;
    
18. 
    
19. Table created.
    
20. 
    
21. Elapsed: 00:00:00.03
    
22. 20:14:58 SYS @ slow >commit;
    
23. 
    
24. Commit complete.
    
25. 
    
26. Elapsed: 00:00:00.00
    
27. 20:15:02 SYS @ slow >

答案是确定的，说明成功了，备库能对主库commit的DML操作立即同步，做出反应！！！

1. 20:14:16 SYS @ gotime >select * from t2017;
   
2. 
   
3.     DEPTNO DNAME     LOC
   
4. ---------- -------------- -------------
   
5.     10 ACCOUNTING     NEW YORK
   
6.     20 RESEARCH     DALLAS
   
7.     30 SALES     CHICAGO
   
8.     40 OPERATIONS     BOSTON
   
9.     10 ACCOUNTING     NEW YORK
   
10.     20 RESEARCH     DALLAS
    
11.     30 SALES     CHICAGO
    
12.     40 OPERATIONS     BOSTON
    
13. 
    
14. 8 rows selected.
    
15. 
    
16. Elapsed: 00:00:00.10
    
17. 20:15:17 SYS @ gotime >select * from t2018;
    
18. 
    
19.     DEPTNO DNAME     LOC
    
20. ---------- -------------- -------------
    
21.     10 ACCOUNTING     NEW YORK
    
22.     20 RESEARCH     DALLAS
    
23.     10 ACCOUNTING     NEW YORK
    
24.     20 RESEARCH     DALLAS
    
25. 
    
26. 4 rows selected.
    
27. 
    
28. Elapsed: 00:00:00.00
    
29. 20:15:36 SYS @ gotime >

-----------------------------------备库重新启动之后，Real Time Apply 消失 -------------------------------------------------------

将备库由Real Time Apply 状态重新启动，然后打开至open，进行测试

1. 20:15:36 SYS @ gotime >startup mount force
   
2. ORACLE instance started.
   
3. 
   
4. Total System Global Area 521936896 bytes
   
5. Fixed Size         2254824 bytes
   
6. Variable Size         377489432 bytes
   
7. Database Buffers     138412032 bytes
   
8. Redo Buffers         3780608 bytes
   
9. Database mounted.
   
10. 20:24:30 SYS @ gotime >recover managed standby database cancel;
    
11. ORA-16136: Managed Standby Recovery not active
    
12. 
    
13. 
    
14. 20:25:05 SYS @ gotime >alter database open;
    
15. 
    
16. ^Calter database open
    
17. *
    
18. ERROR at line 1:
    
19. ORA-10458: standby database requires recovery
    
20. ORA-01196: file 1 is inconsistent due to a failed media recovery session
    
21. ORA-01110: data file 1: '/u01/app/oracle/oradata/gotime/system01.dbf'
    
22. 
    
23. 
    
24. Elapsed: 00:00:24.23
    
25. 
    
26. 20:27:42 SYS @ gotime >recover managed standby database disconnect;
    
27. Media recovery complete.
    
28. 20:28:50 SYS @ gotime >recover managed standby database cancel;
    
29. Media recovery complete.
    
30. 20:30:05 SYS @ gotime >alter database open;
    
31. 
    
32. Database altered.
    
33. 
    
34. Elapsed: 00:00:00.28

主库创建DML操作，进行测试，是否备库重新启动之后，Real Time Apply 消失....

1. 20:31:13 SYS @ slow >create table t2000 as select * from t2017 where deptno < 20;
   
2. 
   
3. Table created.
   
4. 
   
5. Elapsed: 00:00:00.06
   
6. 20:31:29 SYS @ slow >commit;
   
7. 
   
8. Commit complete.
   
9. 
   
10. Elapsed: 00:00:00.00
    
11. 20:31:32 SYS @ slow >select * from t2000;
    
12. 
    
13.     DEPTNO DNAME     LOC
    
14. ---------- -------------- -------------
    
15.     10 ACCOUNTING     NEW YORK
    
16.     10 ACCOUNTING     NEW YORK
    
17. 
    
18. 2 rows selected.
    
19. 
    
20. Elapsed: 00:00:00.00
    
21. 20:33:42 SYS @ slow >

此时备库的状态是open的，read only的，但是无法查询主库提交DML的数据，Real Time Appy 消失！！！

1. 20:30:38 SYS @ gotime >select * from t2000;
   
2. select * from t2000
   
3.               *
   
4. ERROR at line 1:
   
5. ORA-00942: table or view does not exist
   
6. 
   
7. 
   
8. Elapsed: 00:00:00.00
   
9. 20:31:39 SYS @ gotime >
   
10. 20:33:44 SYS @ gotime >r
    
11.   1* select * from t2000
    
12. select * from t2000
    
13.               *
    
14. ERROR at line 1:
    
15. ORA-00942: table or view does not exist
    
16. 
    
17. 
    
18. Elapsed: 00:00:00.00
    
19. 20:33:46 SYS @ gotime >

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/31405474/viewspace-2150117/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/31405474/viewspace-2150117/