cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent issue : Short Dump --Time out Error

Former Member
0 Kudos

Hello BW Experts ,

While loading master data for Order Number from R/3 production to BW Development we are getting short dump error message . When I checked in ST22 for the short dump it shows " Time Out Error message ".

The data is loaded successfully upto PSA and from Transfer rules is it not going ahead. The total time is just 1 Hrs and number of records loaded upto PSA are 193211.

Surprisingly while loading data from R/3 Production to BW Production we do not get any error and same number of records are loaded.

The transfer rules are active in BW development server and are same as that of BW Production server.

I have tried to load the data 5 times uptil now , but same error continues.

Any help please .

Best Regards,

Amol.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Amol,

Are there any transfer routines in the transfer rules.

I think this is a ABAP program error.

Check the OSS Notes : 505585 and 380999

it may help.

Thanks

hari

Former Member
0 Kudos

Hello Hari My Friend in Wipro ,

Kusuma Bandi Harinath ,

We do not have any transfer routines in Transfer rules.

Regards ,

Amol.

Former Member
0 Kudos

Hi Amol,

the problem may be in Update Rules, and in particular in Start Routine.

Try to debug starting from the PSA with the selection "Simulate Upload".

Maybe you are trying to read a table too large.

Hope this help.

Ciao.

Riccardo.

Former Member
0 Kudos

Hello Riccardo ,

I am loading master data for Order Number. So there are no update rules.

We do not have any routine in Transfer rules .

Amol.

Former Member
0 Kudos

Hi,

Please check the profile parameters (like rdisp/max_wprun_time and few other timeout parameters) in RZ10 or RZ11 and increase the value.

also check this thread

Assign Points if Useful....

-Shreya

Former Member
0 Kudos

Hi Amol,

You need to dig further in the short dump and post the entire message here. It could either be a tablespace issue or your server has too many requests at the sametime.

Bye

Dinesh

Former Member
0 Kudos

Hello Dinesh ,

Please note that system profile "rdisp/max_wprun_time"

setting was previously 600 one month back and 20 days back we have made it 1800 but still the same error .


Following is the error message ,
Runtime

Error TIME_OUT

The program "XYZ……." has exceeded the maximum permitted
runtime without

 
Error analysis


After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.

The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 1800 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.

successfully processed, the system gives it another 1800 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".


How to correct the error

You should usually execute long-running programs as batch jobs.

If this is not possible, increase the system profile parameter

"rdisp/max_wprun_time".

Depending on the cause of the error, you may have to take one of the

following measures:

- Endless loop: Correct program;

- Dataset resulting from database access is too large:

Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

(for example);

- Database has an unsuitable index: Check index generation.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

Regards ,

Amol Kulkarni.