Database Backup and Recovery (MOSC)

MOSC Banner

Very odd RMAN error with RETENTION POLICY

edited Dec 11, 2013 7:06PM in Database Backup and Recovery (MOSC) 5 commentsAnswered
Hello,

Any insights you may have with this error are greatly appreciated.  I'll post follow up details and solution.

Over 99% of our databases that have backup retention policy set to use a RECOVERY WINDOW are successful.  We recently found what appears to be random occurrences RMAN, on it's own, switching the retention policy from RECOVERY WINDOW to REDUNDANCY 1.

For example:

Note that the retention policy was specifically set to "RECOVERY WINDOW OF 30 DAYS" in the script.  RMAN acknowledges the retention policy was set to "RECOVERY WINDOW OF 30 DAYS" ***BUT*** RMAN sets the retention policy to "redundancy 1".

old RMAN configuration parameters:

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