BaaN and High Perf Loader
I've heard that the reason you shouldn't use the Informix tools to load and unload databases in BaaN (we've purchased a new server and are looking to quickly transfer data) is because of the hash columns. Someone from Informix told me that the pipe delimiter might be a value in the hash column and then during the reload, you'd get your data all broken. Is there a delimiter charachter that would never show up in a hash column? Or is there a better way to do this? Jon Freeland<*> DBA Miller Industries, Inc. jon@millerind.com eclypse@babylon5.cdc.net
In article <18354681B203D01A.D0BB7FF55ACF473B.68E15B36F1ED481D@library-
proxy.airnews.net>, -=Eclypse=- <eclypse@cdc.net> writes
>I've heard that the reason you shouldn't use the Informix tools to
>load and unload databases in BaaN (we've purchased a new server and
>are looking to quickly transfer data) is because of the hash columns.
>Someone from Informix told me that the pipe delimiter might be a
>value in the hash column and then during the reload, you'd get your
>data all broken. Is there a delimiter charachter that would never
>show up in a hash column? Or is there a better way to do this?
>
??? Shouldn't be a problem, but you can always use onload/onunload to
do binary loads/unloads.
>Jon Freeland<*>
>DBA
>Miller Industries, Inc.
>jon@millerind.com
>eclypse@babylon5.cdc.net
--
David Williams
-=Eclypse=- wrote:
>
> I've heard that the reason you shouldn't use the Informix tools to
> load and unload databases in BaaN (we've purchased a new server and
> are looking to quickly transfer data) is because of the hash columns.
> Someone from Informix told me that the pipe delimiter might be a
> value in the hash column and then during the reload, you'd get your
> data all broken. Is there a delimiter charachter that would never
> show up in a hash column? Or is there a better way to do this?
>
> Jon Freeland<*>
> DBA
> Miller Industries, Inc.
> jon@millerind.com
> eclypse@babylon5.cdc.net
Hi,
have you ever asked, why it is neccessary to first unload the
data to disk and then load it again from the disk ? If you
want to use Informix tools, use the capability of distributed
queries. i.e.
insert into ttfgld410401 select * from baandb@oldserver:ttfgld410401;
If you don't want to enter this statement manually, try this
query in you old environment.
dbaccess baandb - <<eof
unload to "copy.sql" delimiter ";"select "insert into " || trim(tabname) ||
"select * from baandb@" || trim(sitename) || ":" || trim(tabname)
from systables where tabid >= 100;
eof
This query will generate a SQL script that contains all
insert statements. Copy the script to your new environment
and run it from dbaccess. It's the fastest way to copy the
Baan data to a new environment. ( Don't forget to turn logging
off on both servers, before you start the script. )
Best regards,
Stefan Weideneder
Stefan Weideneder wrote:
[SNIP]
> have you ever asked, why it is neccessary to first unload the
> data to disk and then load it again from the disk ? If you
> want to use Informix tools, use the capability of distributed
> queries. i.e.
>
> insert into ttfgld410401 select * from baandb@oldserver:ttfgld410401;>
> If you don't want to enter this statement manually, try this
> query in you old environment.
>
> dbaccess baandb - <<eof
>
> unload to "copy.sql" delimiter ";"> select "insert into " || trim(tabname) ||
> "select * from baandb@" || trim(sitename) || ":" || trim(tabname)
> from systables where tabid >= 100;
>
> eof
>
> This query will generate a SQL script that contains all
> insert statements. Copy the script to your new environment
> and run it from dbaccess. It's the fastest way to copy the
> Baan data to a new environment. ( Don't forget to turn logging
> off on both servers, before you start the script. )
Actually my dbcopy is a bit faster.
Art S. Kagel