ORA-16698 error: BANNERCON_ID invalid OracleDatabase12cEnterpriseEditionRelease12.1.0.2.0 when DGMGRL is configured for 12.1.0.2DataGuard
ORA-16698 error: BANNER CON_ID failed ---------- Oracle Database 12c Enterprise Edition Release 12.1.0.2.0-64bit Produ was encountered when DGMGRL was configured for 12.1.0.2 replica uard
An ORA-16698 error occurred while configuring DGMGRL for 12.1.0.2 javasuard:
BANNER CON_ID------------------------------------------------------------------------------------------ ----------Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production 0PL/SQL Release 12.1.0.2.0 - Production 0CORE 12.1.0.2.0 Production 0TNS for Linux: Version 12.1.0.2.0 - Production 0NLSRTL Version 12.1.0.2.0 - Production 0DGMGRL> DGMGRL> [oracle@PD009 ~]$ oerr ora 1669816698, 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.
This error can be solved by canceling the log_archive_dest_n parameter on Primary and Standby. The actual parameter must be managed by the DG broker and no human intervention is required.
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. restart primary and standby instances [oracle @ PD009 ~] $ Dgmgrl sys/oracle @ PDPRODDGMGRL for Linux: Version 12.1.0.2.0-64bit ProductionCopyright (c) 2000,201 3, 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" addedConnected as SYSDBA. DGMGRL> enable configuration; Enabled. DGMGRL> show configuration; Configuration-pdprod Protection Mode: MaxPerformance Members: pdprod-Primary database pdstby-Physical standby database Fast-Start Failover: DISABLEDConfiguration Status: SUCCESS (status updated 5 seconds ago)
Related posts:
- Recreate failovered primary database using Flashback Database
- Duplicate standby database from active database
- Solve the Problem of DGMGRL Unable to connect to database ORA-12541: TNS: no listener
- New Feature of 11gR2: STANDBY_MAX_DATA_DELAY
- About the parameter log_file_name_convert
- How to reset the flash cache content on Exadata cell
- 11gR2 New Features of cursor sharing, as well as _ cursor_features_enabled, _ cursor_obsolete_threshold and 106001 event
- DataGuard and heterogeneous platforms
- How to bypass ORA-00701 errors and reduce high levels of bootstrap objects
- _ Shared_pool_reserved_pct or shared_pool_reserved_size with ASMM
Original address: 12.1 DataGuard configuration DGMGRL encountered a ORA-16698, thanks to the original author to share.