Long select on EBAN and VBAK

Question

From few days, and only on tuesday night or in Thursday night, a job stay on a long time on select to EBAN table. Also without logged user or other jobs/reports in runs.
In SM50 I see:
No Ty. PID      Status  Reasn Start Err Sem CPU      Time   Cl. User
52 BGD 22805    Running       Yes           0:19     930    020 IT
Report / Spool action
%_T001G0
Main Program
MASSBACK
Action                    Table
Sequential Read           EBAN
Waiting f.                                                                   since
Last SQL statement
SELECT "MANDT" , "BANFN" , "BNFPO" , "BSART" , "BSTYP" , "BSAKZ" , "LOEKZ" , "STATU" , "ESTKZ" , "FRGKZ" ,
"FRGZU" , "FRGST" , "EKGRP" , "ERNAM" , "ERDAT" , "AFNAM" , "TXZ01" , "MATNR" , "EMATN" , "WERKS" , "LGOR
T" , "BEDNR" , "MATKL" , "RESWK" , "MENGE" , "MEINS" , "BUMNG" , "BADAT" , "LPEIN" , "LFDAT" , "FRGDT" , "
WEBAZ" , "PREIS" , "PEINH" , "PSTYP" , "KNTTP" , "KZVBR" , "KFLAG" , "VRTKZ" , "TWRKZ" , "WEPOS" , "WEUNB"
, "REPOS" , "LIFNR" , "FLIEF" , "EKORG" , "VRTYP" , "KONNR" , "KTPNR" , "INFNR" , "ZUGBA" , "QUNUM" , "QU
POS" , "DISPO" , "SERNR" , "BVDAT" , "BATOL" , "BVDRK" , "EBELN" , "EBELP" , "BEDAT" , "BSMNG" , "LBLNI" ,
"BWTAR" , "XOBLR" , "EBAKZ" , "RSNUM" , "SOBKZ" , "ARSNR" , "ARSPS" , "FIXKZ" , "BMEIN" , "REVLV" , "VORA
B" , "PACKNO" , "KANBA" , "BPUEB" , "CUOBJ" , "FRGGR" , "FRGRL" , "AKTNR" , "CHARG" , "UMSOK" , "VERID" ,
"FIPOS" , "FISTL" , "GEBER" , "KZKFG" , "SATNR" , "MNG02" , "DAT01" , "ATTYP" , "ADRNR" , "ADRN2" , "KUNNR
" , "EMLIF" , "LBLKZ" , "KZBWS" , "WAERS" , "IDNLF" , "GSFRG" , "MPROF
Database                         Number              Time (usec)         Recs.
Direct Read                       310             987.892                 113
Sequential Read                   209            14238383                 899
Insert                              3                 655                   3
Update                              1                 155                   1
Delete                              0                   0                   0
Sources                       979.000  (Bytes)
RSQL                          446.648  (Bytes)
Commit                                                  0
DB Procedure Calls                  0                   0
Have you got any suggest?
Regards.

Answer 1

Hi,
sorry but I have to enter as this is a clear case of "lets guess and see what happens"
1) OP indicates
> a job stay on a long time on select to EBAN table
Are you sure is ONE long select and not a LOT of small selects? that information is not provided
2) OP do not provide full SQL statement
3) OP do not provide execution plan of the statement
4) OP do not provide statistical information about the runtime of the statement(s)
5) OP do not provide information about the available indexes, oracle version, blablablabla
There is no information whatsoever to be able to provide a meaningful answer or suggestion.
But immediately it is suggested to calculate statistics.
Please, read:
http://www.battleagainstanyguess.com/
I assume that, if you have read up to here you have realized that it is NOT possible to help you.
Please, HELP US to help you.
For that you have to do a little work
You have to provide proper information (for example the SAP note 212986 "Required data for processing CBO/RBO problems" will indicate what information would be necessary to analyze ANY performance issue at the DB level)
Any other thing would be waste of time, it may work or not or even make things worse. Nobody knows.