Thank you. I realised that. I thought that production backup procedure does include following (my assumption apeared to be wrong): RMAN> sql "Alter System Archive Log Current"; RMAN> backup ArchiveLog all; Next time I will definetly rely on current SCN than on last archived SCN. Regards Mindaugas --- Hemant K Chitale <hkchital@xxxxxxxxxxxxxx> wrote: > > ARCHIVE_CHANGE# is the last SCN _archived_ -- ie written out from > Redo to ArchiveLog > You were trying to compare that with current SYSDATE. Obviously, > ARCHIVE_CHANGE# > would be lower than the real current SCN as there transactions are still in > the Online Redo Log > when you get SYSDATE. > > Hemant K Chitale > At 03:19 AM Thursday, you wrote: > >Hi, > > > >Last few days I was dialing with task of restoring and recovering database > >into > >test environment. Database size ~1TB. Production backups are kept on TSM > >server > >and we are using RMAN. Oracle 9.2.0.5 2 node RAC. > > > >Since production server operates in UTC and test box uses EST time > >(UTC-4hours), we decided not to use UNTIL TIME option of recovering. > >Instead we > >decided to use UNTIL SCN. > > > >We run following query to find current SCN in production environment. Is > this > >right place to look for the last SCN? > > > >Select TO_CHAR(ARCHIVE_CHANGE#,'9999999999999') as last_SCN, > >to_char(sysdate,'YYYY-MM-DD HH24:MI:SS') as tstamp > >from V$DATABASE; > > > >LAST_SCN > >-------------------------------------------- > >TSTAMP > >--------------------------------------------------------------------------- > > 14402145866 > >2006-07-16 04:32:59 > > > > > >Thank you > >Mindaugas Navickas > >Oracle DBA > > http://web.singnet.com.sg/~hkchital > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- //www.freelists.org/webpage/oracle-l