DATAGUARD - Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set Failed.

 Scenario Preview: Getting  oracle error ORA-16698 dduring creation of dataguard in 19c release.  

Physical standby already created and in sync.  steps to create datagauard on 19c and troubleshooting error as well. 

Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set Failed.

[oracle@srv6 dgbroker]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Aug 17 20:10:53 2021

Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.3.0.0.0

SQL> ALTER SYSTEM SET DG_BROKER_CONFIG_FILE1='/u01/dgbroker/pr1ORADB.dat';

System altered.

SQL> ALTER SYSTEM SET DG_BROKER_CONFIG_FILE2='/u01/dgbroker/pr2ORADB.dat';

System altered.

SQL> SHOW PARAMETER DG_BROKER_START

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

dg_broker_start                      boolean     FALSE

SQL>  ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH;

System altered.

SQL> alter system set LOG_ARCHIVE_DEST_2='' SCOPE=BOTH sid='*';

System altered.

SQL> exit

Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.3.0.0.0

[oracle@srv6 dgbroker]$ dgmgrl sys/system123@TEST19C

DGMGRL for Linux: Release 19.0.0.0.0 - Production on Tue Aug 17 20:13:48 2021

Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

Welcome to DGMGRL, type "help" for information.

Connected to "TEST19C"

Connected as SYSDBA.

DGMGRL> show configuration;

ORA-16532: Oracle Data Guard broker configuration does not exist

Configuration details cannot be determined by DGMGRL

DGMGRL> CREATE CONFIGURATION TEST19C AS PRIMARY DATABASE IS TEST19C CONNECT IDENTIFIER IS TEST19C;

Configuration "test19c" created with primary database "test19c"

DGMGRL> show configuration;

Configuration - test19c

  Protection Mode: MaxPerformance

  Members:

  test19c - Primary database

Fast-Start Failover:  Disabled

Configuration Status:

DISABLED

DGMGRL> ADD DATABASE TESTDR AS CONNECT IDENTIFIER IS TESTDR;

Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set

Failed.

• Primary database LOG_ARCHIVE_DEST_2 attribute aleady clear but as we noticed standby attribute was not cleared so we set parameterd to emplty in physical standby database. 

SQL> alter system set LOG_ARCHIVE_DEST_2='' SCOPE=BOTH sid='*';

System altered.

SQL>

DGMGRL> ADD DATABASE TESTDR AS CONNECT IDENTIFIER IS TESTDR;

Database "testdr" added

DGMGRL> show configuration;

Configuration - test19c

  Protection Mode: MaxPerformance

  Members:

  test19c - Primary database

    testdr  - Physical standby database

Fast-Start Failover:  Disabled

Configuration Status:

DISABLED

DGMGRL>

DGMGRL> ENABLE CONFIGURATION;

Enabled.

DGMGRL> SHOW CONFIGURATION;

Configuration - test19c

  Protection Mode: MaxPerformance

  Members:

  test19c - Primary database

    testdr  - Physical standby database

      Warning: ORA-16853: apply lag has exceeded specified threshold

Fast-Start Failover:  Disabled

Configuration Status:

WARNING   (status updated 2 seconds ago)

DGMGRL>

DGMGRL> EDIT DATABASE TESTDR SET STATE=APPLY-ON;

Succeeded.

DGMGRL> SHOW CONFIGURATION;

Configuration - test19c

  Protection Mode: MaxPerformance

  Members:

  test19c - Primary database

    testdr  - Physical standby database

Fast-Start Failover:  Disabled

Configuration Status:

SUCCESS   (status updated 44 seconds ago)

DGMGRL>