Ansicht
Dokumentation

03275 - *BASE Activity level?

03275 - *BASE Activity level?

Fill RESBD Structure from EBP Component Structure   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

*BASE Activity level?

Actually, it isn't just one SAP program, it's quite a few, but I just know that
I can reproduce
the problem with STMS refresh...

Andy

--- Lloyd R Perera <lpereraZu...> wrote:
>
> Hi Andy
> I don't think your issues should or can be addressed through "standard"
> AS/400 OS parameters like activity levels or pool sizes etc... These are
> performance parameters to be set to manage "normal activity".... and as you
> point out, all is well - usually!
>
> As you point out, the problems is a very specific SAP transaction. When the
> specific transaction goes haywire, you see all hell break loose - and
> that's only the symptom!!! The increase in temporary space usage is caused
> by the SAP Application grabbing more and more memory (and then work space
> on disk) to do its dastardly thing! ...
>
> I suggest you raise an OSS note with SAP.... and get our friends at SAP
> working on it....
>
> I'm sure they'll be able to make sense of the "Commit operation failed due
> to constraint violation" message ..
>
> Cheers
>
> Lloyd R. Perera
> iSeries Technology Center
> Building 005-2/H103
> 3605 Highway 52 North
> Rochester, MN 55901
> LPERERAZU...
> Tel: (507) 286-6378 (tieline: 456-6378)
> Fax: (507) 253-0424(tieline: 553-0424)
>
>
>
>

>
> Squash

>
> <realsquashZya To: sap400Zm...

>
> hoo.com> cc:

>
> Subject: Re: *BASE Activity
level?
>
> 09/26/2001

>
> 04:24 PM

>
>

>
>

>
>
>
>
> My problem is that the unprotected memory (both used and maximum) goes up
> to sometimes as high as
> 75,000 mb! Normally the system sits at maybe around 5500 or so. Right now
> it's sitting at 23,400
> and climbing.
>
> Also, since the upgrade, about every other time I run TMS (from DEV, the
> domain controller) and
> refresh the PRD import queue, the TMSADM user locks up in the PRD system in
> client 000 after a
> second. To end the job takes around 5 hours if I actually let it go that
> long. And after this
> happens the pages go sky high. I'm talking a consistent, sustained 1500
> non DB pages where I
> usually see 0-35 normally, but never sustained! When the job finally ends,
> the paging goes back
> to normal.
>
> Also get some problems in the work process joblogs after the system runs
> for a while (but before
> any job crashes). Says "Commit operation failed due to constraint
> violation" which I never saw
> before the upgrade.
>
> So I discovered that a few PTFs were actually missing that are on the APAR,
> naughty me. I'm
> IPLing tonight so I hope it works....
>
> The performance on the system has been perfectly fine before the upgrade,
> even after the upgrade
> until a job pukes. It just seems like I can make the TMS refresh do it.
> So right now, that is my
> quick test.
>
> Andy Quaas
>
> --- Lloyd R Perera <lpereraZu...> wrote:
> > Folks
> > If I may add a few observations to Ron's note....
> >
> > The number of Work Processes defined in an SAP R/3 Instance is very
> similar
> > in function to setting Activity Level at the OS/400 level.... basically
> to
> > control the number of requests that can be processed at the "same
> time"...
> > I think the idea of setting this "high" is to allow the SAP experts
> control
> > this through the Instance Parameters.
> >
> > The Active-to-Wait value is not a measure of any problem. This is not to
> > be confused with what Ron mentions ACTIVE-TO-INELIGIBLE which can take on
> a
> > value greater than 0 if your max activity level is too low.
> >
> > Also, on the point of DB- and non-DB "pages" in the WRKSYSSTS display ...
> > the value you should be looking at is DB and non DB FAULTS - and a 100
> > faults per sec may in itself not be necessarily too high - unfortunately
> > this "depends" .... you need to see how many work processes are active.
> > However, if the overall response times experienced by the SAP user are
> fine
> > - why worry about a "technical value" like this!
> >
> > Your note does not say that you have bad response times in general! If
> you
> > had terminated a job, you may have sparked off a DB rollback associated
> > with the cancelled job.
> >
> > Cheers
> >
> > Lloyd R. Perera
> > iSeries Technology Center
> > Building 005-2/H103
> > 3605 Highway 52 North
> > Rochester, MN 55901
> > LPERERAZU...
> > Tel: (507) 286-6378 (tieline: 456-6378)
> > Fax: (507) 253-0424(tieline: 553-0424)
> >
> > ----- Forwarded by Lloyd R Perera/Rochester/IBM on 09/26/2001 03:33 PM
> > -----
> >
>
> >
> > Ron
>
> >
> > Schmerbauch/Rochester To:
> sap400Zm...
> >
> > /IBMZIBMUS cc:
>
> >
> > Subject: Re: *BASE
> Activity level?
> >
> > 09/26/2001 03:24 PM
>
> >
> >
>
> >
> >
>
> >
> >
> >
> >
> >
> >
> > If you press F1 when the cursor is sitting on the MaxActive text, you'll
> > get to see what the OS meaning of this value is, and it seems like you'd
> > want it set pretty high. Unfortunately, the DB also uses it. They divide
> > the available memory by this number to determine what a "fair share" of
> > memory for a job should be...so setting it low seems like a good thing.
> >
> > To satisfy both needs, you should set this value as low as
> > possible(favoring DB), without making the Act->Inel go above 0(the
> > indicator that you have set it too low). The 1.2x multiplier is ok, in
> > your case 27, just as long as that Act->Inel stays at 0 at all times.
> > If QPFRADJ is set to something other than 0, the adjuster tends to raise
> > the max act value a bit over time, so either set QPFRADJ to 0, or check
> > MaxActive once in a while to make sure it isn't getting really high.
> >
> > ps. To any who don't know...to find Act->Inel, Press F21, then set Expert
> > mode on WRKSYSSTS.
> >
> > Ron Schmerbauch 507-253-4880 rschmerbZu...
> > iSeries 400 - ERP Development - Rochester, MN
> >
> >
> > Squash <realsquashZy...> on 09/26/2001 02:49:39 PM
> >
> > To: SAP AS/400 List <sap400Zm...>
> > cc:
> > Subject: *BASE Activity level?
> >
> >
> >
> > I'm having performance issues since my V4R5 upgrade and I noticed that my
> > *BASE pool activity
> > level is set to 500. SAP note 428855 says:
> >
> > ------------------------------
> > QBASACTLVL:
> >
> > Activity Level of the *BASE Pool.Generally one or several SAP R/3 systems
> > are assigned to this
>
=== message truncated ===


__________________________________________________
Do You consolut?
Get email alerts & NEW webcam video instant messaging with consolut Messenger.
http://im.consolut.net

Durban Tours - Südafrika Safari

ABAP Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 9541 Date: 20240425 Time: 093133     sap01-206 ( 3 ms )