RE: Shared Memory Segments are not removed

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. No, we run onmode -ky once. Do you mean that running onmode -ky repeatedly would remove the segments in question? 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. Thanks Shehla > -----Original Message----- > From: Obnoxio The Clown [SMTP:obnoxio@hotmail.com] > Sent: Wednesday, March 08, 2000 4:25 AM > To: SArshad@purolator.com; informix-list@iiug.org > Subject: Re: Shared Memory Segments are not removed > > From: "Arshad, Shehla" <SArshad@purolator.com> > > > >I have seen this problem quite a few times on two of our HP-UX 11 servers > >running IDS 7.30.FC7 and was wondering if somebody has also encountered > >this. Sometimes, shared memory segments do not get removed at the O/S > level > >after Informix shutdown. ipcs -m shows these segments flagged with "D" > >under > >mode column. Removing these segments using ipcrm does not work either. > > > >What could be the cause of this? And how to avoid it? > > Several questions occur: > > 1. Are you running ipcrm as root? > > 2. Have you tried running onmode -ky repeatedly (even though it says the > server is already down)? > > 3. Do you not perhaps have another instance configured of which you are > not > aware? > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com

Arshad, Shehla (SArshad@purolator.com) wrote: : 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. : Thanks : Shehla Do these servers have different servernums in their onconfigs? I have a box with 5 or 6 servers (depending on my mood) running at once, each has about 5 shared memory segments but they go away when I tell them to (a very nice thing about sun).

Look also with ipcs -s for semaphores. When there are some pieces, remove them with ipcrm -s .... (root). Then it is possible that the deleted pieces are removed because now they are totaly free. Look also with ps -ef for processes running as informix. Regards Hans * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful

Hi!!, I hope don't be late. I have this problem too, and the ipcrm doesn't work, the system tell you that the id is invalid o.k.?, well the solution is that you need to kill (kill -9) all the users that were accesing to your database when it brings down. Look, everyday I make a dbexport, to do that, first, I shutdown my database to ensure that nobody is working to do the dbexport, in some cases, there are 3 or 5 users working when I shut it down, in this moment all the transactions of those users are closed (safely on the db) , but the problem is that there are processes of the OS that are making reference to the share memory, this is when your share memory becomes unusual. Thus, you only need to kill the process of those users (in my example, to those 3 or 5 users) to release the memory. See ya! * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network * The fastest and easiest way to search and participate in Usenet - Free!