Re: Clarfication on reorg of critical dbspace...

How about restoring the rootdbs to a different location? Another thought: mirror the rootdbs, and then break the mirror. I don't like this suggestion so much as it makes the old original references dangling out in the ether forever. Hope these suggestions help. Brice Avila Minneapolis, Minnesota "Rajasekaran, Rajesh" <RRajasekaran@forestpharm.com> wrote in message news:<bg8jq6$qod$1@terabinaries.xmission.com>... > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01C3569F.0B53DCA0 > Content-Type: text/plain; > charset="iso-8859-1" > > Hello all, > > I have this requirement of moving the critical dbspace's data onto a > different physical device. I know the reorg. can be done for physdbs and > logdbs. Is there any way to reorg the Rootdbs ? Does Informix allow the > admin user to perform the reorg of rootdbs like any other dbspace ? > > Any suggestions are greatly appreciated. > > Rajesh Rajasekaran > Informix Database Administrator > Forest Pharmaceuticals Inc. > (314) 493-7073 > rrajasekaran@forestpharm.com > <SNIP>

"Brice Avila" <briceavila@hotmail.com> wrote in message news:c46e3ec5.0307301040.33fdfe@posting.google.com... > How about restoring the rootdbs to a different location? > > Another thought: mirror the rootdbs, and then break the mirror. I > don't like this suggestion so much as it makes the old original > references dangling out in the ether forever. > Not at all. Here's what you do. Assume that the rootdbs chunk is called rootbds, and is a link to /old_disk/rootdbs 1. Enable mirroring on your instance 2. Create a new chunk, rootdbs_m, link to /new_disk/rootdbs 3. Mirror rootdbs to rootdbs_m Shut the engine down, and reverse the links, so rootdbs -> /new_disk/rootdbs and rootdbs_m -> /old_disk/rootdbs 4. Start the instance 5. Drop the mirror on the root dbspace. All done!