Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Gary Quiring — — source: Usenet: comp.databases.informix
On 18 Oct 2005 01:24:33 -0700, mccmx@hotmail.com wrote:
>Funnily enough, your idea to create a soft link in /dev from the old
>device to the new device/location is exactly what I was planning to do
>if I couldn't find a 'better' solution.
>
>Based on this thread, I may well have to go down that route...
>
>My Informix knowledge is very limited....!?!
>
>What I will probably do is:
>
>1. create the soft link from /dev to get informix up and running on a
>different machine.
>2. On this new machine: Add a mirror chunk to each dbspace and drop
>the original mirror to effectively relocate the databse to the
>filesystem.
>
>If I have no joy with step 2, I will run with the soft link from /dev.
>
>This will have to be documented well so that if someone destroys /dev
>(through devfsadm or similar) then the links can be recreated easily.
>Its not ideal but its preferable to unloading and reloading the whole
>database, which has its own risks.
>
>Thanks for the advice..
>
>Matt
If you just want to move the data from box a to box b why not use Art's dbcopy
and copy the data? I have done this several times over a weekend with a 150gig
DB. His utility makes it very easy. Also download his myschema utility which
will allow you to size the DB during the copy for a better setup. With this
method there is no risk to the source. I use about 30 simultanous dbcopies for
better performance. When you create the DB on the new server don't make the
indexes or stored procedures. Leave them for last after you copy the data.
Gary Quiring
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.