RE: Duplicating 8.1.7 database to a scn

Hi,
Thanks for the replies. The problem the "set until time" with Oracle 8.1.7 and Solaris is that it does not appear to work, well at least it doesn't on the set-up we have here! So that's why I wanted to use an scn, v$archived_log looks like the place to find it. Also using "set until logseq" is another option, I am trying that to see if it will work, since getting the sequence number for a archive log is easy.

To do a point in time recovery, you need to set you NLS_DATE_FORMAN to mm-dd-yy:hh24:mi_ss in the OS before envoking rman. With the auxiliary database (clone) in nomount do a connect target..., connect auxiliary ..., connect rcvcat .. and then the first line in the run command should be set until time '09-02-2005:08:00:00'; for example.

If you want to know what scn you should use for a set scn look at v$log. or v$archived_log (specify the date you want if you want to find the scn for or you will get a huge list).

Hi,
I need to duplicate an Oracle 8.1.7 database to a given point in time. I have seen problems when trying to do this with the set command specifying a date, but I have done it using an scn number when I got the scn number from a duplication that did a full recovery.

If I stop all transactions in the database how do I find out what scn number to use? I have it in mind to archive the current log so that all of the changes are in the redo stream, will the most recent archive log give me the scn number and if so where do I get this information from.