Ansicht
Dokumentation
12409 - Tcode ME52 slow on V5R2
TXBHW - Original Tax Base Amount in Local Currency CPI1466 during BackupThis documentation is copyright by SAP AG.
Tcode ME52 slow on V5R2
Hi Victor!What did the SAPer say that the join is not specified properly,
i.e. there is no T_00.MANDT = T_01.MANDT clause.
Did you find the source statement? (Used ST05 trace?)
Kind regards
Rudi
-----Ursprüngliche Nachricht-----
Von: Lin, Victor [mailto:vlinZplastipak.com]
Gesendet: Donnerstag, 18. Dezember 2003 17:35
An: DoNotReply@consolut.eu
Betreff: Tcode ME52 slow on V5R2
Hello everyone,
After we upgraded our production system from V4R5 to V5R2 with lastest CumPack,
DB Fix, HIPER group, and other PTFs in II13337, we noticed that Tcode ME52 got
very slow, and verified that it is slow on our DEV/TST box also.
The SAP support folk found the slow SQL statement against table MARA and MARC,
and directed us to IBM support. The IBM support recommended a few PTFs. Some of
them were so "new" that they were not available for download yesterday.
I am curious how the other folks in this group execute Tcode ME52 on V5R2. The
SQL statemnt is
SELECT
T_00 . "MATNR" , T_01 . "WERKS" , T_01 . "XCHAR" , T_00 . "MTART" ,
T_00 . "MATKL" , T_00 . "MEINS" , T_01 . "TRAME" , T_01 . "UMLMC" ,
T_00 . "LVORM" "LVORM_MARA" , T_01 . "LVORM" "LVORM_MARC"
FROM
R3PRDDATA/"MARA"T_00 , R3PRDDATA/"MARC"T_01
WHERE
( T_01 . "MANDT" = ? AND T_00 . "MATNR" = T_01 . "MATNR" ) AND T_00 .
"MANDT" = ? AND T_00 . "MATNR" IN ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,
? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,
?....
, ? , ? ) AND T_01 . "WERKS" = ? WITH UR
And the library/SQL package/statement is R3PRDX0000/MARA/IHBHNKBKMOHKEMDO.
SQL4021 Access plan last saved on 12/15/03 at 06:19:58.
SQL4020 Estimated query run time is 11 seconds.
SQL4017 Host variables implemented as reusable ODP.
SQL4007 Query implementation for join position 1 table 2.
SQL4006 All indexes considered for table 2.
SQL4008 Index "MARC+WRK" used for table 2.
SQL4011 Index scan-key row positioning used on table 2.
SQL4007 Query implementation for join position 2 table 1.
SQL4006 All indexes considered for table 1.
SQL4009 Index created for table 1.
SQL4014 1 join column pair(s) are used for this join position.
SQL4015 From-column 1.*HOSTVAR, to-column 1.MATNR, join operator MF, join
predicate 1.
SQL4011 Index scan-key row positioning used on table 1.
Anybody has similar/different experiences with ME52 on V5R2?
Thank you very much,
Victor
SAP Basis Manager
Plastiapk Packaging INC
Have a look to our homepage at: http://www.consolut.net
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
Your use of consolut is subject to:
http://www.consolut.net
Durban Tours - Südafrika Safari
BAL_S_LOG - Application Log: Log header data SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4116 Date: 20240424 Time: 203428 sap01-206 ( 2 ms )
