Re: dataguard, and rman backup of archive logs

  • From: Ravi Gaur <ravigaur1@xxxxxxxxx>
  • To: eglewis71@xxxxxxxxx
  • Date: Tue, 2 Feb 2010 16:45:04 -0600

Ed,
We have a similar setup here. We have to manually clean the logs (cronjob)
since only the softlinks gets deleted by the Oracle LSB apply.
We basically have 2 destinations:
log_archive_dest_1 has valid_for=(ALL_LOGFILES,ALL_ROLES) (that is where the
physical archives are sitting)
log_archive_dest_2 has valid_for=(STANDBY_LOGFILES, STANDBY_ROLE)
I don't have a place to test as we only have this in production but I
suspect log_archive_dest_2 setting is what causes the softlinks

- Ravi


On Tue, Feb 2, 2010 at 12:27 PM, Edward Lewis <eglewis71@xxxxxxxxx> wrote:

> Hello,
>      I have a rac cluster, with dataguard replicating
> to a logical standby, as well as a physical standby.
> All environments are using ASM.
>
>      I use RMAN to back up the archive logs on the LSB.
> The LSB is a set up to delete the archive logs once they are
> backed up. When I check the alert log, it shows the archive logs
> being deleted.  When I check the archive log location on ASM,
> the archive logs still remains.
>         They way ASM is set up is has a soft link to the actual archive
> log files in the archive log directory. Here is an example.
>
>  srptpre_dcea562_1_919_702560930.arc =>
> +REM_ARCH/srptpre/ARCHIVELOG/2010_02_02/thread_1_seq_919.670.709896975
>
>       So, when Oracle deletes the archive log, it just removes the link
> name.
> In this case, that would be "srptpre_dcea562_1_919_702560930.arc".
> The actual archive log file,
> "+REM_ARCH/srptpre/ARCHIVELOG/2010_02_02/thread_1_seq_919.670.709896975"
> still remains. It does not get deleted.
>
> Has anyone seen this sort of behavior ? Is there a way to have the archive
> log deleted also ?
>
> Sun solaris 10,  oracle 10.2.0.4.
>
>      thanks
>

Other related posts: