Ansicht
Dokumentation
13318 - DB/SQL Problem
rdisp/max_wprun_time - Maximum work process run time BAL Application Log DocumentationThis documentation is copyright by SAP AG.
DB/SQL Problem
Jim,Great tip! - we've had it happen on occassion and will use this in the
future.
Thanks,
Tom
"Jim Doll" <jdollZp...>
03/12/2004 08:06 AM
Please respond to SAP on System i
To: <DoNotReply@consolut.eu>
cc:
Subject: Re: DB/SQL Problem
Tom:
We're in a similar situation--not being able to put maintenance on
regularly. We were on 1313 for a long time, with minimal trouble. We
upgraded to 1670 last Fall.
One suggestion with the overloaded WP: we had that a couple of times a
while ago, and we were able to go in to SM50 and change the individual
work process to RESTART AFTER ERROR = NO, then cancel it without core.
That put that work process out of commission and allowed us to limp by
until we were able to shut the entire system down--beats doing it during
the day!
Jim Doll, Perrigo
>>> tom.gainesZu... 03/11/04 05:50PM >>>
Hi all,
>From an appreciative long-time viewer, here's my first posting -
For about the last 2 months we have been getting SQL 7917 "Access Plan Not
Updated" errors on our production system (4.6c). CPU utilization has
increased but not enough to hurt us much, although there have been
complaints of slow response time on certain jobs. We are running an 830
with 3 processors and 10gb memory allocated to PRD. We have deleted the
SQL packages several times which temporarily cleans up the problem but the
frequency and impact of the error then builds up again until we delete the
packages again.
We opened a PMR with IBM and applied the PTF's they created for us. We
applied the latest cum at their request. We are also current on the fixes
recommended on the SAP infoapar. We now have a new error MCH 6802
"Literal Values Cannot be Changed" and the SQL 7917 error has resurfaced
again. We also had a MCH 3601 error "Pointer Not Set for Location
Referenced" which caused one of our SAP WP's to overload, requiring an IPL
to recover. I don't know if the pointer error is related to the others or
not.
IBM is doing what they can to get to provide fixes but it takes time. My
question to the group is has anyone experienced these errors, how much
should I worry about them, and what did you do to remedy them. Our
kernel level is old (1313) because we are in a FDA regulated environment
and updates require a special process. Is the old kernel a factor and if
so, why? Until now, we have not had performance issues.
Thanks much for any feedback.
____________________________________________________
Tom Gaines
Data Center Supervisor
Upsher-Smith Laboratories, Inc.
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.EasyMarketplace.de
DoNotReply@consolut.eu
consolut Links
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.EasyMarketplace.de
DoNotReply@consolut.eu
consolut Links
To visit your group on the web, go to:
http://groups.consolut.net/group/SAP on System i/
To unsubscribe from this group, send an email to:
DoNotReply@consolut.eu
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
BAL_S_LOG - Application Log: Log header data RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 4843 Date: 20240328 Time: 203237 sap01-206 ( 3 ms )