Thank you.
STACKSIZE is already configured to 64K. That is the configuration that
failed.
DG
"Samar Desai" <samarof74@yahoo.com> wrote in message
news:b9k9ms$tte$1@terabinaries.xmission.com...
>
> John,
>
> You may need to increase STACKSIZE parameter in
> ONCONFIG file and bounce the engine. Standard value is
> 32K. Try using 64K stacksize.
>
> HTH
> Regards
> Samar
>
>
> --- John Carlson <john_carlson@whsmithusa.com> wrote:
> > On Tue, 6 May 2003 08:21:36 -0800, "David E. Grove"
> > <david_grove@correct.state.ak.us> wrote:
> >
> > >Just had an experience in which a user attempted to
> > run a very long SQL
> > >query. ("Long" in the sense that just to view the
> > text of the query
> > >required about a dozen screens when looking at it
> > with onstat) The SQL
> > >involved over 170 tables and UNION ALLs. However,
> > the selectivity on each
> > >table was pretty high, though. In any event,. it
> > used all the stack
> > >resources and crashed the server.
> > >
> > >This led me to ask tech support if there wasn't
> > some way to limit resources
> > >used by each user session so that users are
> > isolated. In other words, I
> > >wondered if there were some way to insulate users
> > from each other so that an
> > >individual user couldn't crash the system with a
> > rogue query. I was told
> > >that was not possible.
> > >
> > >Is this a common situation with other RDBMS's, or
> > is Informix unusual? Just
> > >wondering.
> > >
> > >Thank you for any comments from folks experienced
> > with other DBMS's.
> > >
> > >Regards,
> > >
> > >DG
> >
> > Which engine version is this?
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com