Re: Migration of Data
Catalin
I agree with your answer but why do the databases need to have logging?
It seems it would be better to turnoff logging on both databases for the
transfer.
No out of locks or filling up logical logs issues plus I would think it was
faster.
=====================================================================
Paul Watje Database Something or Another
watjep@hasting.com Hastings Books, Music, & Video
----------
From: ilist
To: informix-list
Subject: Re: Migration of Data
Date: Monday, April 24, 1995 1:39PM
dproksch@vrx.vhi.com wrote:
: We are in the processing of moving from a Pyramid ES to a Pyramid NILE
: computer, as well as going from 5.x to 7.10. Inorder to pull this
: off, I need to unload/load all the data. Does anyone have any
: suggestions (other than praying a lot) on how to pull this off
: in a relatively timely manner? Previous migrations at this company
: have involved unloading to a named pipe, some smoke and mirrors
: I don't quite understand, then reading from another named pipe
: and then feeding load or dbload. Is there a way write to a socket
: and read from the socket and then feed load/dbload? I am going to
: move ~50GB of data.
Why don't you keep it simple by using the power of Informix Star
(now included in 6.0 and 7.1):
1. Recreate your database on your new server (dbschema).
2. Define entries in the sqlhosts, services, etc... for both
servers (old/new)
3. dbaccess and connect to your old server.
4. For each table use:
insert into your-db@newserver:tablename
select * from tablename
Note: step 4 can be an easily generated script.
Caveats:
Databases must have logging.
Tested between 6.x and 7.x. (Have not tried it with 5.x, though
it shouldn't be any different)
Catalin