Database Backup and Recovery (MOSC)

MOSC Banner

Can someone explain this INCREMENTAL LEVEL 0 RMAN behavior

edited Mar 7, 2012 1:29AM in Database Backup and Recovery (MOSC) 13 commentsAnswered
Environment:   O/S: Linux  2.6.18-92.1.22.el5  64-bit.

Oracle: 10.2.0.4

RMAN: 10.2.0.4

I'm running "backup incremental level 0 cumulative database plus archivelog ;"

I'm getting the error:

RMAN-03002: failure of backup plus archivelog command at 01/06/2012 02:38:19
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

The archive log it is complaining about is several weeks old, it's been backed up and deleted (via RMAN archivelog backup). 

The retentionis: RETENTION POLICY TO REDUNDANCY 1;

If I'm running a level 0, why does it care about a prior archive log?

More puzzlement:  The archive log in question continually shows in a "backup list summary" even though I've run "crosscheck", "delete obsolete" and "delete expired".  An immediate "backup list summary" does not show the files, but a subsequent "list backup summary" shows them still existing and "ACTIVE".

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center