RE: Clarfication on reorg of critical dbspace...

Posted in 2003

Rajasekaran, Rajesh — Thu, 31 Jul 2003 08:01:30 -0500 — source: Usenet: comp.databases.informix

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_01C35763.DC3E8710 Content-Type: text/plain; charset="iso-8859-1" Neil, Also, i would like to add on some more info here. I have given my offset start at a different place for the Mirrored volume on this chunk at first place. Could this cause the issue when i relocate the links ? Rajesh Rajasekaran Informix Database Administrator Forest Pharmaceuticals Inc. (314) 493-7073 rrajasekaran@forestpharm.com -----Original Message----- From: Rajasekaran, Rajesh Sent: Thursday, July 31, 2003 7:56 AM To: 'Neil Truby' Cc: informix-list@iiug.org Subject: RE: Clarfication on reorg of critical dbspace... Importance: High Hi, Thanks for your response. I have some issue when i tried to implement yr solution. After mirroring the data, i did the database shutdown. Relocated the links as you suggested. After this, primary path becomes mirror path and vice versa as explained below. When i started the engine, it reports i/o error on both the chunks "cannot open chunk" etc. for some reason. When i swapped back to original setup, i mean relocated the links back to earlier setup, and started the DB and it worked fine. Original setup /informix/PRD/sapdata/physdev5/data8 --> INFDBV040(physical device for PRIMARY chunk) /informix/PRD/sapdata/physdev26/data4 --> INFDBV254( physical device for MIRRORED chunk) After swapping as you suggested /informix/PRD/sapdata/physdev5/data8 --> INFDBV254(physical device for PRIMARY chunk) /informix/PRD/sapdata/physdev26/data4 --> INFDBV040(physical device for MIRRORED chunk) Here is where i have the database initialization failure saying "cannot open chunk:" for both the chunks. My question is 1) Doesnt the reserved pages have the info of the original primary path and Mirror path ? Hence when i swap, it reports errors ? Any suggestions/comments are appreciated. Rajesh Rajasekaran Informix Database Administrator Forest Pharmaceuticals Inc. (314) 493-7073 rrajasekaran@forestpharm.com -----Original Message----- From: Neil Truby [mailto:neil.truby@ardenta.com] Sent: Wednesday, July 30, 2003 2:57 PM To: informix-list@iiug.org Subject: Re: Clarfication on reorg of critical dbspace... "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! ------_=_NextPart_001_01C35763.DC3E8710 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>RE: Clarfication on reorg of critical dbspace...</TITLE> </HEAD> <BODY> Neil, Also, i would like to add on some more info here. I = have given my offset start at a different place for the Mirrored volume = on this chunk at first place. Could this cause the issue when i = relocate the links ? Rajesh Rajasekaran Informix Database Administrator Forest Pharmaceuticals Inc. (314) 493-7073 rrajasekaran@forestpharm.com -----Original Message----- From: Rajasekaran, Rajesh Sent: Thursday, July 31, 2003 7:56 AM To: 'Neil Truby' Cc: informix-list@iiug.org Subject: RE: Clarfication on reorg of critical = dbspace... Importance: High Hi,    Thanks for your response. I have some = issue when i tried to implement yr solution.   After  mirroring the data, i did the = database shutdown. Relocated the links as you suggested. After this, = primary path becomes mirror path and vice versa as explained = below.   When i started the engine, it reports i/o = error on both the chunks "cannot open chunk" etc. for some = reason.   When i swapped back to original setup, i mean = relocated the links back to earlier setup, and started the DB and it = worked fine. Original setup  /informix/PRD/sapdata/physdev5/data8 --> = INFDBV040(physical device for PRIMARY chunk)  /informix/PRD/sapdata/physdev26/data4 --> = INFDBV254( physical device for MIRRORED chunk) After swapping as you suggested  /informix/PRD/sapdata/physdev5/data8 --> = INFDBV254(physical device for PRIMARY chunk)  /informix/PRD/sapdata/physdev26/data4 --> = INFDBV040(physical device for MIRRORED chunk) Here is where i have the database initialization = failure saying "cannot open chunk:" for both the = chunks. My question is  1) Doesnt the reserved pages have the info of = the original primary path and Mirror path  ? Hence when i swap, it = reports errors ?   Any suggestions/comments are appreciated. Rajesh Rajasekaran Informix Database Administrator Forest Pharmaceuticals Inc. (314) 493-7073 rrajasekaran@forestpharm.com -----Original Message----- From: Neil Truby [<A = HREF=3D"mailto:neil.truby@ardenta.com">mailto:neil.truby@ardenta.com</A>= ] <FONT

RE: Clarfication on reorg of critical dbspace...

Related threads

Your privacy choices