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

MOSC Banner

DG broker, RAC: VIP or SCAN

edited Mar 15, 2016 5:05AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered

Hi,


According to "Doc ID 1638605.1": "The primary database should be using the VIP hostname in the TNS connect string to connect to the standby database for archive log shipments."

But in that case I got (dg broker log):

Redo transport problem detected: redo transport for database DB2 has the following error:

  ORA-01034: ORACLE not available

And that because only first instance was shutdown (2 more instances were up and running).


Do I understand right that if one of the instances is down and CRS is still up then this node vip is still up and answers with "ORACLE not available". This answer doesn't lead to connection failover to the next address (next vip) in the connecting string (tns entry at primary site) because failover is only when there is a connection problem (either connection is dropped or no listener at all).

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