Time_Out Dump

[Former Member]

Hi Experts,

I am facing time_out dump in one of the master data cif queue.

the error details are as below.

the dump is occuring while fetching data from /SAPAPO/MATLOTSZ table, the no of entries are 196940.

could someone guide me on this issue please.

Thanks in Advance

Regards,

Kushala

[madhu_vadlamani]

Hi,

What are the basic setting you have for time. Just discuss with basis guy.

Madhu.

[Former Member]

Hi Madhu,

The time is 1500 seconds set, we are still facing the dump.

Do you have any other suggestions on this Please?

Regards,

Kushala

[madhu_vadlamani]

Hi,

This is enough. Now try to tune the program.

[Former Member]

Hi Madhu,

We have done optimization to the code, still we have time_out dump.

is it becaus of the for all entries used in the second select query, as the no of records is 196000?

Thanks in advance

regards,

Kushala

[raymond_giuseppi]

Start optimizing your program (SAPLZxxx  customer development) - Use tools as SAT (SQL statement or some wrong itab management in code) and ST05 (no index, multiple select single) to analyze cause of bottlenecks or performance issues.

Also consider convert program to background job, so no time-out.

The time is 1500 seconds

Already very long (far away from recommendations, but alas not unusual)

Regards,

Raymond

[Former Member]

Hi Raymond,

Thanks for your suggestion.

Even after optmizing the program, i am still facing the dump.

we had similar issue in test system, after the code optimization we are seeing the dump in test system, where as the issue still exist in production.

i am attaching the prece of the code where the issue is occuring,kindly check and let m eknow your suggestions please.

[raymond_giuseppi]

Could you try to replace the two select statements with a single SELECT with JOIN or subquery, so removing the FOR ALL ENTRIES. Also execute some ST05 for missing required index (look for some table full scan or with only client key)

Regards,
Raymond

[former_member195402]

Hi Kushala,

if this timeout occurs in dialogue, then try it in batch mode, where the timeout value is much higher.

If the above code is in a loop (LOOP. WHILE, DO) then you can set a commit work after the SELECT FOR ALL ENTRIES to reset the timeout counter.

Or you can try to improve your code.

Regards,

Klaus  

[former_member1084186]

Hi Kushala,

Some suggestions sorted based on relevance.

1. Performance optimization. that means using index( may be create an index, if there is none), or using many fields in where clause if possible.

If you have done all these, but still face issue then parallel processing is your answer.

2. check the value for this parameter

rdisp/max_wprun_time  = ?  Is it really set as 1500 seconds

3. If nothing works and seems that actually you are selecting a lot of data without any optimization possible, then thing about background processing. It can go and go on for a very long time, without giving a time out error.

[former_member199306]

Hi Kushala,

It seems time out error is coming due to your select query since it is fetching lots of records.

you can analyse the root cause by using T-code 'ST05'.

there by using proper index you can reduce your CPU cost time.

Regards,

Bhupendra