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

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...
Post a Comment
Read more