Re: Shared memory segments hanging around

Jacob Salomon <jake@apparel.net> wrote: : Hi Folks. : I have a problem I that calls for familiarity with certain quirks. : OnLine DSA 7.13.UC5: : HMMmm... I looked at ipcs -m and found the shared memory segments : hanging around. (Minus the user segment with the permissions rw-rw-rw-) : When I ran ipcrm -m on these segments, they get marked D and the key : values got zeroed out but they still hang around and I cannot bring up : the instance again. : So why can't it come up again? Those shared memory segments I see: Are : they from this current attempt to come up or are they holdovers from the : session that was running before I changed the parameters? I am inclined : to suspect the former, because the error was in "addseg" and there is a : segment missing (the user segment). : Oh yes, when the system gets rebooted, the OnLine comes up without a : hiccup. (With the locks adjusted as desired.) I've seen this problem a few times, under 8.10 UC1 (XPS) on a SP2. Here is my understanding. 1) First the engine came down in such a manner that all of the shared mem. seg. were not released. The oninit's may have died, but the O.S. can not release the segments until all associated processes are terminated. The next time this happens do a ps -ef. Look for anything that could be attached to a database (4gl's, dbaccess, isql, esqlc, etc ) and kill it. 2) Second you could not bring an instance up with the defucnt shared mem. because the engine wants to attach to shared mem. at particular address. Well those slots are aready occupied. 3) If I could not find any ghost processes referenced in note 1, I had to reboot the box to move on. I believe with a perl or c program and the key to the shared mem seg. you could release the segments by hand. Goodluck, Kevin D. Perry DBA for food money / PLT LDR - FDO for love Argus Health systems