Re: DataGuard with Physical & Snapshot Standby not deleting archivelogs
From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Tue, 10 Sep 2013 14:53:43 -0500
Message-ID: <CAJvnOJbfCedUcoTV6fcg=ifv3j7bic2x6k022WeR3LudYMA7RQ_at_mail.gmail.com>
Well, if there is no other option, you could probably use the v$ view to create an rman delete script based on the sequence number. It might be an interesting exercise. I expect the syntax is something like this, though I would have to look it up to be sure: delete force backup of archivelog from sequence x until sequence y;
Date: Tue, 10 Sep 2013 14:53:43 -0500
Message-ID: <CAJvnOJbfCedUcoTV6fcg=ifv3j7bic2x6k022WeR3LudYMA7RQ_at_mail.gmail.com>
Well, if there is no other option, you could probably use the v$ view to create an rman delete script based on the sequence number. It might be an interesting exercise. I expect the syntax is something like this, though I would have to look it up to be sure: delete force backup of archivelog from sequence x until sequence y;
On Tue, Sep 10, 2013 at 2:34 PM, Maaz Anjum <maazanjum_at_gmail.com> wrote:
> Don,
> I've seen this issue before when I configured Data Guard along with
> GoldenGate, the latter was purposefully registered to use LogMiner within
> the primary database. We had the exact same error message during "backup
> and deleting" arcihived logs. The only fix, before the actual fix, was to
> delete them with the "force" option.
>
> Do you recall making any changes with registering a streams or GoldenGate
> for integrated capture against the primary database?<SNIP>
>
-- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.' -- http://www.freelists.org/webpage/oracle-lReceived on Tue Sep 10 2013 - 21:53:43 CEST