Question Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime) in Technology Q&A

Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Tue, 16 Apr 2013 11:57:46 GMT

Hi Guys,

On BI Production system I am getting ST22 : ABAP Run time error (TIME_OUT)

The Parameter value of rdisp/max_wprun_time = 3600 (1hr) which is maximum value. Even then we are getting around 20 to 30 Dumps. Can any suggest a Note, so that tell my application team to run their programs in Background.

Thanks in Advance for Reply.

Kernel release

720

Runtime Errors	TIME_OUT
Date and Time	15.04.2013 14:19:05

Short text

Time limit exceeded.

What happened?

	The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum
	permitted runtime without
	interruption and has therefore been terminated.

What can you do?

	Note down which actions and inputs caused the error.
	To process the problem further, contact you SAP system
	administrator.
	Using Transaction ST22 for ABAP Dump Analysis, you can look
	at and manage termination messages, and you can also
	keep them for a long time.

Error analysis

	After a specific time, the program is terminated to make the work area
	available to other users who may be waiting.
	This is to prevent a work area being blocked unnecessarily long by, for
	example:
	- Endless loops (DO, WHILE, ...),
	- Database accesses with a large result set
	- Database accesses without a suitable index (full table scan)
	The maximum runtime of a program is limited by the system profile
	parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this
	time limit is
	exceeded, the system attempts to cancel any running SQL statement or
	signals the ABAP processor to stop the running program. Then the system
	waits another 60 seconds maximum. If the program is then still active,
	the work process is restarted.

How to correct the error

	Programs with long runtime should generally be started as background
	jobs. If this is not possible, you can 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 unsuitable index: Check index generation.
	If the error occures in a non-modified SAP program, you may be able to
	find an interim solution in an SAP Note.
	If you have access to SAP Notes, carry out a search with the following
	keywords:
	"TIME_OUT" " "
	"CL_SQL_STATEMENT==============CP" or "CL_SQL_STATEMENT==============CM004"
	"EXECUTE_QUERY"

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

former_member206552 — Tue, 16 Apr 2013 13:28:35 GMT

hi vijay

here is a note about the rdisp/max_wprun_time parameter

Note 25528 - Parameter rdisp/max_wprun_time

the rule of thumb that we use at clients is any job that runs longer than 10 min has to run in the background, or else if everyone does that it will fill up the DIA processes and then no one can logon or work until they free up or system restart.

also review http://scn.sap.com/thread/278023

best regards

marius

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Tue, 16 Apr 2013 14:15:51 GMT

Hi Marius Burger,

Thanks for Quick Response and Reply

Few Queries

In SM21 I found that for DIA - 005 WP Time_out has occurred, when i check DIA WP 005 (I have attached Trace )

1. what exactly is this (RABAX: level LEV_RX_RFC_ERROR entered. A ** RABAX: level LEV_RX_RFC_ERROR completed.)

and

2. ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

Time

Type Nr Clt User

TCode Priority Grp N Text

15:07:11 DIA 005 100 800-13919	AB 0 Run-time error "TIME_OUT" occurred
15:07:11 DIA 005 100 800-13919	AB 1 > Short dump "130416 150711 bp1vci_BP1_10 800-13919 " created

A Tue Apr 16 15:07:11 2013

A ABAP Program CL_SQL_STATEMENT==============CP .

A Source CL_SQL_STATEMENT==============CM004 Line 19.

A Error Code TIME_OUT.

A Module $Id: //bas/720_REL/src/krn/th/thhiserv.c#10 $ SAP.

A Function ThTimeout Line 1830.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end RX_RFC

N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080]

N {root-id=51677E217E2002F4E10000000AC3FA18}_{conn-id=00000000000000000000000000000000}_0

C Tue Apr 16 15:17:23 2013

C Disconnected from 'BP1'

C Disconnected: con_hdl=1 ; appl_hdl=52660; appl_id="136.158.243.157.49897.130416113230"

B Disconnected from connection 1, con_da={R/3*,5003797}

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

former_member206552 — Wed, 17 Apr 2013 06:32:39 GMT

hi vijay

1. the suggestions i could find about this problem was to update the kernel

2. please have a look at http://scn.sap.com/thread/1584075

best regards

marius

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Mon, 03 Jun 2013 21:02:06 GMT

Hi Vijay,

We are recently facing the same "TIME_OUT" dump for the same program in ST22. Can you please let me know what exactly you did to fix your issue ?

Thanks in advance.

Thanks & Regards,

Mithun

P.S. - Can you please let me know how did you reach to the job name and the corrective actions performed.

Message was edited by: Mithun Nair

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

former_member206552 — Wed, 05 Jun 2013 10:34:56 GMT

Hi Mithun,

In ST22 it will tell you which job is causing the error.

double click on the TIMEOUT error and click on USER AND TRANSACTIONS on the left, under PROGRAM : program_name

follow the answer marked as correct

hope it helps

best regards

marius

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Thu, 06 Jun 2013 19:23:15 GMT

Hi Marius,

Thanks for your prompt reply. I went through the parameter info.

I understand that, in my case, the job which is apparently taking a long time to process in the foreground is being cut short by this "rdisp/max_wprun_time" parameter (and hence, the Time_out dump in ST22) to optimize the usage of the dialog processes and free them up. Considering that the parameter value cant be increased from the present limit, I believe the next fix is to convert this time-consuming program running in the foreground to a background process.

Can you please help me with the corrective actions (meaning Job name or report name etc) which need to be converted from a forground process to a Background process, and the exact way to do so. We are getting the exact same dump as in the heading of this thread.

The ST22 in our SP1 system contains only Time_out dumps (10 per day for that matter) and we're trying to fix it up. Appreciate your help. Thanks in advance.

Regards,

Mithun

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

former_member206552 — Mon, 10 Jun 2013 04:36:31 GMT

Hi Mithun

Is the job being manually kick off in sa38/se38 ?

if this is the case it's quite easy

here is also a tread :http://scn.sap.com/thread/641412

Best Regards

Marius

Best Regards

Marius

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Mon, 10 Feb 2014 10:10:41 GMT

Hi all,

I'm trying to create a CHIP in Application configuration.

When double click on the Application Configuration and test it in "Administration Mode" its navigating me to a page customizing page.

Here any click on any tab is keeping me waiting for 15-20 min and ultimately gives and error message as "Time limit exceeded".

Can anyone help me this???

Thanks in advance

Supriya.

Re: Runtime Errors : TIME_OUT (The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum permitted runtime)

Former Member — Wed, 21 Sep 2016 12:18:19 GMT

Hi Vijay,

I got the same error today on my SAP ECC system while executing ABAP report to calculate the HANA Memory Size, I have fix this error just now by following below steps:

You also can try and fix your system error with easy steps.

Steps to resolve Timeout error for CL_SQL_CONNECTION=CP ABAP Program.

I hope this will help you to fix your system error as well .