My Oracle Support Banner

After add brokerconfig in sharding, gsm got error GSM-40148 and ORA-12154 (Doc ID 2319449.1)

Last updated on JULY 06, 2021

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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.

Symptoms

On : 12.2.0.1 version, Oracle Data Guard

When attempting to start GSM,
the following error occurs.

ERROR
-----------------------
2017-10-17T18:52:50.875679-07:00
GSM is started successfully
2017-10-17T18:52:52.793646-07:00
Dynamic address is already listened on (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<host>)(PORT=<port number>)))
17-OCT-2017 18:52:52 * (ADDRESS=(PROTOCOL=tcp)(HOST=<IP>)(PORT=<port number>)) * service_register * yq%1 * 0
2017-10-17T18:52:52.830835-07:00
GSM-40132: Database "<db name>" is registered
2017-10-17T18:52:54.262802-07:00
GSM-40148: Database task failed:database:"<db name>", status 6, message:"ORA-12154: TNS:could not resolve the connect identifier specified \(ngsmoci_connect\)

But sqlplus sys/<password>@<service> as sysdba on primary can connect to standby database<db name>. And no related error can be found in dg broker log.

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
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.