Re: Oracle 8.0.6.2 MTS configuration..need help?

Hi Howard,

Thanks again for your advice.
You are so humorous about "disaster in waiting".

I totally agree with you, some of these automatic tuning, either it is NOT BIG enough, or like you says "disaster in waiting". Yes, I agree, I should start with the NOT so large number and tune it up if I need the large pool to be bigger.

But you know what I work as a TEMP(oracle DBA) in a company in california. This company is small, but the oracle is very busy and processing a lot of short request per second, usually can't go down at all.
And the uppermanagement might require to TURN MTS ON. Even if I or some users get some errors occasionally, not sure whether I could even have downtime in midnight to fix it. Somehow their service contract with customers are very strict.

A lot of time, I have to do some GOOD GUESSING. The things is they don't have enough $$$ to build a bigger stress-test or testing cluster either. (Current testing cluster is very small, very different from the production one). So working in these environment is quite stressful for me. I am trying my best.
I even tell them I never use MTS at all. I am quite honest with them, I don't lie. If I never use it, I never use MTS.

Dominica

"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message news:<3d582b62_at_dnews.tpgi.com.au>...
> There aren't any really good metrics on tuning the large pool,
> unfortunately.
>
> The approach I've used in the past is: guess. Stick it to about 10M to start
> with, and then have a look, and start tuning.
>
> Tuning consists of seeing whether vast swathes of your initial 10M are
> sitting there doing nothin (in which case, you can make it smaller), or
> seeing whether you get 'unable to0 allocate memory' errors (in which case,
> make it bigger). To test for wasted space, do select * from v$sgastat where
> pool='large pool';. There's a 'free memory' statistic there, which
> shouldn't be too big.
>
> There is an alternative: if you set the init.ora parameter
> PARALLEL_AUTOMATIC_TUNING=TRUE, you get a large pool automatically
> allocated -and Oracle works out what size it should be. I haven't tested how
> *good* its calculations are, though, so I have no idea whether this is truly
> a magic fix, or a disaster in waiting. I've heard good reports about it,
> though -and have NOT heard bad ones.
>
> If you set PARALLEL_AUTOMATIC_TUNING=TRUE, obviously don't set your own
> value for large_pool_size, as that is likely to cause confusion (to yourself
> or your colleagues down the track, if not to Oracle itself!).
>
> Regards
> HJR
>
>
>
> "Dominica Leung" <dominica_l_at_yahoo.com> wrote in message
> news:5f8af180.0208121232.6673b7c_at_posting.google.com...
> > Hi Howard,
> >
> >
> > I really really appreciate your help on my question.
> > I understand WHEN should I use MTS now.
> > For the "LARGE_POOL_SIZE", what should I set to.
> > CUrrently, my SGA is around 100 Meg.
> >
> >
> > Dominica
> > ============
> > "
> > Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
> news:<3d546e38_at_dnews.tpgi.com.au>...
> > > "Dominica Leung" <dominica_l_at_yahoo.com> wrote in message
> > > news:5f8af180.0208091526.69a763c_at_posting.google.com...
> > > > Hi Sybrand,
> > > >
> > > > One more thing,
> > > > I need to increase the SGA area right , if I would be RUNNING
> > > > MTS in my server.
> > >
> > > When you configure MTS, you should configure a LARGE_POOL_SIZE. When you
> do
> > > that, the SHARED_POOL_SIZE doesn't need to increase significantly.
> > >
> > > As ever, though, it's a question of tuning: monitor the shared pool and
> see
> > > if can benefit from a modest increase.
> > >
> > > > Basically, I am not too sure, what other oracle parameters
> > > > I should be changing/tuning when change to MTS version.
> > >
> > > There aren't many, apart from the obvious MTS_ ones. LARGE_POOL_SIZE is
> the
> > > only one that readily springs to mind.
> > >
> > > Regards
> > > HJR
> > >
> > > > This part really worry me.
> > > > Since I NEVER run MTS in my whole career in the production
> > > > environment and this production environment is very sensitive.
> > > >
> > > >
> > > >
> > > > Dominica
> > > >
> > > > =======
> > > >
> > > > S
> > > > ybrand Bakker <postbus_at_sybrandb.demon.nl> wrote in message
> news:<ld38luggqm8dd6ou4imt2bss7rp78un291_at_4ax.com>...
> > > > > On 9 Aug 2002 11:37:16 -0700, dominica_l_at_yahoo.com (Dominica Leung)
> > > > > wrote:
> > > > >
> > > > > >Sorry, one question, the mts_dispatchers should be
> > > > > >listenering on its own port right?
> > > > > >Not the same as the LISTENER.
> > > > >
> > > > > Hi Dominica,
> > > > > not necessarily. You can always set up an extra tnsnames.ora entry
> > > > > with (server=dedicated) added. When you look at lsnrctl services,
> you
> > > > > will see you get 2 different services, whether using 2 different
> ports
> > > > > or not.
> > > > >
> > > > > Hth
> > > > >
> > > > >
> > > > > Sybrand Bakker, Senior Oracle DBA
> > > > >
> > > > > To reply remove -verwijderdit from my e-mail address
Received on Tue Aug 13 2002 - 18:22:31 CDT