The standby database method works until U open it. You can copy a database to
another machine. You can apply logs to it from the production. But once
opened the relationship between the two is severed. I presently refresh
database by copying, applying logs and recovering but once the copy is
opened you can not apply any more logs.
What I am looking for and I think Mike is is a way to constantly apply the
changes from the production to the devlopment system at regular intervals
without having to recopy the entire database (which I do now, or you have to
with an import) and being able to open and use the test database ( which you
cannot do with a standby database)
Mike Taylor wrote:
> We have wo databases, one for LIVE transactions and the other for
> testing/training, hence called TEST.
>
> I would like produce a script for updating the TEST database with all the
> transactions currently in the LIVE database.
>
> Note : The TEST database will be inactive at the time the copy is
> performed.
>
> How best can this be achieved ?