database migration
A poster planned to move a 7.3 database to a new server and then upgrade to 9.2, by ontape level 0 backup and restore. Art S. Kagel warned this gives converted rather than native 9.2 tables and preferred dbexport and dbimport into a clean 9.21 engine. Ray Margarella said it should work if the machines are binary compatible, noting detached indexes use extra space after the 9.2 upgrade. Jay Konigsberg suggested HPL. No final choice.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello all
I've got a 7.3 db that is to be upgraded to 9.2 Before it is upgraded
though, it needs to be moved to a new server. Can I do this by
performing a full backup (ontape -s -L 0), from the old server and
restoring it on the new server (ensuring that all the links to the
chunks exist). The host name will be different.
Is there any flaws in my plan, or is there a better way to do it.
Sent via Deja.com http://www.deja.com/
Before you buy.
The only flaw is that you will get converted tables not native 9.2 tables
and there are differences. If you can it is better to dbexport your
databases, create a clean 9.21 engine on the new machine and dbimport them.
Art S. Kagel
gorgos@my-deja.com wrote:
>
> Hello all
> I've got a 7.3 db that is to be upgraded to 9.2 Before it is upgraded
> though, it needs to be moved to a new server. Can I do this by
> performing a full backup (ontape -s -L 0), from the old server and
> restoring it on the new server (ensuring that all the links to the
> chunks exist). The host name will be different.
>
> Is there any flaws in my plan, or is there a better way to do it.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
assuming the two machines are binary compatible -- sounds good. (The
sqlhosts file may need updating since the host is changing)
One thing I've noticed about the 9.2 upgrade is that all indexes are created
as "detached" ---> or placed in their own extent by default. This can
consume your disk space at a suprising rate. All the orginal extent sizes
are sized to contain both data and indexes --- now you have a separate
extent for both data and indexes...
<gorgos@my-deja.com> wrote in message news:8qai85$nmc$1@nnrp1.deja.com...
> Hello all
> I've got a 7.3 db that is to be upgraded to 9.2 Before it is upgraded
> though, it needs to be moved to a new server. Can I do this by
> performing a full backup (ontape -s -L 0), from the old server and
> restoring it on the new server (ensuring that all the links to the
> chunks exist). The host name will be different.
>
> Is there any flaws in my plan, or is there a better way to do it.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
You might consider using NFS to mount some hard drives and the unload/load
with the High Performance Loader. Its a bit buggy and need a fair amount of
hand-holding, but is pertty quick.
<gorgos@my-deja.com> wrote in message news:8qai85$nmc$1@nnrp1.deja.com...
> Hello all
> I've got a 7.3 db that is to be upgraded to 9.2 Before it is upgraded
> though, it needs to be moved to a new server. Can I do this by
> performing a full backup (ontape -s -L 0), from the old server and
> restoring it on the new server (ensuring that all the links to the
> chunks exist). The host name will be different.
>
> Is there any flaws in my plan, or is there a better way to do it.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.