Actually, I thought about this again and you might be able to use a logon
trigger.
Conner might be correct.
Jim
"Connor McDonald" <connor_mcdonald_at_yahoo.com> wrote in message
news:9tu869$luc$1_at_news5.svr.pol.co.uk...
> There is a routine is DBMS_SYSTEM to set parameters in other sessions -
but
> I'm not currently at a database to see if it works.
>
> hth
> connor
>
> =================================
> Connor McDonald
> http://www.oracledba.co.uk
>
> "Jim Kennedy" <kennedy-family_at_home.com> wrote in message
> news:vcwM7.81013$XJ4.43922236_at_news1.sttln1.wa.home.com...
> > Not that I know of. Maybe get them to buy the extra RAM or fix the bad
> sql.
> > They should be willing to fix the problem; it is unlikely they actually
> know
> > it is a problem and you would be doing them a massive favor to tell them
> > where the problem is. If they act defensive then bump the problem up
the
> > chain. Although good customer service organizations will listen nicely
> and
> > help to fix it.
> > Jim
> > "Jens Lundell" <lundellj_at_saic.com> wrote in message
> > news:c4fbc557.0111261028.115bbf7f_at_posting.google.com...
> > > I know I can set sort_area_size (and sort_area_retained_size) at the
> > > instance level in init.ora and for "my" session using "alter session
> > > set sort_area_size = xxx". But is it possible to set sort_area_size
> > > for another session or for a specific user and/or user type? We have a
> > > third party application that (due to bad SQL) needs a BIG sort area
> > > but we can't afford to set that big sort area at the instance level.
> > >
> > > Thanks,
> > >
> > > -Jens
> >
> >
>
>
Received on Mon Nov 26 2001 - 14:58:18 CST
