ORACLE 11G SNAPSHOT STANDBY实例(三)
ltered.
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> select database_role,db_unique_name,open_mode from v$database;
DATABASE_ROLE DB_UNIQUE_NAME OPEN_MODE
---------------- ------------------------------ --------------------
PHYSICAL STANDBY ogg READ ONLY WITH APPLY
查看LAG情况
此时日志传输 、日志应用LAG都为 0，备库已经重新与主库同步
SQL> select to_char(SYSDATE,'yyyymmdd hh24:mi:ss') CTIME,NAME,VALUE,DATUM_TIME
from V$DATAGUARD_STATS
WHERE NAME LIKE '%lag'; 2 3
CTIME NAME VALUE DATUM_TIME
----------------- ---------------- ------------------------------ ------------------------------
20131030 12:13:23 transport lag +00 00:00:00 10/30/2013 12:13:22
20131030 12:13:23 apply lag +00 00:00:00 10/30/2013 12:13:22
确认在SNAPSHOT STANDBY下面的操作都已回滚
SQL> select table_name,TABLESPACE_NAME from dba_tables where tablespace_name = 'TBS_XHL';
TABLE_NAME TABLESPACE_NAME
------------------------------ ------------------------------
XHL TBS_XHL
被删除的表已经恢复
SQL> select count(*) from xhl_snapstb.xhl;
select count(*) from xhl_snapstb.xhl
*
ERROR at line 1:
ORA-00942: table or view does not exist
新增表的操作已经撤销
1* SELECT USERNAME FROM DBA_USERS WHERE USERNAME= 'XHL_SNAPSTB'
SQL> /
no rows selected
新增用户已经撤销
总结：SNAPSHOT STANDBY 模式将备库置于可读写状态，可以在此备库上来回折腾 ，这个
结合REAL APPLICATION TESTING 做升级前测试非常方便。要注意如果在SNAPSHOT STANDBY
上面的数据更改操作过大，恢复回PHYSICAL STANDBY的时间会非常长。