Is there a way to get around setting the Database Log Mode to
"Archivelog"
when configuring the Oracle server for the Oracle Agent? Or is there a
way
to move the Archivelog off the database server to a mapped drive?


"Brian Klein" wrote:
>
>David,
> I have used 3 different mechanisms to do this (each depends on the

use
>and size of the DB)
>1. For small DB - find some kind of del that supports deletions older

then
>X days and use that as a post processing job.
>2. For any size. Create a seperate File grooming job that executes

after
>the DB backup to get the archive logs. This will backup, verify and

then
>delete. This approach can be tricky with autoloaders with multiple

tape
>drives though as the only control mechanism is your time schedule. I

does
>however work well if the timing is managed.
>3. For any size. Create a post processing job that executes a command

like
>del /A:-A c:\oracle\SID\archivelogs\*ARCH*.* .
>This will delete only files which do not have the archive flag set

meaning
>they have been backed up to tape. This tends to require the least

management
>and works for any size DB, no time restrictions or anything else.
>
>Each of these methods work well. It just depends on how many

archivelogs
>you like to have on disk and more importantly how much disk space you

have.
> For large OLTP DB, the last 2 work the best(especially for a crazy DB

such
>as SAP). Unfortunatly these are the best I have found. I have

requested
>an enhancement to have the Oracle agent delete Archivelog files once

they
>are backed up to tape although I have not seen it yet)
>
>Good Luck,
>Brian
>
>
>
>
>"David Kight" wrote:
>>
>>I am evaluating the backup exec for Oracle agent on NT 4.0. I there

an
>automated
>>mechanism to allow for the automatic delete of archive logs after they

are
>>backed up to tape?

>