Re: getting rid of copies of archivelogs

From: Robert Freeman <robertgfreeman_at_yahoo.com>
Date: Tue, 16 Sep 2008 09:42:53 -0700 (PDT)
Message-ID: <220351.32532.qm@web38907.mail.mud.yahoo.com>


How are these copies being created? If you are using some tool just to copy them from disk to tape, this will never be recorded in RMAN.

RF

 Robert G. Freeman
Author:
Oracle Database 11g New Features (Oracle Press) Portable DBA: Oracle (Oracle Press)
Oracle Database 10g New Features (Oracle Press) Oracle9i RMAN Backup and Recovery (Oracle Press) Oracle9i New Feature
Blog: http://robertgfreeman.blogspot.com (Oracle Press) The LDS Church is looking for DBA's. You must be LDS to apply (please don't write to me and tell me I'm breaking the law. A church can choose to hire members of it's own faith. Look it up if you don't believe me).

  • Original Message ---- From: David Barbour <david.barbour1_at_gmail.com> To: Claudia Zeiler <czeiler_at_ecwise.com> Cc: Ray Stell <stellr_at_cns.vt.edu>; "oracle-l_at_freelists.org" <oracle-l_at_freelists.org> Sent: Tuesday, September 16, 2008 10:24:36 AM Subject: Re: getting rid of copies of archivelogs

So you've got two archive log destinations defined for your instance? The "standard" backup you're running deletes the logs from only one of the two locations?

"Copies" can have more than one meaning when you're dealing with RMAN.

Presuming you have two destinations defined, If you restore an archivelog file, where does it end up?

On Tue, Sep 16, 2008 at 10:14 AM, Claudia Zeiler <czeiler_at_ecwise.com> wrote:

I need to clarify.

Since I delete the input when I backup the archive logs

 backup archivelog all not backed up delete all input format '/d123/backup/arch_%d_%u_%s';

the problem files are not archive logs, but copies of them. The archive logs have been deleted. These copies are copied off to tape each night, so I don't want them on disk the next day. I especially don't need them on disk a week or two later! All of my rman commands seem to address the original archive logs, not these copies of archive logs. That is why I am coming to wonder if the COPIES of the archivelogs on /d123 may not be rman files at all, and can be cleared out with a simple 'rm'? Of course, I have removed them with an 'rm', but I am worried that they still may be listed somehow in rman.

Thank you in advance to any clarification that you can give.

Claudia Zeiler
ECWise Database Administrator



From: Ray Stell [stellr_at_cns.vt.edu]
Sent: Tuesday, September 16, 2008 5:25 AM To: David A. Barbour
Cc: Claudia Zeiler; oracle-l_at_freelists.org Subject: Re: getting rid of copies of archivelogs

check CONFIGURE ARCHIVELOG DELETION POLICY. I don't think the commands will bypass the policy.

On Mon, Sep 15, 2008 at 10:44:33PM -0400, David A. Barbour wrote:
> Not having my handy manual, I think you might need to specify something like
> "not backed up 1 times" to get the logs to delete. Or you could just have
> "archivelog all" without the not backed up clause and they'd delete. I back
> up "not backed up 1 times" every 15 minutes and delete when the filesystem
> is 50% full.
>
>
>
>
>
>
>
> _____
>
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of Claudia Zeiler
> Sent: Monday, September 15, 2008 9:03 PM
> To: oracle-l_at_freelists.org
> Subject: getting rid of copies of archivelogs
>
>
>
> I have set up a database in archivelog mode with
>
> backup as COMPRESSED BACKUPSET archivelog all not backed up delete all
> input format '/d123/backup/arch_%d_%u_%s';
>
> among my rman script commands.
>
>
>
> Now /d123/ is filling up. I have tried all sorts of rman> delete obsolete
> etc without result. Finally, I wonder, are these copied logs no longer
> part of rman? Is it sufficient to just delete them from the file system?
> Or is there an RMAN command that I haven't tried.
>
>
>
> Thanks in advance for your assistance,
>
>
>
> Claudia Zeiler
>
> Database Administrator
>
> EC|Wise
>
>
>
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Sep 16 2008 - 11:42:53 CDT

Original text of this message