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

MOSC Banner

How to get rid of a log_archive_dest_state_2 once the standby database is log_archive_dest_state_3?

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
  1. An UPS failure made the data guard database fail over to the standby database which had been log_archive_dest_state_2
  2. Created a new standby database on the old primary server and then failed over to it. Now I have a primary database with a log_archive_dest_state_2 prod database that did not exist before that is supposedly open and the standby database as log_archive_dest_state_3 as prod_stdby and it is applying the archive logs.
  3. The archive logs are not being deleted since the new log_archive_dest_state_2 open prod database has not applied the archive logs and never will.

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