前提:

主庫執行:

1. 放在Oracle內部schema下的使用者表將不會被複制到備庫,並且DBA_LOGSTDBY_UNSUPPORTED這裡也查詢不到

--查詢Oracle內部的schema
SELECT OWNER FROM DBA_LOGSTDBY_SKIP WHERE STATEMENT_OPT = 'INTERNAL SCHEMA';

2. 

--查詢SQL Apply不支援的表
SELECT DISTINCT OWNER,TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED ORDER BY OWNER,TABLE_NAME;

3.  為了確保SQL Apply能有效應用update的redo資料到備庫,建議主庫的表都有主鍵或非空唯一索引

--查詢沒有唯一邏輯識別符號的表
SELECT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_NOT_UNIQUE
   WHERE (OWNER, TABLE_NAME) NOT IN 
   (SELECT DISTINCT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED) 
   AND BAD_COLUMN = 'Y';
如果上面的語句非常慢,建議直接執行:
SELECT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_NOT_UNIQUE
   WHERE  BAD_COLUMN = 'Y';

步驟:

一 、 首先建立好物理備庫

二、原物理備庫上停止日誌應用

SQL>  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

三、主庫上設定支援邏輯備庫的操作

1.  更改LOG_ARCHIVE_DEST_1,只歸檔線上日誌,而不歸檔standby redo

SQL> alter system set LOG_ARCHIVE_DEST_1='LOCATION=/bak2/archivelog/
  VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
  DB_UNIQUE_NAME=r5'  scope=both;

2.  設定LOG_ARCHIVE_DEST_3,此引數僅當主庫轉換為邏輯備庫角色時使用

SQL> alter system set LOG_ARCHIVE_DEST_3='LOCATION=/bak2/arch2/
  VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE)
  DB_UNIQUE_NAME=r5'    scope=both;

SQL> alter system set LOG_ARCHIVE_DEST_STATE_3=ENABLE scope=both;

注: 不能共用/bak2/archivelog/這個歸檔日誌目錄,應新建一個目錄,否則會報錯:

ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16033: parameter LOG_ARCHIVE_DEST_3 destination cannot be the same as
parameter LOG_ARCHIVE_DEST_1 destination

3.  在Redo資料中建立LogMiner字典

注: 此命令會等主庫所有當前的事務完成後才執行

四、 備庫上執行操作,以將物理備庫轉為邏輯備庫

SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY r5standby;

注: 如果執行此命令報ORA-19953: database should not be open, 那麼需要先shutdown,然後startup mount,

如果執行此命令卡住,則可執行ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL來取消

SQL> SHUTDOWN;
SQL> STARTUP MOUNT;

SQL> alter system set log_archive_config='dg_config=(r5,r5standby)';

SQL>ALTER SYSTEM SET  LOG_ARCHIVE_DEST_1=
  'LOCATION=+DATA/R5STANDBY/ARC1
   VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
   DB_UNIQUE_NAME=r5standby' scope=both;
SQL>ALTER SYSTEM SET  LOG_ARCHIVE_DEST_2=
  'SERVICE=r5 ASYNC
   VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
   DB_UNIQUE_NAME=r5' scope=both;
SQL> alter diskgroup DATA add directory '+DATA/R5STANDBY/ARC2';   
SQL>ALTER SYSTEM SET  LOG_ARCHIVE_DEST_3=
  'LOCATION=+DATA/R5STANDBY/ARC2
   VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE)
   DB_UNIQUE_NAME=r5standby' scope=both;
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE scope=both;
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE scope=both;
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3=ENABLE scope=both;

SQL> ALTER DATABASE OPEN RESETLOGS;


SQL>  ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

五、驗證

備庫上查詢:

SQL> select protection_mode,database_role,protection_level,open_mode from v$database; 


PROTECTION_MODE      DATABASE_ROLE    PROTECTION_LEVEL  OPEN_MODE
-------------------- ---------------- -------------------- --------------------
MAXIMUM PERFORMANCE  LOGICAL STANDBY  MAXIMUM PERFORMANCE  READ WRITE

SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
SESSION_ID    STATE
----------    -------------
1             INITIALIZING

SQL> select open_mode from v$database;


OPEN_MODE
--------------------
READ WRITE

注: 狀態為INITIALIZING時,備庫正在初始化,此時,你在主庫的DML操作等,是還不會應用到備庫來的,alter日誌如下:

Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 0
Starting background process SMCO
Tue Jan 10 10:21:13 2017
SMCO started with pid=21, OS id=2803
[[email protected] trace]$ tail -100 alert_r5standby.log
Indexes of table  SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ENC$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_KOPM$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_NTAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OPQTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PARTOBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PROPS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_REFCON$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SEED$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SUBCOLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
Tue Jan 10 10:22:59 2017
LOGMINER: End mining logfiles during dictionary load for session 1
Tue Jan 10 10:22:59 2017
LSP2 started with pid=56, OS id=2859
Tue Jan 10 10:23:00 2017
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 1064, +DATA/r5standby/arc2/1_1064_865010252.dbf
LOGMINER: End   mining logfile during commit scan for session 1 thread 1 sequence 1064, +DATA/r5standby/arc2/1_1064_865010252.dbf
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 1065, +DATA/r5standby/arc2/1_1065_865010252.dbf
LOGMINER: End mining logfiles during commit scan for session 1
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1064, +DATA/r5standby/arc2/1_1064_865010252.dbf
Tue Jan 10 10:23:02 2017
LOGSTDBY Analyzer process AS00 started with server id=0 pid=56 OS id=2862
Tue Jan 10 10:23:02 2017
LOGSTDBY Apply process AS05 started with server id=5 pid=61 OS id=2872
Tue Jan 10 10:23:02 2017
Tue Jan 10 10:23:02 2017
LOGSTDBY Apply process AS03 started with server id=3 pid=59 OS id=2868LOGSTDBY Apply process AS04 started with server id=4 pid=60 OS id=2870


Tue Jan 10 10:23:02 2017
LOGSTDBY Apply process AS02 started with server id=2 pid=58 OS id=2866
Tue Jan 10 10:23:02 2017
LOGSTDBY Apply process AS01 started with server id=1 pid=57 OS id=2864
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1064, +DATA/r5standby/arc2/1_1064_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1065, +DATA/r5standby/arc2/1_1065_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1065, +DATA/r5standby/arc2/1_1065_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1066, +DATA/r5standby/arc2/1_1066_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1066, +DATA/r5standby/arc2/1_1066_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1067, +DATA/r5standby/arc2/1_1067_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1067, +DATA/r5standby/arc2/1_1067_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1068, +DATA/r5standby/arc2/1_1068_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1068, +DATA/r5standby/arc2/1_1068_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1069, +DATA/r5standby/arc2/1_1069_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1069, +DATA/r5standby/arc2/1_1069_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1070, +DATA/r5standby/arc2/1_1070_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1070, +DATA/r5standby/arc2/1_1070_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1071, +DATA/r5standby/arc2/1_1071_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1071, +DATA/r5standby/arc2/1_1071_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1072, +DATA/r5standby/arc2/1_1072_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1072, +DATA/r5standby/arc2/1_1072_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1073, +DATA/r5standby/arc2/1_1073_865010252.dbf
LOGMINER: End   mining logfile for session 1 thread 1 sequence 1073, +DATA/r5standby/arc2/1_1073_865010252.dbf
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1074, +DATA/r5standby/onlinelog/sredo09.log
Tue Jan 10 10:23:12 2017
RFS LogMiner: RFS id [2810] assigned as thread [1] PING handler

此時說明正常了, 然後我們可以測試同步,並且可以在備庫上執行建立表等操作了