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

MOSC Banner

Archive log deletion policy

edited Oct 13, 2009 4:07AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 5 commentsAnswered
 I am testing a data guard setup which will eventually implemented in production environment. The idea is to have a logical standby as copy of production database to offload reporting load. The production database will be the primary. Currently, the production database creates archive logs in the flash recovery area. Every 3 hours, a Netbackup job copies these archive logs to tape and deletes them from flash recovery area. With logical standby in place, this strategy of archive log deletion will create a problem as the archive logs which have not been transported yet might get deleted.

What is the best way to get around this limitation without changing the archive log deletion policy? I did read about the RMAN configuration

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