My Oracle Support Banner

ORA-12154 when add brokerconfig using GDSCTL (Doc ID 1641409.1)

Last updated on JANUARY 30, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


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.

For the purposes of this document, the following fictitious environment is used as an example
to describe the procedure:

Primary database = primdb1
Standby database = standbydb1
Pool = dbpoolora
Region = Regionora

o ORA-12154 when add brokerconfig using GDSCTL.

o Active dataguard, primary is primdb1 and standby is standbydb1


o The active data guard is configured with broker. Hence using the following command to add to the GDS configuration:

GDSCTL>add brokerconfig -connect <HOST>:<PORT>/SYDPDB1 -pwd <PASSWORD>
DB Unique Name: primdb1
GSM Warnings:
standbydb1:ORA-12154: TNS:could not resolve the connect identifier specified

GDSCTL>config database
Name Pool Status Region
---- ---- ------ ------
standbydb1 dbpoolora Uninitialized regionora
primdb1 dbpoolora Ok regionora



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

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