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

MOSC Banner

Standby Archive Logs in Primary Recovery Catalog

edited Aug 27, 2015 8:05AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered

Oracle RDBMS 12.1.0.2

Non-Active Dataguard, one primary and one standby

We have a primary database with scheduled RMAN backups happening, and every day we do a PREVIEW to make sure all is right. 

We've been getting these messages:

no backup of archived log for thread 1 with sequence 2180 and starting SCN of 74815143139 found to restore

And have pieced this together:


At first we had the primary rman archivelog deletion policy as:

          CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED TO ALL STANDBY:

This was a bad thing to do because it caused (using 2142 as an example)

- archive log 2142 generated on primary

- archive log 2142 shipped to standby and applied 

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