Re: Latest SCN in archive-log files

"Howard J. Rogers" wrote:
>
> v#archived_log in the original database may help (it tells you the first
> change number of a log, not the last, though).

Sure it does - look at first_change# for the first SCN, and look at next_change# for the last. You'll see that next_change# for a given archive corresponds to first_change# for the archive immediately after it.

> But I question what it is
> that you are trying to achieve. Ordinarily, unless you are seeking to
> perform an incomplete recovery, and halt the application of redo before it
> would otherwise stop on its own, there is seldom a need to do a 'recover
> until change'.

True, unless he's cloning a database, which is often a frequent event in production datacenters. We do it everyday (when building a reporting instance from production). We also do it everytime we clone a database for testing, which is to say many times a week.

Regards,
Sean Received on Thu Mar 14 2002 - 14:42:50 CST