TIME_OUT dumps by user SAPGRC

[Former Member]

Hi All,

We are receiving Time_Out dumps in ECC system with user name SAPGRC every hour.

Below is the ST22 log of the dump,

Runtime Errors	TIME_OUT
Date and Time	03.09.2012 23:21:03

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short text	|
|	Time limit exceeded.	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened?	|
|	The program "/GRCPI/CL_GRIA_LOG============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 600 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" " "	|
|	"/GRCPI/CL_GRIA_LOG============CP" or "/GRCPI/CL_GRIA_LOG============CM008"	|
|	"GET_STAD_LOG"	|
|	|
|	If you cannot solve the problem yourself and want to send an error	|
|	notification to SAP, include the following information:	|
|	|
|	1. The description of the current problem (short dump)	|
|	|
|	To save the description, choose "System->List->Save->Local File	|
|	(Unconverted)".	|
|	|
|	2. Corresponding system log	|
|	|
|	Display the system log by calling transaction SM21.	|
|	Restrict the time interval to 10 minutes before and five minutes	|
|	after the short dump. Then choose "System->List->Save->Local File	|
|	(Unconverted)".	|
|	|
|	3. If the problem occurs in a problem of your own or a modified SAP	|
|	program: The source code of the program	|
|	In the editor, choose "Utilities->More	|
|	Utilities->Upload/Download->Download".	|
|	|
|	4. Details about the conditions under which the error occurred or which	|
|	actions and input led to the error.	|
|	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|System environment	|
|	SAP-Release 701	|
|	|
|	Application server... ""	|
|	Network address...... ""	|
|	Operating system..... "Windows NT"	|
|	Release.............. "6.1"	|
|	Hardware type........ "4x AMD64 Level"	|
|	Character length.... 16 Bits	|
|	Pointer length....... 64 Bits	|
|	Work process number.. 0	|
|	Shortdump setting.... "full"	|
|	|
|	Database server... ""	|
|	Database type..... "MSSQL"	|
|	Database name..... ""	|
|	Database user ID.. ""	|
|	|
|	Terminal.......... " "	|
|	|
|	Char.set.... "C"	|
|	|
|	SAP kernel....... 701	|
|	created (date)... "Nov 21 2011 23:49:55"	|
|	create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"	|
|	Database version. "SQL_Server_8.00 "	|
|	|
|	Patch level. 170	|
|	Patch text.. " "	|
|	|
|	Database............. "MSSQL 9.00.2047 or higher"	|
|	SAP database version. 701	|
|	Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows	|
|	NT 6.0, Windows NT 6.1"	|
|	|
|	Memory consumption	|
|	Roll.... 16192	|
|	EM...... 8379680	|
|	Heap.... 0	|
|	Page.... 0	|
|	MM Used. 2755696	|
|	MM Free. 5621136	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|User and Transaction	|
|	Client.............. 100	|
|	User................ "SAPGRC"	|
|	Language Key........ "E"	|
|	Transaction......... " "	|
|	Transactions ID..... "C00BF6E1A2C0F1C18C2800155D000F66"	|
|	|
|	Program............. "/GRCPI/CL_GRIA_LOG============CP"	|
|	Screen.............. "SAPMSSY1 3004"	|
|	Screen Line......... 2	|
|	|
|	Information on caller of Remote Function Call (RFC):	|
|	System.............. ""	|
|	Database Release.... 702	|
|	Kernel Release...... 720	|
|	Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)	|
|	Call Type........... "synchron and non-transactional (emode 0, imode 0)"	|
|	Inbound TID.........." "	|
|	Inbound Queue Name..." "	|
|	Outbound TID........." "	|
|	Outbound Queue Name.." "	|
|	|
|	Client.............	|
|	User................ "WF-BATCH"	|
|	Transaction......... " "	|
|	Call Program........."CL_GRAC_AD_SUPER_USER_RFC=====CP"	|
|	Function Module..... "/GRCPI/GRIA_TRAN_GET_LOG"	|
|	Call Destination.... ""	|
|	Source Server....... ""	|
|	Source IP Address... ""	|
|	|
|	Additional information on RFC logon:	|
|	Trusted Relationship " "	|
|	Logon Return Code... 0	|
|	Trusted Return Code. 0	|
|	|
|	Note: For releases < 4.0, information on the RFC caller are often	|
|	only partially available.	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Information on where terminated	|
|	Termination occurred in the ABAP program "/GRCPI/CL_GRIA_LOG============CP" -	|
|	in "GET_STAD_LOG".	|
|	The main program was "SAPMSSY1 ".	|
|	|
|	In the source code you have the termination point in line 69	|
|	of the (Include) program "/GRCPI/CL_GRIA_LOG============CM008".	|

----------------------------------------------------------------------------------------------------

Could anyone help me how to troubleshoot this issue and fix this?

Thanks in advance.

[JPReyes]

We are not magicians, without further info the only thing i can tell you is that the program is timing out because it reaches the value of parameter rdisp/max_wprun_time.

What is this user running? I presume SAPGRC is not a dialog user so can you be more specific?, also you migth need to run that as a background job.

Regards, Juan

[Former Member]

Hi Juan ,

I know, we are administrators but I am not sure what information can I provide, and hence could not provide much more information on this.  As you predicted SAPGRC is not a dialog user , it is a Communication Data user.

My assumption of this dump is that some activity in SAP GRC system is triggering these dumps in ECC server, but I am unable to figure it out and how to proceed.

Another interesting thing I observed is that we have 4 application servers and this dump is occurring only on a particular application server.

Please let me know what additional information can I provide, I will happy if you could assist me

Thanks,

Pradeep

[JPReyes]

Another interesting thing I observed is that we have 4 application servers and this dump is occurring only on a particular application server.

Compare  parameter rdisp/max_wprun_time in all your instance profiles... 600 seconds is quite a short time_out..

Regards, Juan

[Former Member]

Hello Pradeep,

Check rdisp/max_wprun_time value on that particulat App server.

Goto SM21 for more info about the error on that App server. Generally before dump ,you can find some hint in SM21. Ckeck out for failed b/g job.

Cheers,

Vishal

[Former Member]

Hi Juan , Vishal,

Thanks for the inputs, I am working on the parameter value.

I will update you the results soon.

Regards,

Pradeep

[Former Member]

Hi Pradeep,

It seems the job is failing to collect STAD data for your application. Please evaluate OSS#Note 1626238 - Long time taken by transaction usage log collection

Regards,

Samik

[Former Member]

Hi Samik,

I have gone through this Note our GRC system already has GRCPINW component on release V1000_700 and level 6. So this note is not valid for our system.

Thanks,

Pradeep

[Former Member]

Hi Pradeep,

Did you solve this issue.

If so, can you please share the solution.

We are facing a similar issue.

Any help is much appreciated!

Best Rgds,

Jaravuy

[Former Member]

hi there are 2 possiblities. 1. time out parameter. 2. your system Program........."CL_GRAC_AD_SUPER_USER_RFC=====CP"                        OR Function Module..... "/GRCPI/GRIA_TRAN_GET going to infinite loop. just debug the program if u can or debug with help of ABAP team and also who changed this program last time.  that leads to this

[Former Member]

Use SAPGUI_PROGRESS_INDICATOR function module in the Loop when you are appending final value into the table.

Warm Regard!!

Jenish Tailor

[Former Member]

Hi Jinesh,

I am not sure how to do it.. could you please explain.

Thanks,

Pradeep

[Former Member]

HI,

Please tell me your development scenario then i will explain you with example code.

[Former Member]

Hi Jinesh,

I am from Basis team, and I am not aware of these concepts.

I will consult an ABAP resource.

Thanks,

Pradeep