Re: v$archived_log problem after restoring db on a new server

On 4 May 2005 10:09:24 -0700, "crajac66_at_gmail.com" <crajac66_at_gmail.com> wrote:

>Some questions.
>- Did I miss something in the restore steps I implemented on server B?
>- I thought that by opening the database with resetlogs that the old
>sequence#'s (i.e. 3970 and higher) would have been removed from the
>base table that v$archived_log gets it's data from. Is my understanding
>correct?
>-If I leave the database as is, will there be a problem when the
>current sequence# (21) eventually advances to 3970?
>
>To fix the problem here are some of the ideas I have.
>
>1. Shutdown and open the database again with resetlogs.
>2. Recreate the controlfile
>3. Start all over and restore the database again.
>
>Any insight as to why the old sequence#'s are still present and how to
>remove them from the base table for v$archived_log would be
>appreciated.

question 1: No
question 2: No, also no need for that as the archivelog number is reset, but the SCN is never reset.
Question 3: see question 2

Consequently, you don't have a problem, and you don't need to fix anything.
Also there is no base table, the data is only in the control file. If you edit the controlfile directly you will invalidate your support contract.

--
Sybrand Bakker, Senior Oracle DBA