Re: Clarfication on reorg of critical dbspace...
On Wed, 30 Jul 2003 09:32:38 -0400, Rajasekaran, Rajesh wrote: The only way is to shutdown the engine, dd the entire contents of the root chunk to the new device, change the link that the engine uses to access the chunk (you did use symlinks for chunkpaths right?) to point to the new root chunk, and restart the engine. Or to so an archive and restore relinking between similar to above. Art S. Kagel > 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 > > > ------_=_NextPart_001_01C3569F.0B53DCA0 Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3Diso-8859-1"> > <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = > 5.5.2653.12"> > <TITLE>Clarfication on reorg of critical dbspace...</TITLE> </HEAD> > <BODY> > > <P><FONT SIZE=3D2 FACE=3D"Times New Roman">Hello all,</FONT> </P> > > <P><FONT SIZE=3D2 FACE=3D"Times New Roman">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 ?</FONT></P> > > <P><FONT SIZE=3D2 FACE=3D"Times New Roman">Any suggestions are greatly = > appreciated.</FONT> > </P> > > <P><B><FONT COLOR=3D"#000000" FACE=3D"Verdana">Rajesh = > Rajasekaran</FONT></B> > <BR><B><FONT COLOR=3D"#000000" FACE=3D"Verdana">Informix Database = > Administrator</FONT></B> > <BR><B><FONT COLOR=3D"#000000" FACE=3D"Verdana">Forest Pharmaceuticals = > Inc.</FONT></B> > <BR><B><FONT COLOR=3D"#000000" FACE=3D"Verdana">(314) = > 493-7073</FONT></B> > <BR><B><U><FONT COLOR=3D"#000000" = > FACE=3D"Verdana">rrajasekaran@forestpharm.com</FONT></U></B> </P> > > </BODY> > </HTML> > ------_=_NextPart_001_01C3569F.0B53DCA0-- sending to informix-list
"Art S. Kagel" <kagel@bloomberg.net> wrote in message news:pan.2003.07.30.15.25.31.506842.15473@bloomberg.net... > On Wed, 30 Jul 2003 09:32:38 -0400, Rajasekaran, Rajesh wrote: > > The only way is to shutdown the engine, dd the entire contents of the > root chunk to the new device, change the link that the engine uses to > access the chunk (you did use symlinks for chunkpaths right?) to point to > the new root chunk, and restart the engine. Or to so an archive and > restore relinking between similar to above. or ... (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.