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

MOSC Banner

Data Guard ORA-00257: archiver error in Primary database with MaxPerformance setting

edited Oct 12, 2019 5:05AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered

Hi all,

Today we had a network problem which resulted in a no connectivity status with our (Data Guard) standby database.

We were very surprised to see that our primary instance was going in to a halt because of an ORA-00257: archiver error.

We are not aware that this is possible if the Data Guard environment is configured  with the MaxPerformance setting.

If we look at our dest. parameters we see that at dest 2 it has the mandatory setting.

Can this be the cause of the problem? and if so why is dest2 set to mandatory when we created a default configuration MaxPerformance with DGMGRL?

Tagged:

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