RE: Shared Memory Segments are not removed

The shared memory segments are marked to be deleted, but there are processes still attached to them. We have found the fastest way to remove them is to re-boot the system's. I have only seen this problem on HP-UX system's. Wayne E. Martin Informix Database Administrator Kmart Corp. -----Original Message----- From: Arshad, Shehla [mailto:SArshad@purolator.com] Sent: Wednesday, March 08, 2000 10:19 AM To: 'Obnoxio The Clown'; Arshad, Shehla; informix-list@iiug.org Subject: RE: Shared Memory Segments are not removed I did open up a case with Tech Support and they advised me post this problem on IIUG. I guess I am stuck!! > -----Original Message----- > From: Obnoxio The Clown [SMTP:obnoxio@hotmail.com] > Sent: Wednesday, March 08, 2000 9:37 AM > To: SArshad@purolator.com; informix-list@iiug.org > Subject: RE: Shared Memory Segments are not removed > > From: "Arshad, Shehla" <SArshad@purolator.com> > > > >Yes, we have tried ipcrm as root but that does not remove the segments. > >Unix > >complains that the segment id is invalid. That may be because the > instances > >have been marked as "to be removed" and the key of those segments looks > >like > >0x00000000. > > This does not sound even remotely good. Have you logged a case with Tech > Support? > > >No, we run onmode -ky once. Do you mean that running onmode -ky > repeatedly > >would remove the segments in question? > > It *might*. > > >There are two instances on that server so we noramlly have four > (Informix) > >shared memory segments when the instances are online (i.e two per > >instnace). > >After bringing down both instances we saw two segments still hanging in > >there. We could tell by the sizes of those segments that they both > belonged > >to one of the instances. > > Hm. Nope, no idea... > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com