在11.2.0.3.0 - 64bit配置DG时遇到错误，查看alert:
Mon Feb 01 10:26:37 2016
ARC3 started with pid=24, OS id=3869 
PING[ARC2]: Heartbeat failed to connect to standby 'dg02'. Error is 16047.
Mon Feb 01 10:26:38 2016
QMNC started with pid=25, OS id=3871 
Mon Feb 01 10:26:38 2016
NSA2 started with pid=26, OS id=3873 
ARC2: Archivelog destination LOG_ARCHIVE_DEST_2 disabled: Data Guard configuration identifier mismatch
Archived Log entry 31 added for thread 1 sequence 25 ID 0x6c3720d9 dest 1:
Completed: alter database open
Mon Feb 01 10:26:38 2016
db_recovery_file_dest_size of 2048 MB is 19.49% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Feb 01 10:26:38 2016
Starting background process CJQ0
Mon Feb 01 10:26:38 2016
CJQ0 started with pid=27, OS id=3887 
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Thread 1 advanced to log sequence 27 (LGWR switch)
  Current log# 3 seq# 27 mem# 0: /u01/app/oracle/oradata/dg/redo03.log
Archived Log entry 32 added for thread 1 sequence 26 ID 0x6c3720d9 dest 1:
Mon Feb 01 10:26:50 2016
FAL[server]: DGID from FAL client not in Data Guard configuration
Mon Feb 01 10:36:37 2016
Starting background process SMCO
Mon Feb 01 10:36:37 2016
SMCO started with pid=28, OS id=3956 
Mon Feb 01 11:05:59 2016
FAL[server]: DGID from FAL client not in Data Guard configuration
 
1,在standby检查是否 set log_archive_config='DG_CONFIG=(dg01,dg02)';
2,在standbyALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE