Re: Must service be stopped to migrate database ?

Hi,

If you want a fully synchronized copy of your database to another server/location, without having long downtime, you might want to do following:

1. make a hotbackup of your database
2. restore/copy the backed files to new location/server
3. open the backed database in mount mode (if you have files in different directories, you have to use alter database rename file first)
4. copy all archive logs from source to target
5. recover database (apply all existing archives)
6. shutdown source db
7. copy last archive(s) and redolog(s), including current one over to target (check the sequence# from v$log and v$archived_log)
8. recover database (you have to manually specify the location of "current" and non-archived redologs, the archived logs should be automatically found if parameters are set correct)
9. open target db.

You might want to cycle steps 4-5 several times, depending on how many additional archivelogs are generated when recovering.

Tanel.

"j" <perseus_medusa_at_hotmail.com> wrote in message news:3e572b20$1_at_newsgate.hknet.com...
> Hi all ,
>
> I am wondering if I want to migrate database from one instance to
> another, must the service provided by the database (like web or
application)
> be stopped during the process in order to prevent transactions during
> migration ? As I always think that this may cause unsynchronized data
> between the replicated target database and the source database.
>
> If the above question make you confuse, then simply, I am asking if
> someone show me what's the usual practice / procedure of doing migration ?
>
> Thanks.
>
> Perseus
>
>
Received on Sun Feb 23 2003 - 10:41:20 CST