Re: Database Migration
Thanks all for your help...I have opted to use onbar and rename the
chunks...I have an chance to test it before the live implementation so
fingers crossed!
"Madison Pruet" <mpruet@comcast.net> wrote in message
news:A6f6d.124029$MQ5.113221@attbi_s52...
> Why can't you do a redirected restore?
> also -- don't count out HPL.
>
>
> "Howard Jones" <howie_lfc@hotmail.com> wrote in message
> news:QMb6d.562$_V.161@newsfe6-gui.ntli.net...
> > IDS9.40.FC4
> > HPUX 11.0
> > Database size 200Gb
> >
> > Hello all,
> >
> > I am about to migrate a database to a larger server and was wondering
> which
> > method is recommended.
> >
> > The easiest method I guess is to use a level 0 archive which would mean
> the
> > same structure between the two servers which the Unix guys building the
> > system are against.
> >
> > dbexport I fear would take too long, as would need to be done to tape
> (size
> > restrictions of system)
> >
> > Which leaves onunload/onload....This is just a data unload and a schema
of
> > the whole database would need to be taken prior to onunload running (is
> this
> > right?)
> > Is this the same as dbexport where the chunk raw-logical-volumes names
and
> > sizes do not need to be as the original machine.
> > Has anyone out there got an easy explanation of the process involved
when
> > using onunload/onload?
> >
> > Cheers,
> >
> > Howard
> >
> >
>
>