cancel
Showing results for 
Search instead for 
Did you mean: 

Error in bods job-time limit exceeded

siba_pkd21
Participant
0 Kudos

Hi All

A job which runs every 3 hour fetches some of it's executions with below error, it says time limit exceeded.

so the job is trying to run beyond it's time limit , is it someting related to huge data loading during that execution or any filer issue or anything else need to be done to resolve this error..please suggest.

Regards,

Siba

RichS
Participant
0 Kudos

Assuming you are reading from an SAP application datastore - the original timeout issue is probably related to a large volume of data being extracted. If you are attempting to limit the number of rows in your WHERE clause, make sure you are using expressions that can be evaluated on the SAP side (so that it doesn't bring back all rows and evaluate the expression in Data Services). Beyond that, you might consider breaking up the extract into multiple data flows that each pull a range of rows (by the primary key of the source table) and re-assemble them in the target environment. If all else fails, you could switch to an ABAP Data Flow.

Accepted Solutions (0)

Answers (1)

Answers (1)

DayaJha
Active Contributor
0 Kudos
siba_pkd21
Participant
0 Kudos

Hi Daya

this particular job which gives abap runtime error contains 22 Dataflows with 22 different source tables. All source tables cache is No & execute in background(batch) are not checked.

If we select execute in background option for each table, will it help as mentioned in best answer in the SCN thread?

Regards,

Siba

siba_pkd21
Participant
0 Kudos

Hi Daya, All,

While the recurring job executing withthe selection of the option-execute in background(batch) and source table cache is Yes , the Job ran with following error.