Re: clearing dba_registered_archive_logs

Hi. No that didnt work. It didnt even look at the foreign archive logs. It only looked at the regular archive logs. Probably a bug.

On Thu, Sep 13, 2018 at 9:22 PM Leng <lkaing_at_gmail.com> wrote:

> Try this:
>
> Rman> crosscheck foreign archivelog all;
> Rman> delete expired foreign archivelog all;
>
> Cheers,
> Leng
>
> On 14 Sep 2018, at 11:31 am, Andrew Kerber <andrew.kerber_at_gmail.com>
> wrote:
>
> Hi. I appreciate the response. However, because the logs have already
> been deleted I just get an error message about the file not being present.
> THe logs still show up on the dba_registered_archive_log view. So I just
> need to remove them from the view, they are already gone from asm.
>
> On Thu, Sep 13, 2018 at 8:23 PM Vishnu <vishnukumarmp_at_gmail.com> wrote:
>
>> Hi Andrew, Check this Support note
>>
>> How To Delete Archive Logs From Downstream Database (Doc ID 2011174.1)
>>
>> Thanks,
>> Vishnu
>>
>> On Thu, Sep 13, 2018 at 7:57 PM Andrew Kerber <andrew.kerber_at_gmail.com>
>> wrote:
>>
>>> I have deleted a large number of files manually due to space
>>> considerations from asm, all are in this
>>> path:+RECOVERY/FOREIGNARCHIVELOG/dbname. However, the deleted files still
>>> show up in dba_registered_archive_logs. This is a downstream capture
>>> database, so the logs came in from another database and were mined for
>>> data, and I manually deleted them. Now I need to clear them from the
>>> dba_registered_archive_logs view. Any ideas on how to do that? Crosscheck
>>> archivelog all in rman isnt even aware of them.
>>>
>>> --
>>> Andrew W. Kerber
>>>
>>> 'If at first you dont succeed, dont take up skydiving.'
>>>
>>
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

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