Re: Best option for moving database of server

  • From: Oliver <ofabelo@xxxxxxxxx>
  • To: Martin Berger <martin.a.berger@xxxxxxxxx>
  • Date: Thu, 3 May 2012 14:29:58 +0100

It is all in local physical hard disks, it isn't a important database, it
is a testing environment for datawarehouse.
I ask about it because I'm not a dba, but I do things of dba :-) (I'm
sysadmin) I have many knowledge of Oracle (I think), but I'm not a expert.
Downtime is not a problem, but I like do the things well and quick, and I'm
asking to you the experts.
First thing that I will do is install oracle 10g (, install patchset (as source database) and I had thought read about cloning
Source database is in archive mode, but I don't know very well how to
recovery using rman backup, I've worked more with exp/imp or expdp/impdp.
Thanks beforehand.

2012/5/3 Martin Berger <martin.a.berger@xxxxxxxxx>

> Oliver,
> do you can share some informations about your storage infrastructure?
> Also an accepted downtime and size or your DB might influence  the
> decission.
> If it's a SAN, can you just detatch the LUNs from the old server and
> attach them to the new?
> the physical equivalent with built in disks would be removing the
> disks from old node and attaching them to new one?
> (I prefer the 'logical only' solution in a SAN, removing hardware is
> always somehow risky)
> Beside that a dataguard comes to my mind - so the new server is just a
> switchover away.
> other solutions are datapump over a DB link, ... do you need still more?
>  Martin
> On Thu, May 3, 2012 at 10:25 AM, Oliver <ofabelo@xxxxxxxxx> wrote:
> > Hi,
> > I have to move a oracle database 10g ( to another server, what
> > would you recommend me that is the best option for doing it? Cloning
> > database?
> > Architecture will be the same in the source and target server, different
> > distribution of Linux, but with same architecture (x86-64).
> > I had thought install oracle (I think that there isn't
> > full install), I will have to install patchset and then cloning
> > database :-?
> > I know transport tablespaces too ... and export/import. What would be the
> > best option? Database is not large/great, and it isn't a important
> > database, it can be stopped, although I don't want a large downtime.
> > Thanks beforehand.
> > P.D.: If you prefer cloning database, some manual about it?
> >
> > Cheers...
> >
> >
> > --
> >


Other related posts: