Cannot attach to shared memory errno = 22

Hello, C:\\\\Windows\\\\system32>onstat - MapViewOfFileEx: w32ec=487 at nt_shm.c:767 12:07:28 shmat: [22]: operating system error 12:07:28 Client could not attach server shared memory segment, use IFX_XFER_SHM BASE. onstat: Cannot attach to shared memory. errno = 22 above error comming with informix 11.50TC9 and windows server 2003 standard any one have idea about and have face this ever. how can we fix it Thanks Pushpa

Try to set SHMBASE values in your onconfig bigger than 0x1000000L, for example to 0xc000000L, and restart informix. On 20.05.2014 09:39, PUSHPA KUMARA wrote: > Hello, > > C:\\\\Windows\\\\system32>onstat - > MapViewOfFileEx: w32ec=487 at nt_shm.c:767 > 12:07:28 shmat: [22]: operating system error > 12:07:28 Client could not attach server shared memory segment, > use IFX_XFER_SHM > BASE. > onstat: Cannot attach to shared memory. errno = 22 > > above error comming with informix 11.50TC9 and windows server 2003 standard > any one have idea about and have face this ever. how can we fix it > > Thanks > Pushpa > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > -- *Ivan Zaviç* System & database administrator *T* +381 21 68 98 608 | *M* +381 69 846 99 08 *@*ivan.zavis@mi-system.co.rs <mailto:ivan.zavis@mi-system.co.rs> *M&I Systems, Co. Group* Bulevar vojvode Stepe 16, 21000 Novi Sad *T:* +381 21 68 98 602 *F:* +381 21 68 98 604 *@:* info@mi-system.co.rs *w:* www.mi-system.co.rs <http://www.facebook.com/pages/MI-Systems-Co/263409380366499>; <http://www.linkedin.com/company/m&i-systems-co.>; <http://www.youtube.com/misystemsco>; Odricanje od odgovornosti: Ovaj dokument namenjen je samo licima kojima je upucen i za pozivanje na isti od stane bilo kog lica, neophodna je naknadna pismena potvrda njegovog sadr§aja. Shodno tome, M&I Systems, Co. Novi Sad odrice svaku odgovornost i ne prihvata bilo kakvu obavezu (ukljucujuci slucaj nepa§nje) za posledice koje mo§e pretrpeti bilo koje lice zbog cinjenja ili necinjenja na bazi takve informacije pre nego çto takva lica prime dodatnu pismenu potvrdu. Ukoliko ste greçkom primili ovu elektronsku poruku, uniçtite ili izbriçite istu sa vaçeg racunara. Svako umno§avanje, çirenje, kopiranje, obelodanjivanje, izmene, distribucija i/ili objavljivanje ove elektronske poruke je strogo zabranjeno. Sadr§aj ove elektronske poruke ne predstavlja nu§no stavove M&I Systems, Co. Novi Sad

Hello, Thanks for the reply, the value is already set tot that. current value is " SHMBASE 0xc000000L " can we use more bigger value Thanks Pushpa

Yes, I think. On 20.05.2014 09:59, PUSHPA KUMARA wrote: > Hello, > > Thanks for the reply, > > the value is already set tot that. > current value is " SHMBASE 0xc000000L " > > can we use more bigger value > > Thanks > Pushpa > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hello, Thanks for the quick response, do you have any idea the approximate value that we can use Thanks

You can try 0x1100000 ? Depends on how much memory is in your server ... IBM resolved this: http://www-01.ibm.com/support/docview.wss?uid=swg1IC63111 On 20.05.2014 10:08, PUSHPA KUMARA wrote: > Hello, > > Thanks for the quick response, > > do you have any idea the approximate value that we can use > > Thanks > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hello, it's a 32bit server and i has 4GB memory only db server is running on server. Thanks

Hi, I have similar problems sometimes and use 0x2000000L as SHMBASE, also review on system some parameters like swap file. If possible define it as fixed size with 4095Mb. SP

Hello, Thanks for the reply, I thinks that is the best way that i can try. Thanks

I remember getting similar issues a few years back. We had to also exclude the system dll range to get large enough buffers setting as they sit just below the 2GB mark. This worked for us: SHMBASE 0x3000000L# system dll range SHMNOACCESS 0x70000000-0x7FFFFFFF Can use sysinternals process explorer to see if anything else jumping into memory range informix wants. For example we also found an old ISA2004 firewall client got in way so added: # FwcWsp.dll seems to be jumping in here (MS Firewall Client Windows Sockets 2 Service Provider). SHMNOACCESS 0x55600000-0x5562F000 Regards, Bryce Stenberg.