Ansicht
Dokumentation
08400 - Re(2): 3tier V5R1 - "unprotect/te mp s torage" for SPOOL WP
ABAP Short Reference PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Re(2): 3tier V5R1 - "unprotect/te mp s torage" for SPOOL WP
Hi Yannis,it is very interesting, that you see a large increasement in the QXDARECVR jobs.
There is no kernel running at all. That means, that this memory is used for the
open data paths of the tables in the DB2/400. There is nothing, that SAP can do
against this.
Do yopu want to setup the "automatic cycle"-parameter as well ?
Regards
Volker
-----Original Message-----
From: ÓìáñéáííÜêçò ÃéÜííçò [mailto:smarianakisZminoan.gr]
Sent: Freitag, 22. November 2002 09:37
To: Gueldenpfennig, Volker; DoNotReply@consolut.eu
Subject: Re(2): 3tier V5R1 - "unprotect/te mp s torage"
for SPOOL WP
Hi Volker,
I noticed that after the release upgrade that the temp space that QXDA*
processes use, increased. I use the command DSPTMPSTG in order to see this. I
also noticed an increase in temp space when SAP is up for many days (e.g 1
week). This problem existed before the upgrade also, but not as much. Also if
we use the commands DSPTMPSTG and WRKSYSTS we notice the following :
When the SAP first comes up the values that you see for temp space from both
commands are almost the same. If you wait for a day or two and run the commands
again, you see a variation of temp space between DSPTMPSTG and WRKSYSTS. The
temp space that I see from wrksyssts is greater than the one I see from
DSPTMPSTG.
That means that there is a memory leakage somewhere in the sence that some
processes do not free up the temporary space.
This problem was there before the upgrade also. For example, before the upgrade
we used to have a temp space (wrksyssts) of about 8-12GB with DSPTMPSTG of
about 6-10GB. Now we have a temp space (wrksyssts) of about 15GB with DSPTMPSTG
of 12GB. Sometimes especially when SAP runs for about a week (without restart)
we get a 20GB temp space (wrksyssts) while in DSPTMPSTG we see 12GB.
I think that the memory likage has to do with SAP kernel. As far as the
increase in temp space, (V4R5 vs V5R1) I believe that has to do also with the
previews problem but it is not the likage that causes it; of course the mem
likage contributes to this, making things worse. Maybe the processes in V5R1
run more efficiently know and as a result consume more temp space? I do not
have an answer for this, that is why I believe that SAP - IBM have to look over
it.
Regards,
Yannis
Gueldenpfennig, Volker [22/11/2002 9:50 ðì]:
Bi,
but why does this occur since you were moving from V4R5 to V5R1 ?
Don't you think, that this is independent from the SAP kernel then ?
Regards
Volker
-----Original Message-----
From: ÓìáñéáííÜêçò ÃéÜííçò [mailto:smarianakisZminoan.gr]
Sent: Freitag, 22. November 2002 07:32
To: Anderson, Doreen; DoNotReply@consolut.eu
Subject: Re: 3tier V5R1 - "unprotect/temp s torage" for
SPOOL WP
Hi,
We also have the same problem since our V4R5 to V5R1 upgrade. There were times
that we reached 20GB within a week!! So we IPL all servers every week.
I believe that there is a "memory leak" problem with SAP kernel which for some
reason get worse to V5R1.
Also there is no way to "direct" temporary space to use another ASP(other than
ASP1). As a result we are forced to add more disks to our ASP1.
I think that this is an issue that SAP should look into.
Regards,
*************************************
Yannis Smarianakis
Systems & Network Dept.
Minoan Lines
tel : +32810399892
e-Mail: smarianakisZminoan.gr
*************************************
Anderson, Doreen [21/11/2002 6:55 ìì]:
Since our V4R5 to V5R1 upgrade (Oct.26) the temp storage/unprotect on
our app servers had reached 26GB within 3 weeks. This forced us to
bounce SAP on the app servers (1 at a time) only 3 weeks into them being
up. With logon load balancing, we are able to pull an app server, wait
till all users end up on the other app server, and then bounce SAP on
the app server without impacting our 24x7 requirements, but this an
exercise that I would prefer not to do.
Before V5R1 we could run for more than 3 months without bouncing them.
Has anyone else run into temp storage issues since upgrading to V5R1?
We've not made any profile changes. We are at kernel patch lvl 4.6D
1124. V5R1 cume lvl C2134
Doreen
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
PERFORM Short Reference BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6854 Date: 20240602 Time: 185851 sap01-206 ( 2 ms )