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

MOSC Banner

Archive Log Deleteion Policy On A Physical Standby Database

edited Oct 24, 2012 5:02AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
Dear Oracle DBA's,

Need your inputs with regards to configuring the right archive log deletion policy on a physical standby database.

This is our environment .........

0.We are using a physical standby dataguard setup running in maximum performance mode. We are having a standalone primary database and single standalone standby database.

1.Primary and Standby database are on RHEL x86 64 bit (Operating System version 5.6) on Oracle 11gR2 version 11.2.0.3

We have offloaded the complete backup setup to the standby database i.e., weekly once level 0, daily incremental backups, periodic archivelog backups etc., take place from the standby database.

On the primary we have cofigured the FRA just to store the archivelogs ( No backups are performed on the primary)

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