ORA error

ORA-16698

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

Quick fix

Cause
DGMGRL refused ADD DATABASE (or ENABLE CONFIGURATION) because one of the databases already has a LOG_ARCHIVE_DEST_n that ships redo to a SERVICE. The broker manages redo transport itself and will not take over a destination it did not create. The parameter can be on the primary, the standby, or both.
Fix
Clear the remote LOG_ARCHIVE_DEST_n on both databases (keep the local destination), then add the database to the broker again. Set transport options through broker properties such as LogXptMode from then on.
SHOW PARAMETER log_archive_dest_2
ALTER SYSTEM SET log_archive_dest_2 = '' SCOPE=BOTH;
Full walkthrough: ORA-16698 While Adding a Standby to Data Guard Broker: Cause and Fix (...

The article that fixes it