A few couple more places you should check:
What is returned by "restore database preview;"?
If you're not using a recovery catalog, what is the setting
for control_file_record_keep_time?
--
Fernando.
To educate a man in mind and not in morals is to educate a menace to
society.
Theodore Roosevelt
On Fri, Mar 4, 2016 at 9:42 AM, Ndidi Ibeachum <chinedui@xxxxxxxxxx> wrote:
Dear Dragutin;
I had been playing around with the redundancy using both that and recovery
window options.
You did give me an excellent idea, I just incorporated 'catalog start
with...' in my rman script till i figure out what the problem is.
It is just 'strange' since I have other databases running similar backup
and they don't have this issue.
Thanks for the feedback. I'd let you know what I find :)
Chinedu Ibeachum
------------------------------
Date: Fri, 4 Mar 2016 13:02:07 +0100
Subject: Re: RMAN Backup Strange Behavior
From: orahawk@xxxxxxxxx
To: chinedui@xxxxxxxxxx
CC: oracle-l@xxxxxxxxxxxxx
"
The command you mentioned reports as before "no obsolete backups found".
"
Yes but, in such cases, you need to play a little with the options and
analyze the behaviour, before saying that you hitted a bug, that is why I
suggested you to play with your retention policy - but of course you need
to generate additional backups and see what is happening with redundancy
1,2,3.
If you don't have enough space, try to backup some small tablespace.
"
For the part you don't understand, I mean that the backup records of the
previous day which is meant to be marked obsolete on completion of the
current backup disappears and the physical backups remain without being
deleted.
I then try the crosscheck and these old physical backups don't still show
up.
"
So you say that the backups are deleted from the catalog but are still on
the disk. The crosscheck is used in the opposite case - when the backups
are in the catalog and are not on the disk, so the crosscheck will not
help you in your case.
Can you do catalog backuppiece '/your_backup_directory/your_backup' , the
backupset should appear in the controlfile , and then issue the report
obsolete command again.
Also, can you verify the privileges at OS level, maybe something has
changed recently.
Dragutin
