DSWP transactiontaking more tha 30 minutes to show up

[Former Member]

Hi

DSWP transaction is taking long time to show up. Its running the below reports SAPLSMSY_GET_DATA and SAPLSMSY_PPMS_API and doing sequential read. Can any one hep me on improving the performance of this transaction.

Thanks

[Former Member · Accepted solution]

What is your Solman Version?

Do this to evaluate the root cause,

1. SE30---> Transaction ---> DSWP -

---

> Hit Execute.

ONce you get the screen hit BACK.

This will give us the file and hit Evaluate FILe --> Reply here if it is taking more time in DB or ABAP.

Thanks

SM

[Former Member · Accepted solution]

Hi SM,

Below are the results. We are on 7.0 ehp1 sp 25

Execution time in microseconds:

ABAP 625.550.326 = 53,2%

Database 550.083.695 = 46,7%

System 1.295.034 = 0,1%

Thanks

Kiran Nekkanti

[Former Member · Accepted solution]

On the evalution Page click the Hit List on the top right side, and sort by Net%, paste the top 15 Calls here.

Thanks

SM

[Former Member · Accepted solution]

Hi SM

The below are the results

341.426 377.515.926 = 377.515.926 32,1 32,1 Fetch SMSY_PROD_VERS

340.003 732.277.845 348.109.960 62,3 29,6 Perform READ_SINGLE_PRODUCTVERSION

5.053.479 917.340.635 186.285.134 78,0 15,8 Call Func. SMSY_GET_PRODUCT_TO_PRODVER

9.468 129.953.973 = 129.953.973 11,0 11,0 Fetch SMSY_SYST_PRODVR

19.307 25.445.824 = 25.445.824 2,2 2,2 Fetch SMSY_SWCV_PV

9.301 1.079.238.221 20.150.587 91,8 1,7 Call Func. SMSY_GET_PRODVERS_TO_SYSTEM

9.481 10.518.445 = 10.518.445 0,9 0,9 Fetch SMSY_SYSTEM

9.308 10.513.789 = 10.513.789 0,9 0,9 Fetch SMSY_SYS_RELINST

341.426 7.578.478 = 7.578.478 0,6 0,6 Open Cursor SMSY_PROD_VERS

820.417 6.611.868 = 6.611.868 0,6 0,6 Perform X031L_TO_DFIES

9.468 140.311.830 4.863.709 11,9 0,4 Call Func. SMSY_GET_INSTALED_PRODVERS

53.621 10.366.478 3.754.610 0,9 0,3 Perform FIELDLIST_TO_DFIES

53.621 11.146.183 3.543.854 0,9 0,3 Perform CHECK_SECURITY

9.301 1.118.841.300 2.454.881 95,1 0,2 Call M. CL_SMSYB_BUFFER_PRODSYS_RELS=>GET_PRODVERS_FOR_SYS

538.130 37.148.198 2.165.763 3,2 0,2 Call Func. SMSY_IS_ABAP_INSTANCE

28.353 432.256.329 2.102.037 36,7 0,2 Call Func. SMSY_BASIC_GET_DATA

24.925 41.817.738 1.752.656 3,6 0,1 Call Func. SMSY_BASIC_GET_DATA

53.621 3.694.501 1.558.301 0,3 0,1 Call Func. BAL_LOG_CREATE

53.621 15.047.634 1.462.497 1,3 0,1 Call Func. DDIF_NAMETAB_GET

53.621 1.912.366 1.258.606 0,2 0,1 Call Func. BAL_LOG_REFRESH

53.622 1.336.904 1.182.272 0,1 0,1 Call Func. GUID_CREATE

107.242 1.103.677 = 1.103.677 0,1 0,1 Select Single SMSY_OPTIONS

1.134 2.847.997 1.005.241 0,2 0,1 Call Func. SMSY_GET_COMP_REL_TO_PROD_VERS

1.424 1.981.101 889.651 0,2 0,1 Perform UPDATE_PRODVER_BUFFER

37.734 37.632.057 874.974 3,2 0,1 Call Func. SMSY_GET_COMP_VER_TO_INST

19.307 796.942 = 796.942 0,1 0,1 Open Cursor SMSY_SWCV_PV

53.621 2.252.090 696.199 0,2 0,1 Call Func. DD_GET_NAMETAB

18 671.118 = 671.118 0,1 0,1 Fetch SMSY_SYSTEMS

9.300 8.113.747 627.192 0,7 0,1 Call M. CL_SMSYB_BUFFER_PRODSYS_RELS=>GET_RELINST_FOR_PRODVERS

107.242 1.705.847 602.170 0,1 0,1 Perform GET_SMSY_OPTION_VALUE

200.506 732.524 572.580 0,1 0,0 Call Func. GUID_CREATE

53.621 542.668 = 542.668 0,0 0,0 Open Cursor SMSY_SYSTEMTYPE

53.621 541.832 = 541.832 0,0 0,0 Call CUR_LCL

335 523.214 = 523.214 0,0 0,0 Fetch SMSY_MAIN_INST

69.032 518.931 = 518.931 0,0 0,0 Select Single SMSYPPMSUPDATE

9.300 6.110.356 507.443 0,5 0,0 Call Func. SMSY_GET_INSTANCES_OF_PRODVERS

49 497.692 = 497.692 0,0 0,0 Fetch SMSY_LOGCMP_VER

12.681 1.756.071 486.470 0,1 0,0 Call Func. SMSY_GET_INSTANCES_OF_PRODUCT

9.301 1.143.934.230 480.280 97,3 0,0 Call M. CL_SMSYB_BUFFER_PRODSYS_RELS=>GET_RELINST_FOR_SYS_WITH_PROD

53.621 470.948 = 470.948 0,0 0,0 Call Func. ECATT_MODIFY_BALMSG

53.621 458.237 = 458.237 0,0 0,0 Fetch SMSY_SYSTEMTYPE

9.301 1.039.480 430.697 0,1 0,0 Call Func. SMSY_GET_PRODUCT_TO_PRODVER

12.681 1.127.612 400.959 0,1 0,0 Perform GET_MAIN_INST_FROM_BUFFER

9.481 394.549 = 394.549 0,0 0,0 Open Cursor SMSY_SYSTEM

9.308 378.810 = 378.810 0,0 0,0 Open Cursor SMSY_SYS_RELINST

9.468 354.425 = 354.425 0,0 0,0 Open Cursor SMSY_SYST_PRODVR

19.307 338.294 = 338.294 0,0 0,0 Import Nametab SMSY_SWCV_PV

257.750 317.317 = 317.317 0,0 0,0 Call RFCControl

53.621 514.373 313.884 0,0 0,0 Perform SHADOW_EXCEPTION

Edited by: Kiran Nekkanti on May 18, 2011 12:37 PM

[Former Member · Accepted solution]

I have checked the Table SMSY_PROD_VERS in my System, it is of 1280 KB and it's kind of Weird that it has the highest run time.

Can you check the size of this Table SMSY_PROD_VERS, and you might wanna do some Index rebuilds if you see any Fragmentation and update stats using Program RSANAORA.

Thanks

SM

[Former Member · Accepted solution]

Hi Sm

I have only 2718 entries and i have done stats and indexing they look good. still it takes same time. we are on Db2

Thanks

[Former Member · Accepted solution]

FETCH on Table SMSY_PROD_VERS indicates data Transfer from Table to SAP.

If there only fewer entries but the session is taking long time to read the table, check the ST04 --> Session --> SQL & Explain plan.

Perhaps you can create a medium priority Message with SAP.

Thanks

SM

[Former Member · Accepted solution]

Hi SM

DSWP when i click on active solution for prod it take more time but when i click any other solution it comes up immediately. Any thoughts on this.

Thanks

[Former Member · Accepted solution]

WHen you have too many EWA Sessions under Prod Soltuion, You have to delete the obsolete ones, like 6 Months ago, or 1 Year ago,

This will make the Solution to show up faster on the first time visit.

Thanks

SM

[Former Member · Accepted solution]

Hi SM

Even tried that and kept only 2 months of data. I will create a ticket with sap see what they say about it and thanks for all your help

Thanks