Timeout dumps

[Former Member]

Hi All,

In our PI Production system we are getting lot of time out dumps in ST22 as below.

The program u201CCL_XMS_PERSIST_ADM============CPu201D has exceeded the maximum permitted uninterrupted runtime and has therefore been terminated.

I have checked all of Dialog work process is Running and ON HOLD state is it any cause for these dumps.. as well as rdisp/max_wprun_time chaged to 900.

Short text

Time limit exceeded.

What happened?

The program "CL_XMS_PERSIST_ADM============CP" has exceeded the maximum

permitted uninterrrupted

runtime and has therefore been terminated.

What can you do?

Take note of the actions and inputs that lead to the error.

Contact your SAP administrator for further processing of the problem.

Using transaction ST22 for ABAP short dump analysis you can see and

administrate termination messages and retain them for a longer period.

Error analysis

The system profile contains the maximum runtime of a program.

When this time limit has been exceeded, the program is terminated

to make way for other users who may be waiting.

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.

Kindly advice on this..

Regards,

KUMAR

[former_member703274]

Recommend this to be executed in background if possible and you can find that option in your screen (Program-> execute-> execute in Background) while executing whatever report you were working on. This will create a job and the same status can be fond in SM37 and report can be fetched without any changes once the job is finished.
Also changing parameter can always be done with respect to your standards which was SET with SAP help. Also try to activate ABAP trace while working on this to check further.

[Former Member]

Hello Sir,

I am getting the same error for using modify statement for an internal table.

Something like:

Modify ITAB from i_struct where <some_condition>

ITAB has lots of records almost close to 1 lakh entries.

As per the above solution, indexing the DDICs solved the issue. What about the case in internal tables.

Kindly give your inputs.

Thanks & Regards,

Rohit

[venkata_emandi]

increaseing rdisp/max_wprun_time this parameter will effect to the entire system i.e all dialog process can run till that given time which interns effect the performance of the system.

Try tracing the program when it is running and fine our the response time and sql statements and then tune the tables by adding index etc.

thanks

venkata

[Former Member]

Hi,

Increase the wp process runtime to 1800 and check. Update the DB stats if necessary.

Regards,

Vamshi.

[Former Member]

I have changed to 1200 but there is still existing error

[Former Member]

again increase it to 2000, have you restarted the instance, after changing any profile parameter you need to restart the SAP instance.

[Former Member]

Hello,

Also don't do this profile parameter changes to production server directly,

first check with dev or qty. also take proper downtime, then restart the sap instance properly, if works ok with dev or qty then do changes in production.

Regards,

Kiron.

[Former Member]

rdisp/max_wprun_time is dynamically switchable right?

just changed to new value i didnt restarted.

Regards,

Kumar

[Former Member]

i am able to view the messages in SXMB_MONI but when i click on message to open it will taking long time then it creates dump..

pls find logs below

How to correct the error

Long running programs should generally be run as batch jobs.

If that is not possible, the system profile parameter "rdisp/max_wprun_time"

can be

enlarged.

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 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,

please use the following search criteria:

"TIME_OUT" " "

"CL_XMS_PERSIST================CP" bzw.

"CL_XMS_PERSIST================CM02M"

"READ_CHILDS"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem (short dump).

To obtain this, select "System->List->Save->Local File (unconverted)"

on the current screen.

2. A suitable hardcopy printout of the system log.

To obtain this, call the system log with Transaction SM21

and set the time interval to 10 minutes before and 5 minutes after

the short dump. In the display choose "System->List->Save->

Local File (unconverted)"

3. If the programs are your own programs or modified SAP programs,

======================================================================================

Tue Jan 4 17:26:46 2011

rdisp/max_wprun_time: 900 -> 1200

Tue Jan 4 17:59:30 2011

rdisp/max_wprun_time: 1200 -> 1800

Tue Jan 4 18:31:50 2011

OCIStmtExecute() failed with -1=OCI_ERROR

SQL error 1013:

SQL cancelled; calling registered function at 4efd80

program canceled

reason = max run time exceeded

user = PISUPER

client = 500

terminal = dv2700-PC

report = CL_XMS_PERSIST================CP

TH VERBOSE LEVEL FULL

• RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

• RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

• RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

• RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

• RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

• RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

• RABAX: level LEV_RX_RESET_SHMLOCKS entered.

• RABAX: level LEV_RX_RESET_SHMLOCKS completed.

• RABAX: level LEV_RX_ROLLBACK entered.

• RABAX: level LEV_RX_ROLLBACK completed.

ABAP Program CL_XMS_PERSIST================CP .

Source CL_XMS_PERSIST================CM02M Line 53.

Error Code TIME_OUT.

Module $Id: //bas/710_REL/src/krn/th/thhiserv.c#12 $ SAP.

Function ThTimeout Line 1736.

• RABAX: level LEV_RX_STDERR completed.

• RABAX: level LEV_RX_RFC_ERROR entered.

• RABAX: level LEV_RX_RFC_ERROR completed.

• RABAX: level LEV_RX_RFC_CLOSE entered.

• RABAX: level LEV_RX_RFC_CLOSE completed.

• RABAX: level LEV_RX_IMC_ERROR entered.

• RABAX: level LEV_RX_IMC_ERROR completed.

• RABAX: level LEV_RX_DATASET_CLOSE entered.

• RABAX: level LEV_RX_DATASET_CLOSE completed.

• RABAX: level LEV_RX_ERROR_SAVE entered.

• RABAX: level LEV_RX_ERROR_SAVE completed.

• RABAX: level LEV_RX_ERROR_TPDA entered.

• RABAX: level LEV_RX_ERROR_TPDA completed.

• RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

• RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

• RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

• RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

• RABAX: level LEV_RX_END entered.

• RABAX: level LEV_RX_END completed.

• RABAX: end no http/smtp

• RABAX: end RX_GOTO_RABAX

Time limit exceeded..

regards,

kumar

[Former Member]

Hello Raj,

If you are receiving timeout dumps after increasing so much the time out for the work process, it is a clear indication that the problem here is not with the time out, but with the selection criteria that you are making to run this job. If it is possible, you should break this job in several smaller jobs in order to be able to run this report properly. Remember that when you are increasing the run time of the work process, you can lead to hang situations in poor system performance situation.

Cheers,

Maurício

[Former Member]

You need to rebuild the indexes of tables related to SXMB_Moni

SXMSPMAST - master table

SXMSPEMAS

SXMSCLUR

and SXMSCLUP

This has solved my problem.

Please check and do the following:

.For rebuilding Please go to DB02 go to detailed analysis fill the Object Name & execute it,now click on Table Index,Select the Appropriate index,then go to detailed analysis,Now check the storage Quality of Index.Ideally it should be more than 75%.If the storage quality is quite less then go to index menu & rebuild Index.next day you will not get any warning related to this Index

- Sandy

[Former Member]

Hi,

Please see the SAP note..

Note 883732 - TIME_OUT dump before rdisp/max_wprun_time has elapsed

Regards

[Former Member]

Hello Raj

It all depends on the criteria which you select on the SXMB_MONI.

If your system is processing large volume of messages and you are not using TREX for indexing this will generally happen.

You need to use better selection criteria to look for the messages.

You need to also set the message retention parameter on Integration Engine so that message search can be made easier.

Regards

Vivek

[Former Member]

Hi Guys, Hi Sandeep,

I'm just one year late 🙂 but i wanted to give you a feed back about this solution.

Rebuilding our biggest indexes fixed our issue.

We did this rebuild first, furthermore we also compressed them using the BRTools.

Some of them have been reduced 10 times and some jobs (those which were running several days) are now taking less than a cuple of hours.

No Dev, no ABAP and no rdisp were modified!

I encounter 3 difficulties:

1. Find the related indexes (by the way if someone can give me advices or a fast method...)

2. The PSAPTEMP was not large enough (if you don't check, you 'll be in trouble 🙂 : if you don't use the parallel function, then your PSAPTEMP must be at least 2 times bigger than your bigger index.

3. Find a downtime.

Thank you Sandeep for this tip!

[former_member563787]

Program "CL_XMS_PERSIST================CP" has exceeded the maximum uninterrrupted runtime and has therefore been terminated.

******

Solved by updating the DB stats

[Former Member]

can you provide a Note no for this solution???