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

MOSC Banner

DEST_N parameter get lost after db is restarted

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

Good morning

We are facing an issue whenever we restart one of our dataguard databases. Everytime we have to restart one of the databases(whether its the primary or one of the standbys) the dest_n parameter in that database get lost, so we have to reconfigure it. I've been looking on the internet for any document or clue on how to solve the issue, but unfortunately haven't found anything yet. Following are the details of our configuration:


- Primary: 2-nodes RAC 12.2 EE

- OS: Solaris 11

- Configuration: Maximun performance

- Standby1: Single Physical Standby 12.2 EE

- OS: Solaris 11

- Standby2: 2-nodes RAC 12.2 EE

- OS: Solaris 11

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