Changing the path of a chunk from onstat -d output.

Hi Hopefully this hasn't been covered before as I couldn't find the answer in google. We have certain naming standards here for chunk names on a given server. We base some scripted infrastructure around these standards. Unfortunately a chunk has been added to a server whereby the link pointing to the actual raw device has the wrong name, which is showing in the onstat output. This is causing glitches in some of our scripts. My question is, "Is it possible to update the fname field in syschunks, create the corrected link and they bounce the server? If this proves successful then remove the original incorrect link?". Has anyone tried this? The server version is 7.30 running on Solaris 2.8. Thanks for any help Regds Rob White -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. sending to informix-list

It probably is possible. But I wouldn't try it on a live system. And I'm brilliant .... Is the chunk very full? Would it not be better to move its contents, then drop and re-add the chunk with the correct name, if at all possible? "Robert White" <Robert.White@morganstanley.com> wrote in message news:bdv1tm$quh$1@terabinaries.xmission.com... > > Hi > > Hopefully this hasn't been covered before as I couldn't find the answer > in google. > > We have certain naming standards here for chunk names on a given server. > We base some scripted infrastructure around these standards. > Unfortunately a chunk has been added to a server whereby the link > pointing to the actual raw device has the wrong name, which is showing > in the onstat output. This is causing glitches in some of our scripts. > > My question is, "Is it possible to update the fname field in syschunks, > create the corrected link and they bounce the server? If this proves > successful then remove the original incorrect link?". > > Has anyone tried this? > > The server version is 7.30 running on Solaris 2.8. > > Thanks for any help > > Regds > > Rob White > > > > -- > NOTICE: If received in error, please destroy and notify sender. Sender > does not waive confidentiality or privilege, and use is prohibited. > > > sending to informix-list

I agree with Neil that it is probably possible, but I'd have my resume nice and pressed before attempting it. FWIW, do you know your version of IDS is obsolete? Brice Avila Minneapolis, Minnesota "Neil Truby" <neil.truby@ardenta.com> wrote in message news:<bdv69q$118v3p$1@ID-162943.news.dfncis.de>... > It probably is possible. > But I wouldn't try it on a live system. > And I'm brilliant .... > > Is the chunk very full? > Would it not be better to move its contents, then drop and re-add the chunk > with the correct name, if at all possible? > > "Robert White" <Robert.White@morganstanley.com> wrote in message > news:bdv1tm$quh$1@terabinaries.xmission.com... > > > > Hi > > > > Hopefully this hasn't been covered before as I couldn't find the answer > > in google. > > > > We have certain naming standards here for chunk names on a given server. > > We base some scripted infrastructure around these standards. > > Unfortunately a chunk has been added to a server whereby the link > > pointing to the actual raw device has the wrong name, which is showing > > in the onstat output. This is causing glitches in some of our scripts. > > > > My question is, "Is it possible to update the fname field in syschunks, > > create the corrected link and they bounce the server? If this proves > > successful then remove the original incorrect link?". > > > > Has anyone tried this? > > > > The server version is 7.30 running on Solaris 2.8. > > > > Thanks for any help > > > > Regds > > > > Rob White > > > > > > > > -- > > NOTICE: If received in error, please destroy and notify sender. Sender > > does not waive confidentiality or privilege, and use is prohibited. > > > > > > sending to informix-list