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 [email]rrajasekaran@forestpharm.com[/email] -----Original Message----- From: Neil Truby [mailto:neil.truby@ardenta.com] Sent: Wednesday, July 30, 2003 2:57 PM To: [email]informix-list@iiug.org[/email] Subject: Re: Clarfication on reorg of critical dbspace... "Brice Avila" wrote in message news:c46e3ec5.0307301040.33fdfe@posting.google.com...[quote] > 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. >[/quote] 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 RE: Clarfication on reorg of critical dbspace...

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: [email]informix-list@iiug.org[/email]
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: [email]informix-list@iiug.org[/email]
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-- sending to informix-list [allowsmilie] => 1 [showsignature] => 0 [ipaddress] => [iconid] => 0 [visible] => 1 [attach] => 0 [infraction] => 0 [reportthreadid] => 0 [isusenetpost] => 1 [msgid] => [ref] => [htmlstate] => on_nl2br [postusername] => Rajasekaran, Rajesh [ip] => RRajasekaran@fo [isdeleted] => 0 [usergroupid] => [membergroupids] => [displaygroupid] => [password] => [passworddate] => [email] => [styleid] => [parentemail] => [homepage] => [icq] => [aim] => [yahoo] => [msn] => [skype] => [showvbcode] => [showbirthday] => [usertitle] => [customtitle] => [joindate] => [daysprune] => [lastvisit] => [lastactivity] => [lastpost] => [lastpostid] => [posts] => [reputation] => [reputationlevelid] => [timezoneoffset] => [pmpopup] => [avatarid] => [avatarrevision] => [profilepicrevision] => [sigpicrevision] => [options] => [akvbghsfs_optionsfield] => [birthday] => [birthday_search] => [maxposts] => [startofweek] => [referrerid] => [languageid] => [emailstamp] => [threadedmode] => [autosubscribe] => [pmtotal] => [pmunread] => [salt] => [ipoints] => [infractions] => [warnings] => [infractiongroupids] => [infractiongroupid] => [adminoptions] => [profilevisits] => [friendcount] => [friendreqcount] => [vmunreadcount] => [vmmoderatedcount] => [socgroupinvitecount] => [socgroupreqcount] => [pcunreadcount] => [pcmoderatedcount] => [gmmoderatedcount] => [assetposthash] => [fbuserid] => [fbjoindate] => [fbname] => [logintype] => [fbaccesstoken] => [newrepcount] => [vbseo_likes_in] => [vbseo_likes_out] => [vbseo_likes_unread] => [temp] => [field1] => [field2] => [field3] => [field4] => [field5] => [subfolders] => [pmfolders] => [buddylist] => [ignorelist] => [signature] => [searchprefs] => [rank] => [icontitle] => [iconpath] => [avatarpath] => [hascustomavatar] => 0 [avatardateline] => [avwidth] => [avheight] => [edit_userid] => [edit_username] => [edit_dateline] => [edit_reason] => [hashistory] => [pagetext_html] => [hasimages] => [signatureparsed] => [sighasimages] => [sigpic] => [sigpicdateline] => [sigpicwidth] => [sigpicheight] => [postcount] => 6 [islastshown] => 1 [isfirstshown] => [attachments] => [allattachments] => ) --> Clarfication on reorg of critical dbspace... - Informix

Clarfication on reorg of critical dbspace... - 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_01C3569F.0B53DCA0 Content-Type: text/plain; cht="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 [email]rrajasekaranforestpharm.com[/email] ------_=_NextPart_001_01C3569F.0B53DCA0 ...

  1. #1

    Default Clarfication on reorg of critical dbspace...


    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;
    cht="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
    [email]rrajasekaranforestpharm.com[/email]


    ------_=_NextPart_001_01C3569F.0B53DCA0
    Content-Type: text/html;
    cht="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; =
    cht=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&nbsp; 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">rrajasekaranforestpharm.com</FONT></U></B>
    </P>

    </BODY>
    </HTML>
    ------_=_NextPart_001_01C3569F.0B53DCA0--
    sending to informix-list
    Rajasekaran, Rajesh Guest

  2. #2

    Default 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" <RRajasekaranforestpharm.com> wrote in message news:<bg8jq6$qod$1terabinaries.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;
    > cht="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
    > [email]rrajasekaranforestpharm.com[/email]
    >
    <SNIP>
    Brice Avila Guest

  3. #3

    Default 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;
    > cht="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
    > [email]rrajasekaranforestpharm.com[/email]
    >
    >
    > ------_=_NextPart_001_01C3569F.0B53DCA0 Content-Type: text/html;
    > cht="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; =
    > cht=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&nbsp; 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">rrajasekaranforestpharm.com</FONT></U></B> </P>
    >
    > </BODY>
    > </HTML>
    > ------_=_NextPart_001_01C3569F.0B53DCA0-- sending to informix-list
    Art S. Kagel Guest

  4. #4

    Default Re: Clarfication on reorg of critical dbspace...

    "Art S. Kagel" <kagelbloomberg.net> wrote in message
    news:pan.2003.07.30.15.25.31.506842.15473bloomber g.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.


    Neil Truby Guest

  5. #5

    Default RE: Clarfication on reorg of critical dbspace...


    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_01C356D6.A0C34E10
    Content-Type: text/plain;
    cht="iso-8859-1"

    Hi,

    Thanks. But u know what our layout will still have one more issue with this.
    Since we use offsets in our chunk distribution, like the sample layout
    explained below

    /informix/PRD/sapdata/physdev1/data1 --:> /dev/vx/rdsk/sapdg1/infdbv001 -- >
    rootdbs of size 100 MB (different offset)
    /informix/PRD/sapdata/physdev1/data1 --:> /dev/vx/rdsk/sapdg1/infdbv001 --
    > datadbs of size 1.5 GB (another offset)
    Even if i restore to a different physical location, the new INFDBV volume
    does have the datadbs data due to a single volume distributed across
    multiple chunks. The new volume which will be having is on RAID1 and out
    datadbs will be on RAID 5.


    We are trying to upgrade our storage and the whole box. Iam defining all the
    Informix volumes on the new storage array with RAID5 layout for our DB data.
    But for the critical dbspace, iam created the Informix volumes on the
    internal disks and not on the storage array with RAID1 layout. With this in
    mind, I have a question regarding the DB Mirroring option to resolve the
    issue.

    Once i restore the data (everything will go to new array), i define DB
    mirroring for critical dbspaces to another location say RAID1 disks. After
    mirroring is done, if i reassign my mirror path as primary path and take out
    mirror path in the onconfig, Will that work without any issues ? Does the
    system catalog still contain the old primary path somewhere ?

    Thanks


    Rajesh Rajasekaran
    Informix Database Administrator
    Forest Pharmaceuticals Inc.
    (314) 493-7073
    [email]rrajasekaranforestpharm.com[/email]


    -----Original Message-----
    From: [email]briceavilahotmail.com[/email] [mailto:briceavilahotmail.com]
    Sent: Wednesday, July 30, 2003 1:40 PM
    To: [email]informix-listiiug.org[/email]
    Subject: 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" <RRajasekaranforestpharm.com> wrote in message
    news:<bg8jq6$qod$1terabinaries.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;
    > cht="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
    > [email]rrajasekaranforestpharm.com[/email]
    >
    <SNIP>

    ------_=_NextPart_001_01C356D6.A0C34E10
    Content-Type: text/html;
    cht="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; =
    cht=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>

    <P><FONT SIZE=3D2>Hi,&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
    </P>

    <P><FONT SIZE=3D2>Thanks. But u know what our layout will still have =
    one more issue with this.</FONT>
    <BR><FONT SIZE=3D2>Since we use offsets in our chunk distribution, like =
    the sample layout explained below</FONT>
    </P>

    <P><FONT SIZE=3D2>/informix/PRD/sapdata/physdev1/data1 --:&gt; =
    /dev/vx/rdsk/sapdg1/infdbv001 -- &gt; rootdbs&nbsp; of size 100 MB =
    (different offset)</FONT>
    <BR><FONT SIZE=3D2>&nbsp;/informix/PRD/sapdata/physdev1/data1 --:&gt; =
    /dev/vx/rdsk/sapdg1/infdbv001 -- &gt; datadbs&nbsp; of size&nbsp; 1.5 =
    GB (another offset)</FONT>
    </P>

    <P><FONT SIZE=3D2>Even if i restore to a different physical location, =
    the new INFDBV volume does have the datadbs data due to a single volume =
    distributed across multiple chunks. The new volume which will be having =
    is on RAID1 and out datadbs will be on RAID 5. </FONT></P>
    <BR>

    <P><FONT SIZE=3D2>We are trying to upgrade our storage and the whole =
    box. Iam defining all the Informix volumes on the new storage array =
    with RAID5 layout for our DB data. But for the critical dbspace, iam =
    created the Informix volumes on the internal disks and not on the =
    storage array with RAID1 layout. With this in mind,&nbsp; I have a =
    question regarding the DB Mirroring option to resolve the =
    issue.</FONT></P>

    <P><FONT SIZE=3D2>Once i restore the data (everything will go to new =
    array), i define DB mirroring for critical dbspaces to another location =
    say RAID1 disks. After mirroring is done, if i reassign my mirror path =
    as primary path and take out mirror path&nbsp; in the onconfig, Will =
    that work without any issues ? Does the system catalog still contain =
    the old primary path somewhere ?</FONT></P>

    <P><FONT SIZE=3D2>Thanks</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>Rajesh Rajasekaran</FONT>
    <BR><FONT SIZE=3D2>Informix Database Administrator</FONT>
    <BR><FONT SIZE=3D2>Forest Pharmaceuticals Inc.</FONT>
    <BR><FONT SIZE=3D2>(314) 493-7073</FONT>
    <BR><FONT SIZE=3D2>rrajasekaranforestpharm.com</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>-----Original Message-----</FONT>
    <BR><FONT SIZE=3D2>From: [email]briceavilahotmail.com[/email] [<A =
    HREF=3D"mailto:briceavilahotmail.com">mailto:bric eavilahotmail.com</A>=
    ]</FONT>
    <BR><FONT SIZE=3D2>Sent: Wednesday, July 30, 2003 1:40 PM</FONT>
    <BR><FONT SIZE=3D2>To: [email]informix-listiiug.org[/email]</FONT>
    <BR><FONT SIZE=3D2>Subject: Re: Clarfication on reorg of critical =
    dbspace...</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>How about restoring the rootdbs to a different =
    location?</FONT>
    </P>

    <P><FONT SIZE=3D2>Another thought: mirror the rootdbs, and then break =
    the mirror. I</FONT>
    <BR><FONT SIZE=3D2>don't like this suggestion so much as it makes the =
    old original</FONT>
    <BR><FONT SIZE=3D2>references dangling out in the ether forever.</FONT>
    </P>

    <P><FONT SIZE=3D2>Hope these suggestions help.</FONT>
    </P>

    <P><FONT SIZE=3D2>Brice Avila</FONT>
    <BR><FONT SIZE=3D2>Minneapolis, Minnesota</FONT>
    </P>

    <P><FONT SIZE=3D2>&quot;Rajasekaran, Rajesh&quot; =
    &lt;RRajasekaranforestpharm.com&gt; wrote in message =
    news:&lt;bg8jq6$qod$1terabinaries.xmission.com&gt ;...</FONT>
    <BR><FONT SIZE=3D2>&gt; This message is in MIME format. Since your mail =
    reader does not understand</FONT>
    <BR><FONT SIZE=3D2>&gt; this format, some or all of this message may =
    not be legible.</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    <BR><FONT SIZE=3D2>&gt; =
    ------_=3D_NextPart_001_01C3569F.0B53DCA0</FONT>
    <BR><FONT SIZE=3D2>&gt; Content-Type: text/plain;</FONT>
    <BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
    cht=3D&quot;iso-8859-1&quot;</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    <BR><FONT SIZE=3D2>&gt; Hello all,</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    <BR><FONT SIZE=3D2>&gt; I have this requirement of moving the critical =
    dbspace's data onto a</FONT>
    <BR><FONT SIZE=3D2>&gt; different physical device. I know the reorg. =
    can be done for physdbs and</FONT>
    <BR><FONT SIZE=3D2>&gt; logdbs. Is there any way to reorg the Rootdbs ? =
    Does Informix allow the</FONT>
    <BR><FONT SIZE=3D2>&gt; admin user to perform the&nbsp; reorg of =
    rootdbs like any other dbspace ?</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    <BR><FONT SIZE=3D2>&gt; Any suggestions are greatly appreciated.</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    <BR><FONT SIZE=3D2>&gt; Rajesh Rajasekaran</FONT>
    <BR><FONT SIZE=3D2>&gt; Informix Database Administrator</FONT>
    <BR><FONT SIZE=3D2>&gt; Forest Pharmaceuticals Inc.</FONT>
    <BR><FONT SIZE=3D2>&gt; (314) 493-7073</FONT>
    <BR><FONT SIZE=3D2>&gt; [email]rrajasekaranforestpharm.com[/email]</FONT>
    <BR><FONT SIZE=3D2>&gt; </FONT>
    </P>

    <P><FONT SIZE=3D2>&lt;SNIP&gt;</FONT>
    </P>

    </BODY>
    </HTML>
    ------_=_NextPart_001_01C356D6.A0C34E10--
    sending to informix-list
    Rajasekaran, Rajesh Guest

  6. #6

    Default RE: Clarfication on reorg of critical dbspace...


    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;
    cht="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
    [email]rrajasekaranforestpharm.com[/email]


    -----Original Message-----
    From: Rajasekaran, Rajesh
    Sent: Thursday, July 31, 2003 7:56 AM
    To: 'Neil Truby'
    Cc: [email]informix-listiiug.org[/email]
    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
    [email]rrajasekaranforestpharm.com[/email]


    -----Original Message-----
    From: Neil Truby [mailto:neil.trubyardenta.com]
    Sent: Wednesday, July 30, 2003 2:57 PM
    To: [email]informix-listiiug.org[/email]
    Subject: Re: Clarfication on reorg of critical dbspace...


    "Brice Avila" <briceavilahotmail.com> wrote in message
    news:c46e3ec5.0307301040.33fdfeposting.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;
    cht="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; =
    cht=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>

    <P><FONT SIZE=3D2>Neil,</FONT>
    </P>

    <P><FONT SIZE=3D2>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 ? </FONT></P>

    <P><FONT SIZE=3D2>Rajesh Rajasekaran</FONT>
    <BR><FONT SIZE=3D2>Informix Database Administrator</FONT>
    <BR><FONT SIZE=3D2>Forest Pharmaceuticals Inc.</FONT>
    <BR><FONT SIZE=3D2>(314) 493-7073</FONT>
    <BR><FONT SIZE=3D2>rrajasekaranforestpharm.com</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>-----Original Message-----</FONT>
    <BR><FONT SIZE=3D2>From: Rajasekaran, Rajesh </FONT>
    <BR><FONT SIZE=3D2>Sent: Thursday, July 31, 2003 7:56 AM</FONT>
    <BR><FONT SIZE=3D2>To: 'Neil Truby'</FONT>
    <BR><FONT SIZE=3D2>Cc: [email]informix-listiiug.org[/email]</FONT>
    <BR><FONT SIZE=3D2>Subject: RE: Clarfication on reorg of critical =
    dbspace...</FONT>
    <BR><FONT SIZE=3D2>Importance: High</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>Hi,</FONT>
    </P>

    <P><FONT SIZE=3D2>&nbsp;&nbsp; Thanks for your response. I have some =
    issue when i tried to implement yr solution. </FONT>
    </P>

    <P><FONT SIZE=3D2>&nbsp; After&nbsp; 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.</FONT></P>

    <P><FONT SIZE=3D2>&nbsp; When i started the engine, it reports i/o =
    error on both the chunks &quot;cannot open chunk&quot; etc. for some =
    reason.</FONT>
    <BR><FONT SIZE=3D2>&nbsp; When i swapped back to original setup, i mean =
    relocated the links back to earlier setup, and started the DB and it =
    worked fine. </FONT></P>

    <P><FONT SIZE=3D2>Original setup</FONT>
    </P>

    <P><FONT SIZE=3D2>&nbsp;/informix/PRD/sapdata/physdev5/data8 --&gt; =
    INFDBV040(physical device for PRIMARY chunk)</FONT>
    <BR><FONT SIZE=3D2>&nbsp;/informix/PRD/sapdata/physdev26/data4 --&gt; =
    INFDBV254( physical device for MIRRORED chunk)</FONT>
    </P>

    <P><FONT SIZE=3D2>After swapping as you suggested </FONT>
    <BR><FONT SIZE=3D2>&nbsp;/informix/PRD/sapdata/physdev5/data8 --&gt; =
    INFDBV254(physical device for PRIMARY chunk)</FONT>
    <BR><FONT SIZE=3D2>&nbsp;/informix/PRD/sapdata/physdev26/data4 --&gt; =
    INFDBV040(physical device for MIRRORED chunk)</FONT>
    <BR><FONT SIZE=3D2>Here is where i have the database initialization =
    failure saying &quot;cannot open chunk:&quot; for both the =
    chunks.</FONT>
    </P>

    <P><FONT SIZE=3D2>My question is</FONT>
    </P>

    <P><FONT SIZE=3D2>&nbsp;1) Doesnt the reserved pages have the info of =
    the original primary path and Mirror path&nbsp; ? Hence when i swap, it =
    reports errors ?</FONT></P>

    <P><FONT SIZE=3D2>&nbsp;</FONT>
    </P>

    <P><FONT SIZE=3D2>Any suggestions/comments are appreciated.</FONT>
    </P>

    <P><FONT SIZE=3D2>Rajesh Rajasekaran</FONT>
    <BR><FONT SIZE=3D2>Informix Database Administrator</FONT>
    <BR><FONT SIZE=3D2>Forest Pharmaceuticals Inc.</FONT>
    <BR><FONT SIZE=3D2>(314) 493-7073</FONT>
    <BR><FONT SIZE=3D2>rrajasekaranforestpharm.com</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>-----Original Message-----</FONT>
    <BR><FONT SIZE=3D2>From: Neil Truby [<A =
    HREF=3D"mailto:neil.trubyardenta.com">mailto:neil .trubyardenta.com</A>=
    ]</FONT>
    <BR><FONT SIZE=3D2>Sent: Wednesday, July 30, 2003 2:57 PM</FONT>
    <BR><FONT SIZE=3D2>To: [email]informix-listiiug.org[/email]</FONT>
    <BR><FONT SIZE=3D2>Subject: Re: Clarfication on reorg of critical =
    dbspace...</FONT>
    </P>
    <BR>

    <P><FONT SIZE=3D2>&quot;Brice Avila&quot; =
    &lt;briceavilahotmail.com&gt; wrote in message</FONT>
    <BR><FONT SIZE=3D2><A =
    HREF=3D"news:c46e3ec5.0307301040.33fdfeposting.go ogle.com" =
    TARGET=3D"_blank">news:c46e3ec5.0307301040.33fdfe posting.google.com</A>=
    ....</FONT>
    <BR><FONT SIZE=3D2>&gt; How about restoring the rootdbs to a different =
    location?</FONT>
    <BR><FONT SIZE=3D2>&gt;</FONT>
    <BR><FONT SIZE=3D2>&gt; Another thought: mirror the rootdbs, and then =
    break the mirror. I</FONT>
    <BR><FONT SIZE=3D2>&gt; don't like this suggestion so much as it makes =
    the old original</FONT>
    <BR><FONT SIZE=3D2>&gt; references dangling out in the ether =
    forever.</FONT>
    <BR><FONT SIZE=3D2>&gt;</FONT>
    </P>

    <P><FONT SIZE=3D2>Not at all.</FONT>
    <BR><FONT SIZE=3D2>Here's what you do.</FONT>
    </P>

    <P><FONT SIZE=3D2>Assume that the rootdbs chunk is called rootbds, and =
    is a link to</FONT>
    <BR><FONT SIZE=3D2>/old_disk/rootdbs</FONT>
    </P>

    <P><FONT SIZE=3D2>1. Enable mirroring on your instance</FONT>
    <BR><FONT SIZE=3D2>2. Create a new chunk, rootdbs_m, link to =
    /new_disk/rootdbs</FONT>
    <BR><FONT SIZE=3D2>3. Mirror rootdbs to rootdbs_m</FONT>
    </P>

    <P><FONT SIZE=3D2>Shut the engine down, and reverse the links, so =
    rootdbs -&gt; /new_disk/rootdbs</FONT>
    <BR><FONT SIZE=3D2>and rootdbs_m -&gt; /old_disk/rootdbs</FONT>
    </P>

    <P><FONT SIZE=3D2>4. Start the instance</FONT>
    <BR><FONT SIZE=3D2>5. Drop the mirror on the root dbspace.</FONT>
    </P>

    <P><FONT SIZE=3D2>All done!</FONT>
    </P>

    </BODY>
    </HTML>
    ------_=_NextPart_001_01C35763.DC3E8710--
    sending to informix-list
    Rajasekaran, Rajesh Guest

Similar Threads

  1. big dbspace
    By Gokusan in forum Informix
    Replies: 2
    Last Post: October 10th, 02:02 PM
  2. break one dbspace in to two dbspace
    By hiten.bhawsar in forum Informix
    Replies: 6
    Last Post: October 2nd, 11:55 AM
  3. index length and reorg - help need
    By filler in forum IBM DB2
    Replies: 0
    Last Post: September 10th, 09:19 AM
  4. Replies: 1
    Last Post: September 9th, 02:36 PM
  5. Difference between Reorg e consistency check
    By Stefano in forum IBM DB2
    Replies: 0
    Last Post: July 22nd, 10:05 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •