前言：
log_archive_config 決定remote redo log的傳輸，正常配置data guard的環境中，參數應為：dg_config=(procdb,procdb_std)
[ DG_CONFIG=(remote_db_unique_name1 [, ... remote_db_unique_name30) | NODG_CONFIG ]
在搭建ADG的時候，如果不小心將unique name寫錯，日志不會傳輸到備庫，就會報如下錯誤：
這是你會發現，defer and enable log_archive_dest_2 是不管用的，殺掉主庫的歸檔進程重啟，也是不管用的。日志就是不傳。
這是因為主服務器上的ARCx進程永遠卡在網絡上，或者負責更新應用列的ARCx進程會卡在網絡上，無法恢復自己。
執行如下操作：
ARCx processes on the primary need to be restarted.
Assuming that log transport from the primary is configured by log_archive_dest_2.
Please perform the following:
1) If the Data Guard Broker is running, disable Data Guard Broker on both primary and standby:
SQL> alter system set dg_broker_start=FALSE;
2) On the Primary Database:
- Set log transport state to DEFER status:
SQL> alter system set log_archive_dest_state_2='defer';
SQL> alter system switch logfile;
- Reset log_archive_dest_2
SQL> show parameter log_archive_dest_2 -------------------> Note this value
NAME TYPE VALUE
------------------------------------ ---------- ------------------------------
log_archive_dest_2 string service="(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 1.1.1.111)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = procdb)(UR=A)))" lgwr async compression=enable valid_for=(online_logfiles,primary_role) db_unique_name=procdb
SQL> alter system set log_archive_dest_2 = '';
- Switch logfiles on the Primary
SQL> alter system switch logfile;
3) On the Standby Database:
- Cancel Managed Recovery
SQL> alter database recover managed standby database cancel;
- Shutdown the Standby Database
SQL> shutdown immediate
4) On the Primary: kill the ARCx Processes and the Database will respawn them automatically immediately without harming it.
ps -ef | grep -i arc
kill -9 <ospid of ARC process> <another ospid of ARC process> ...
5) On standby server, startup Standby Database and resume Managed Recovery
SQL> startup mount;
SQL> alter database recover managed standby database [using current logfile] disconnect;
6) Re-enable Log Transport Services on the Primary:
SQL>Alter system set log_archive_dest_2='Service=..............' ; Set log_archive_dest_2 (Which was reset in step 2) to its original value
Alter system set log_archive_dest_2='service="(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 1.1.1.111)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = procdb)(UR=A)))" lgwr async compression=enable valid_for=(online_logfiles,primary_role) db_unique_name=procdb';
SQL> alter system set log_archive_dest_state_2='enable' ;
At this point all the ARCx processes should be up and running on the Primary.
7) Re-enable the Data Guard Broker for both, Primary and Standby if applicable:
SQL> alter system set dg_broker_start=true;
8) Please work with your Network Administrator to make sure the following Firewall Features are disabled.
SQLNet fixup protocol
Deep Packet Inspection (DPI)
SQLNet packet inspection
SQL Fixup
SQL ALG (Juniper firewall)
執行后恢復正常
參考：Logs are not shipped to the physical standby database (Doc ID 1130523.1)