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

MOSC Banner

Broker configuration with multiple networks

edited Apr 16, 2013 1:39PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 11 commentsAnswered
Hi,

I'm configuring Dataguard 10g defining all parameters with TNS alias: FAL_CLIENT, FAL_SERVER, SERVICE option in LOG_ARCHIVE_DEST, LOCAL_LISTENER and REMOTE_LISTENER.

Once configured without Broker, all is working great. But defining DG_BROKER_START to TRUE I can see this messages on the DG log:

DG 2012-09-13-15:32:37 0 2 0 RSM Warning: the connect identifier '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=blsalutorcl316-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=blsalutorcl216-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=blsalutorcl215-vip)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl10g_XPT.cspt.es)(SERVER=dedicated)))' of the primary site 'orcl10g' exceeds the individual string limit of 255 while setting fal_server parameter.

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