Ansicht
Dokumentation
13304 - DB/SQL Problem
TXBHW - Original Tax Base Amount in Local Currency TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
DB/SQL Problem
Hi Tom,first of all:
Your performance problems are definetely NOT related to your old
kernel!
It would be useful to update this kernel because of several reasons -
but I fully understand the reason why you can't do this very often.
The MCH3601 depends on the from&to-program. As I assume, that this is
a new error, I guess it might be in the DB2 interface. Then it can
only be fixed with PTFs. If you see SAP coding related to it we would
need a new kernel. As you didn't change the kernel, I assume the IBM
coding here.
SQL7917 is quite normal if you added indexes or changed your database
contents a lot. This means, that the optimizer decision changed and
then the SQL packs shopuld be updated. As they are usually locked by
other WPs this mostly results in SQL7917 and then locally created SQL-
Packs.
You should delete the SQL-Packs after installing any PTF, after
creating new indexes or after a certain time, where your DB-structure
might have changed. How often do you see these errors ? Every day
after SQL apck deletion ?
MCH6802 looks like a DB2 problem wherte you can only install the
latest PTFs and then open a PMR. This error is not known to me. So, I
assume that this happens quite rarely - which makes it a bit harder
to find for IBM - but you can assume, that they are working hard on
this issue.
Regards
Volker
e-mail: volker.gueldenpfennig "at" easymarketplace.de
web: www.easymarketplace.de
--- In DoNotReply@consolut.eu, tom.gainesZu... wrote:
> 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]
Durban Tours - Südafrika Safari
PERFORM Short Reference BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 4165 Date: 20240425 Time: 091445 sap01-206 ( 2 ms )
