High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

TNS-12564: TNS:connection refused error after setting up Data gaurd

edited Jan 4, 2019 3:17AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
 I have 2 node rac and standby (non RAC) works fine no error in any log....with out DG broker configuration.
When I introduced DG broker configuration , alert log captures below alert very frequently. I setup DG broker thru OEM.
After removing DGB setting everythin seems to be fine in alert log.  Please suggest me if I want to have DGB setting how to aviod this error.

This error is coming in NODE 2 only where I have set setting...

INBOUND_CONNECT_TIMEOUT_LISTENER_1599=120   >> listener.ora
SQLNET.INBOUND_CONNECT_TIMEOUT=180                >> sqlnet.ora


==Alert Log Error ===
Fatal NI connect error 12521, connecting to:
 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<node2 hostname>l)(PORT=<local_port>))(CONNECT_DATA=(SERVICE_NAME=p1kronos_DGB)(INSTANCE_NAME=p1kronos1)(SERVER=DE

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center