My Oracle Support Banner

New Broker Configuration Fails with DGM-17016 ORA-16664 and ORA-16883 (Doc ID 2466824.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

 

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

 

 

DGM-17016 and ORA-16664 errors while checking the DGMGRL configuration on primary

 

Changes

 New broker configuration

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

Configuration "dg_config" created with primary database "primary"

DGMGRL> ADD DATABASE STANDBY AS CONNECT IDENTIFIER IS STANDBY MAINTAINED AS PHYSICAL;

Database "standby" added

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.