Skip to main content

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

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


Error:

[oracle@fundb ~]$ dgmgrl
DGMGRL for Linux: Release 12.2.0.1.0 - Production on Sat Jul 19 18:03:42 2019

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

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect /
Connected to "PRIM_CL"
Connected as SYSDG.
DGMGRL>
DGMGRL> create configuration 'PRIM_CL' as primary database is 'PRIM_CL' connect identifier is PRIM_CL;
Configuration "PRIM_CL" created with primary database "PRIM_CL"
DGMGRL>
DGMGRL> add database 'STAN_CL' as connect identifier is STAN_CL maintained as physical;
Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set

Failed.
DGMGRL>
DGMGRL> exit


Solution:

1. Remove the DG Broker configuration

DGMGRL> remove configuration;
Removed configuration
DGMGRL>

2. Disable log_archive_dest_2

On Primary

SQL> show parameter log_archive_dest_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
log_archive_dest_2                   string      SERVICE=STAN_CL LGWR ASYNC VAL
                                                 ID_FOR=(ONLINE_LOGFILES,PRIMAR
                                                 Y_ROLE) DB_UNIQUE_NAME=STAN_CL

SQL>

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='' scope=both;

System altered.

SQL> show parameter log_archive_dest_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
log_archive_dest_2                   string

SQL>

On Standby

SQL> show parameter log_archive_dest_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
log_archive_dest_2                   string      SERVICE=PRIM_CL LGWR ASYNC VALID_
                                                 FOR=(ONLINE_LOGFILES,PRIMARY_R
                                                 OLE) DB_UNIQUE_NAME=PRIM_CL
SQL>

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='' scope=both;

System altered.

SQL> show parameter log_archive_dest_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
log_archive_dest_2                   string

SQL>

3. Disable / Enable DG Broker

On Primary

SQL> show parameter dg_broker_start

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
dg_broker_start                      boolean     TRUE
SQL>
SQL> alter system set dg_broker_start=false scope=both;

System altered.

SQL> alter system set dg_broker_start=true scope=both;

System altered.

SQL>  show parameter dg_broker_start

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
dg_broker_start                      boolean     TRUE

SQL>

On Standby

SQL> show parameter dg_broker_start

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
dg_broker_start                      boolean     TRUE

SQL>
SQL> alter system set dg_broker_start=false scope=both;

System altered.

SQL> alter system set dg_broker_start=true scope=both;

System altered.

SQL> show parameter dg_broker_start

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------dg_broker_start                      boolean     TRUE

SQL>

4. Configure DG Broker

On Primary

[oracle@fundb ~]$ dgmgrl
DGMGRL for Linux: Release 12.2.0.1.0 - Production on Sat Jul 19 18:25:13 2019

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

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect /
Connected to "PRIM_CL"
Connected as SYSDG.
DGMGRL> create configuration 'PRIM_CL' as primary database is 'PRIM_CL' connect identifier is PRIM_CL;
Configuration "PRIM_CL" created with primary database "PRIM_CL"
DGMGRL>
DGMGRL> add database 'STAN_CL' as connect identifier is STAN_CL maintained as physical;
Database "STAN_CL" added
DGMGRL>
DGMGRL> show configuration;

Configuration - PRIM_CL

  Protection Mode: MaxPerformance
  Members:
  PRIM_CL    - Primary database
    STAN_CL - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
DISABLED

DGMGRL>

5. Enbale LOG_ARCHIVE_DEST_2

On Primary

SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM_CL,STAN_CL)' scope=both;

System altered.

SQL>

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=STAN_CL LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STAN_CL' scope=both;

System altered.

SQL>

On Standby

SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM_CL,STAN_CL)' scope=both;

System altered.

SQL>


SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=PRIM_CL LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIM_CL' scope=both;

System altered.

SQL>

6. Enable DG Broker Configuration

DGMGRL> enable configuration;
Enabled.
DGMGRL>

DGMGRL> show configuration;

Configuration - PRIM_CL

  Protection Mode: MaxPerformance
  Members:
  PRIM_CL    - Primary database
    STAN_CL - Physical standby database (disabled)

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS   




Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
Post a Comment
Read more