Re: Regarding next_change#
From: Hemant K Chitale <hemantkchitale_at_gmail.com>
Date: Fri, 2 Oct 2009 01:07:58 -0700 (PDT)
Message-ID: <05e68fc8-f095-4d7d-9abe-0613b11c0a69_at_m7g2000prd.googlegroups.com>
Date: Fri, 2 Oct 2009 01:07:58 -0700 (PDT)
Message-ID: <05e68fc8-f095-4d7d-9abe-0613b11c0a69_at_m7g2000prd.googlegroups.com>
Possibility : The Redo Log File containing SCNs close to 362846 has not been archived out yet. It is still one of the online redo logs.
On Sep 30, 10:02 pm, Ganesh <ganesh.tam..._at_gmail.com> wrote:
> SQL> select max(next_change#) from v$archived_log;
>
> MAX(NEXT_CHANGE#)
> -----------------
> 362799
>
> I am expecting a value near to 362846 to get displayed as output to
> this query. (But the value displayed is nearer to SCN for earlier
> backup) I am not able to understand why the next_change# is not
> getting updated. Please let me know whether I am missing something
> here.
>
> Thanks in advance,
> Ganesh Tambat
Received on Fri Oct 02 2009 - 03:07:58 CDT