Re: Moving 10g from server to server.

On May 12, 1:17 am, sybra..._at_hccnet.nl wrote:
> Comments embedded
>
> RMAN is used for *physical* backup.

so, which tool you would use to do migration from one serve to the another?

> Evidently, you will end up with
> the *same* datafiles, which may be on a different *location* depending
> on the *set newname* commands you feed it, prior to the actual restore
> command

is it good or bad? is it efficient, once a one is moving a database from one pc to the another (abviously this new i more powerful with more memory, etc)
should I move the databse with RMAN, or rather create a new instance of the same database on the new server, create tablespaces on the new hard disk drives, assign more space for archivelog, etc, and then execute imp form expdmp previously taken? What is your opinion?

> >Question: what would be the most efficient way to move database
> >instance from one server the another knowing that disk allocations for
> >tablespaces, archivelogs, etc will be changes.
>
> It depends. If you are going to relocate data to different tablespaces
> or going to reduce or increase the # of datafiles ,

nope. the same tablespaces (however located on different drives like D: instead of C:) I am thinking about keeping thew same # of datafiles.

> export import, as
> RMAN is used for *physical* backup and restore. Please study the
> impact of the word *physical*.

I am reading Osborne's Oracle Database 10g - The Complete Reference, but did not get to that part yet. unfortunately.

> They will imoact database operation as in a normal situation.
? normal situation?

Sybrand, thank you for your respone. Received on Sat May 12 2007 - 01:13:01 CDT