为12.1DataGuard配置DGMGRL遇到ORA-16698

为12.1.0.2 DataGuard配置DGMGRL时遇到了ORA-16698错误： BANNER CON_ID------------------------------------------------------------------------------------------ ----------Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Produ

为12.1.0.2 DataGuard配置DGMGRL时遇到了ORA-16698错误：

BANNER                                                                                         CON_ID
------------------------------------------------------------------------------------------ ----------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production                        0
PL/SQL Release 12.1.0.2.0 - Production                                                              0
CORE    12.1.0.2.0      Production                                                                          0
TNS for Linux: Version 12.1.0.2.0 - Production                                                      0
NLSRTL Version 12.1.0.2.0 - Production                                                              0
DGMGRL> DGMGRL> [oracle@PD009 ~]$ oerr ora 16698
16698, 0000, "LOG_ARCHIVE_DEST_n parameter set for object to be added"
// *Cause:  One or more LOG_ARCHIVE_DEST_n initialization parameters that
//          contain a SERVICE attribute but not the NOREGISTER attribute were
//          set when attempting to create a configuration or add a standby or
//          far sync instance to the configuration.  askmaclean.com
// *Action: If creating a configuration, clear all LOG_ARCHIVE_DEST_n
//          initialization parameters that contain a SERVICE attribute but not
//          the NOREGISTER attribute. If adding a standby database or far sync
//          instance, clear the LOG_ARCHIVE_DEST_n initialization parameter
//          that specifies the database or far sync instance to be added.

这个错误可以通过在Primary 和 Standby上取消log_archive_dest_n参数来解决，实际这一块的参数应当是交给DG broker 来管理了，不再需要人为介入设置。

primary:
SQL>  alter system reset log_archive_dest_2 scope=spfile sid='*';
System altered.
SQL> alter system reset log_archive_dest_1 scope=spfile sid='*';
System altered.
SQL> startup force;
ORACLE instance started.
standby:
SQL>  alter system reset log_archive_dest_2 scope=spfile sid='*';
System altered.
SQL> alter system reset log_archive_dest_1 scope=spfile sid='*';
System altered.
重启primary和standby实例
[oracle@PD009 ~]$  dgmgrl sys/oracle@PDPROD
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production
Copyright (c) 2000, 2013, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected as SYSDBA.
DGMGRL> create CONFIGURATION PDPROD as primary database is PDPROD CONNECT IDENTIFIER IS  PDPROD;
Configuration "pdprod" created with primary database "pdprod"
add database PDSTBY as CONNECT IDENTIFIER IS PDSTBY MAINTAINED AS PHYSICAL;
Database "pdstby" added
Connected as SYSDBA.
DGMGRL> enable configuration;
Enabled.
DGMGRL> DGMGRL> show configuration;
Configuration - pdprod
  Protection Mode: MaxPerformance
  Members:
  pdprod - Primary database
    pdstby - Physical standby database 
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS   (status updated 5 seconds ago)

Related posts:

1. Recreate failovered primary database using Flashback Database
2. Duplicate standby database from active database
3. 解决DGMGRL Unable to connect to database ORA-12541: TNS:no listener问题
4. 11gR2新特性:STANDBY_MAX_DATA_DELAY
5. 关于参数log_file_name_convert
6. 如何重置Exadata cell上的flash cache的内容
7. 11gR2游标共享新特性带来的一些问题以及_cursor_features_enabled、_cursor_obsolete_threshold和106001 event
8. DataGuard与异构平台
9. 如何绕过ORA-00701错误和降低bootstrap对象的高水位
10. _shared_pool_reserved_pct or shared_pool_reserved_size with ASMM

原文地址：为12.1 DataGuard配置DGMGRL遇到ORA-16698, 感谢原作者分享。