Re: delete obsolete for archivelogs

  • From: De DBA <dedba@xxxxxxxxxx>
  • To: hostetter.jay@xxxxxxxxx, Oracle Discussion List <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 30 Jun 2010 12:50:56 +1000

Jay,

It only now registers to me that you are on Windows (sympathies...). Did you consider non-oracle factors, such as a brain-dead virus checker or a group policy, or even inherited file system permissions?

Some of my clients have a corporate policy that require every windows server to run an on-access scanner and the particular brand that they use will block "suspicious" activity, such as manipulating the registry or deleting "protected" files. There may be meaningful messages either in the scanner's log files or the Windows Event log.

Just a thought..

Cheers,
Tony

On 30/06/10 12:27 PM, De DBA wrote:
Hey Jay,

I'm not sure if this has already been asked, but do the backups on your
production succeed? The "check logical" predicate may cause RMAN to find
logical corruption and fail a datafile backup. As a result the archive
log files won't be obsoleted as you don't have a new complete level 0
(or full hot) backup.

Any errors in the alert log?

Cheers,
Tony

On 30/06/10 5:45 AM, Jay Hostetter wrote:
A backup occurs each night. The relevant part of the script is below.
Report obsolete does not list my archivelogs, even after crosschecking
backups and archivelogs.
I've logged an SR.
Thank you,
Jay
allocate channel ch1 type disk format
'H:\Oracle_Backups\%d\full_s%s_p%p_t%t.bck';
backup
as compressed backupset
check logical database
filesperset 4
tag='daily_full_backup';
allocate channel ch2 type disk format
'H:\Oracle_Backups\%d\arc_s%s_p%p_t%t.bck';
#
backup
as compressed backupset
tag='daily_arch_backup'
archivelog all channel ch2;

On Mon, Jun 28, 2010 at 1:20 PM, Niall Litchfield
<niall.litchfield@xxxxxxxxx <mailto:niall.litchfield@xxxxxxxxx>> wrote:

How many database backups do you have? I'd read your policy as
obsoleting archive logs no longer required for your oldest level 0
backup. That is I expect having 2 backups of the db more recent than
the oldest log would do the trick. The RMAN command report obsolete
should help.

Niall Litchfield

--
//www.freelists.org/webpage/oracle-l




--
//www.freelists.org/webpage/oracle-l


Other related posts: