cancel
Showing results for 
Search instead for 
Did you mean: 

Time out error on SAP

Former Member
0 Kudos

Dear all,

we have prod cluster environment .

PRODCI -


> CI

PRODAPP1 -


>DI

PRODAPP2 -


>DI

Most of the end user are working DI (PRODAPP1 and PRODAPP2).

they are trying to get report through MB52, but got time out error . i have checked ABAP runtime error occured on PRODAPP1 and PRODAPP2 . i have checked same thing on PRODCI , i got the result i didnt get any error (TIME out).

let me know any issue on memory bottle neck on PRODAPP1 and PRODAPP2

Kindly suggest ,

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sateesh,

Does the Time out error indicate any Custom program being accessed by the Standard SAP program of MB52 ?

From ST12, run an ABAP trace when MB52 is being run from the dialog instances and analyse.

You may also want to buffer the table thats being accessed while MS52 runs.

Also, what OS is being used? I remember a similar problem with AIX 5.3 wherein, the network line between the CI and the DI was replaced with a faster one. Co-ordinate this with a UNIX and Network expert.

Regards,

Hari Kishan

Former Member
0 Kudos

Dear HARI ,

We are using AIX 5.3

how can i check the network line between the CI and the DI was replaced with a faster one ,

let me know what should i get from UNIX and Network team ..

Kindly suggest ....

Answers (4)

Answers (4)

Former Member
0 Kudos

Dear all,

I have checked SM50 on PRODAPP1 , the process has been terminated after the 600s and i have checked rdisp/max_wprun_time = 21600 in PRODAPP1.

The same thing i have tried in PRODCI , the process has been completed and its reached more than 800 sec , not giving any time out error and process also not terminated. i have checked rdisp/max_wprun_time = 21600 in PRODCI.

kindly suggest

Former Member
0 Kudos

Hi Satheesh,

Looks like in app server, it is just taking the default value as 600Secs. Can you set in Instance profile of your App server as 21600 and restart the app server and try again.

Moreover Check in RZ11 also , whether it has been set for all Active servers ( Check box) or not.

Thanks,

Jagadish

Former Member
0 Kudos

Hi,

To avoid the difference between the CI and DI, set this parameter rdisp/max_wprun_time in the default profile and then restart SAP instance once.

Hope this will resolve ur issue.

Regards,

Varadharajan M

Former Member
0 Kudos

>

> Hi,

>

> To avoid the difference between the CI and DI, set this parameter rdisp/max_wprun_time in the default profile and then restart SAP instance once.

>

> Hope this will resolve ur issue.

>

> Regards,

> Varadharajan M

Actually this parameter is dynamically switchable. So for a testing no need to bounce the system.

Former Member
0 Kudos

Hi Satheesh,

they are trying to get report through MB52, but got time out error . i have checked ABAP runtime error occured on PRODAPP1 and PRODAPP2 . i have checked same thing on PRODCI , i got the result i didnt get any error (TIME out).

Please check and compare the profile parameter "rdisp/max_wprun_time" parameter in PRODAPP1 and PRODAPP2 with PRODCI.

Regards.

Rajesh Narkhede

Former Member
0 Kudos

Dear Rajesh,

PRODAPP1 and PRODAPP2 Value for rdisp/max_wprun_time is same as PROD CI .

Kindly suggest.

former_member204746
Active Contributor
0 Kudos

TIME_OUT error means that a report took too much time to run. it has nothing to do with memory.

This can be caused by user error such as asking to show years of data in one go.

if someone goes in MB52 and click on EXECUTE without adding criterias, it can run for ages... and hit a TIME_OUT error.

ask your functional team to show your users to use that transaction adequately.

Former Member
0 Kudos

Dear Eric ,

Thanks for your reply .

But i have checked PRODCI , i didnt get any error .

i have tried same thing on PROD DI (PRODAPP1 and PRODAPP2) , but i got runtime error .

Kindly suggest .

former_member204746
Active Contributor
0 Kudos

check ST03 for red entries on your CI.

check SM51, click on your DI run the command and check if you see anything database related.

Former Member
0 Kudos

Dear Eric ,

Thanks for your reply ...

In ST03 where can i check red entries (PRODCI)

In SM51 what should i check .

Kindly suggest .

Former Member
0 Kudos

Dear all,

I have checked rdisp/max_wprun_time= 21600 for all the servers.

Hardware type........ "000184AAD400"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "PRODORADB"

Database type..... "ORACLE"

Database name..... "IRP"

Database user ID.. "SAPSR3"

Terminal................. "ssmanor-53"

Char.set.... "C"

SAP kernel....... 700

created (date)... "May 2 2010 21:56:27"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 254

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 16192

EM...... 465073128

Heap.... 0

Page.... 57344

MM Used. 455660336

MM Free. 5198544

Kindly suggest