NOAGE on Solaris 10

Does anyone have IDS 10 running on Solaris 10 and, if so, is NOAGE OK? My new instance is coming up with this error: Wed May 10 12:54:08 2006 12:54:08 Event alarms enabled. ALARMPROG = '/usr/informix/etc/alarmprogram.sh' 12:54:08 Booting Language <c> from module <> 12:54:08 Loading Module <CNULL> 12:54:08 Booting Language <builtin> from module <> 12:54:08 Loading Module <BUILTINNULL> 12:54:08 Could not disable priority aging: errno = 1 12:54:08 Could not disable priority aging: errno = 1 12:54:08 Could not disable priority aging: errno = 1 12:54:08 Could not disable priority aging: errno = 1 12:54:08 Could not disable priority aging: errno = 1 12:54:09 Could not disable priority aging: errno = 1 12:54:09 Could not disable priority aging: errno = 1 12:54:13 DR: DRAUTO is 0 (Off) 12:54:13 Requested shared memory segment size rounded from 552KB to 1024KB 12:54:13 IBM Informix Dynamic Server Version 10.00.FC4W3 Software SerialNumber AAA#B000000 12:54:14 IBM Informix Dynamic Server Initialized -- Shared MemoryInitialized. (I think they mean "ageing" by the way). The relevant ONCONFIG entry is: VPCLASS cpu,num=7,noage I wonder if it's because I'm running in a Solaris container. Can't see anything in the release notes and thought I would ask on cdi before raising a call in case this is a known limitation. Thanks -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com

----- Original Message ----- From: "Neil Truby" <neil.truby@ardenta.com> Newsgroups: comp.databases.informix To: <informix-list@iiug.org> Sent: Wednesday, May 10, 2006 8:03 AM Subject: NOAGE on Solaris 10 > Does anyone have IDS 10 running on Solaris 10 and, if so, is NOAGE OK? > > My new instance is coming up with this error: > > Wed May 10 12:54:08 2006 > > 12:54:08 Event alarms enabled. ALARMPROG = > '/usr/informix/etc/alarmprogram.sh' > 12:54:08 Booting Language <c> from module <> > 12:54:08 Loading Module <CNULL> > 12:54:08 Booting Language <builtin> from module <> > 12:54:08 Loading Module <BUILTINNULL> > 12:54:08 Could not disable priority aging: errno = 1 > 12:54:08 Could not disable priority aging: errno = 1 > 12:54:08 Could not disable priority aging: errno = 1 > 12:54:08 Could not disable priority aging: errno = 1 > 12:54:08 Could not disable priority aging: errno = 1 > 12:54:09 Could not disable priority aging: errno = 1 > 12:54:09 Could not disable priority aging: errno = 1 > 12:54:13 DR: DRAUTO is 0 (Off) > 12:54:13 Requested shared memory segment size rounded from 552KB to> 1024KB > 12:54:13 IBM Informix Dynamic Server Version 10.00.FC4W3 Software> Serial Number AAA#B000000 > 12:54:14 IBM Informix Dynamic Server Initialized -- Shared Memory> Initialized. > > (I think they mean "ageing" by the way). > > The relevant ONCONFIG entry is: VPCLASS cpu,num=7,noage > > I wonder if it's because I'm running in a Solaris container. > > Can't see anything in the release notes and thought I would ask on cdi > before raising a call in case this is a known limitation. > > Thanks > -- > Neil Truby t:01932 724027 > Director m:07798 811708 > Ardenta Limited e:neil.truby@ardenta.com Neil, My understanding is that if you are running IDS in a Solaris non-global zone there are two limitations: 1. you cannot prevent process aging and 2. you cannot force residency. These limitations are due to limitations of Solaris non-global zones and not an IDS limitation. To avoid error messages set the following 2 parameters in the onconfig file: NOAGE 0 RESIDENT 0 If either of these parameters are set = 1 the engine will run fine but you will see the error messages in the log file. BTW - We have been running IDS 10.0 FC3 in non-global zones for about 6 months with no problems whatsoever. Hope this helps, Ben

"Ben" <ben_informix@comcast.net> wrote in message news:mailman.151.1147273182.848.informix-list@iiug.org... > > ----- Original Message ----- > From: "Neil Truby" <neil.truby@ardenta.com> > Newsgroups: comp.databases.informix > To: <informix-list@iiug.org> > Sent: Wednesday, May 10, 2006 8:03 AM > Subject: NOAGE on Solaris 10 > > >> Does anyone have IDS 10 running on Solaris 10 and, if so, is NOAGE OK? >> >> My new instance is coming up with this error: >> >> Wed May 10 12:54:08 2006 >> >> 12:54:08 Event alarms enabled. ALARMPROG = >> '/usr/informix/etc/alarmprogram.sh' >> 12:54:08 Booting Language <c> from module <> >> 12:54:08 Loading Module <CNULL> >> 12:54:08 Booting Language <builtin> from module <> >> 12:54:08 Loading Module <BUILTINNULL> >> 12:54:08 Could not disable priority aging: errno = 1 >> 12:54:08 Could not disable priority aging: errno = 1 >> 12:54:08 Could not disable priority aging: errno = 1 >> 12:54:08 Could not disable priority aging: errno = 1 >> 12:54:08 Could not disable priority aging: errno = 1 >> 12:54:09 Could not disable priority aging: errno = 1 >> 12:54:09 Could not disable priority aging: errno = 1 >> 12:54:13 DR: DRAUTO is 0 (Off) >> 12:54:13 Requested shared memory segment size rounded from 552KB to>> 1024KB >> 12:54:13 IBM Informix Dynamic Server Version 10.00.FC4W3 Software>> Serial Number AAA#B000000 >> 12:54:14 IBM Informix Dynamic Server Initialized -- Shared Memory>> Initialized. >> >> (I think they mean "ageing" by the way). >> >> The relevant ONCONFIG entry is: VPCLASS cpu,num=7,noage >> >> I wonder if it's because I'm running in a Solaris container. >> >> Can't see anything in the release notes and thought I would ask on cdi >> before raising a call in case this is a known limitation. >> >> Thanks >> -- >> Neil Truby t:01932 724027 >> Director m:07798 811708 >> Ardenta Limited e:neil.truby@ardenta.com > > > Neil, > > My understanding is that if you are running IDS in a Solaris non-global > zone there are two limitations: 1. you cannot prevent process aging and 2. > you cannot force residency. These limitations are due to limitations of > Solaris non-global zones and not an IDS limitation. To avoid error > messages set the following 2 parameters in the onconfig file: > > NOAGE 0 > RESIDENT 0> > If either of these parameters are set = 1 the engine will run fine but you > will see the error messages in the log file. > > BTW - We have been running IDS 10.0 FC3 in non-global zones for about 6 > months with no problems whatsoever. > > Hope this helps, > > Ben Thanks Ben and others who pointed the above out. Now, who can help with zones and EMC Powerpath ....?! >