Skip to Content
0
Feb 11, 2011 at 05:01 PM

sequential read in sm66 - Database size 550GB - system slow for users

361 Views

Hello,

Currently when we use any standard transactions or custom program, it is going to sequential read in sm66.

We are getting slowness in system due to this issue for users.

Sm66 log:

sapXX01_XXX_00 0 DIA 12873 Running Yes 6 XIRFC ZCL_WM_S Sequential Read MARD

sapXX01_XXX_00 20 BTC 16155 Running Yes 15 Zuser1 ZCL_SD_D Sequential Read LTAP

sapXX01_XXX_00 29 SPO 12018 Running Yes 12 Zuser1 print 35

sapXX01_XXX_00 30 SPO 12037 Running Yes 12 Zuser1 print 35

sapXX01_XXX_00 31 SPO 12041 Running Yes 12 SAPSYS querying

sapXX02_XXX_02 3 DIA 15098 Running Yes 714 Zuser2 ZCL_IM_B

sapXX02_XXX_02 4 DIA 8158 Running Yes 38 Zuser2 RWRPLPRO Sequential Read WRPL

sapXX02_XXX_02 6 DIA 8160 Running Yes 555 Zuser3 ZCL_IM_B

sapXX03_XXX_03 0 DIA 1969 Running Yes 2390 Zuser5 SAPLFAGL Sequential Read BSIS

sapXX03_XXX_04 0 BTC 10811 Running Yes 209 Zuser6 ZCL_SD_D Sequential Read LTA

Database: Maxdb

OS: Linux

I understand that if you create Index on these table ( whichever it shows as sequential read ), it will improve the report performance.

Most of the time, system process shows that sequential read on VBAP, VKPA (sales tables), purchase tables, Finance tables and etc.

If sm66 shows as sequential read for few table, that means that corresponding user will get slowness on getting report/transaction output. I agree on that.

Is there any reason other user will get slowness ie if i run Va03 transaction, WE02 transaction which is not relevant to sm66 process over view.

I appreciate, if you give some recommendations reg. this performance improvement and to avoid this kind of sequential read.

Thanks

Praba