Re: production database to test database, apply archive logs, online backup

yls177_at_hotmail.com (yls177) wrote in message news:<c06e4d68.0404190629.3457e83e_at_posting.google.com>...
> Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl> wrote in message news:<af50801qbk7bsvlibn15j2vvq35tr6siv4_at_4ax.com>...
> > On 16 Apr 2004 08:21:28 -0700, yls177_at_hotmail.com (yls177) wrote:
> >
> > >hrishys_at_yahoo.co.uk (hrishy) wrote in message news:<4ef2a838.0404160014.26068408_at_posting.google.com>...
> > >> Hi Yes
> > >>
> > >> You are doing a sort of standby database..remember you shouldnt be
> > >> doing any transactions in your test database.
> > >>
> > >> regards
> > >> Hrishy
> > >>
> > >> yls177_at_hotmail.com (yls177) wrote in message news:<c06e4d68.0404150445.2d9e2f99_at_posting.google.com>...
> > >> > if i take the production server backup (full) and restore to test
> > >> > server, and opened it. and then after some time, took the online
> > >> > backup of production with its control file , and restore to the test
> > >> > server, i am able to do so , right?
> > >> >
> > >> > also, i am able to apply archived logs after the online backup so that
> > >> > i have a latest production backup in the test server as the original
> > >> > production backup?
> > >
> > >
> > >
> > >not doing any transactions as in "open the database"?
> >
> > It doesn't really matter. You are trying to hack yourself out already,
> > so it really doesn't matter how you accomplish your goal.
> > Obviously you *CAN'T* synchronize your 'test' database using the
> > archives from a production database, because as soon as you do
> > *ANYTHING* on that database, the SCNs of 'test' and production
> > databases are going out of sync.
> > Do you really believe you can 'merge' 2 databases using archives. Try
> > to *understand* how Oracle keeps track of transactions by reading
> > documentation and do not simply *assume* it will be possible.
>
>
> one says can and the other say not...
> so how?

You can do it if you open the test database read-only. This is described in some standby database docs, where the object is to have a standby database tracking production (managed recovery), then the recovery is cancelled and the db is brought up in read only mode for perusal, then resyncronized with the production database and put back into managed recovery.
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=70233.1 http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=146091.1 among others.

jg

--
@home.com is bogus.
http://www.canosoarus.com/07RocketBelt/Rocket01.htm