Resource Error. No batch process available. Process Terminated.

[harshil_joshi]

Dear All,

After reading so many threads and blogs and many more things like ( http://scn.sap.com/thread/947686, http://scn.sap.com/thread/1526356 , http://scn.sap.com/thread/1196428, http://saperrors.com/2011/11/17/resource-error-no-batch-process-available-process-terminated/ )

I can not able to solve this error permanently.

First I need to know whether it is BASIS problem or BW problem?

I went through SM50, ST22, SM21, SM37 T Codes and every where found that

No Background Process Available

Category: ABAP Programming Error

Run Time Errors     : TIME_OUT

Time Limit Exceeded.

Error Analysis:

After Specific time, the program is terminated to make the work area available to other users who may be waiting.

Please help to sort out this problem permanently.

Kind regards.

[Former Member · Accepted solution]

Hai Harshil,

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

(or)

The TIMEOUT errors are most likely because your server is too slow and lack in resources or programs are not optimized, which results in the work process exceeding rdisp/max_wprun_time and in case of SAPGUI connections rdisp/gui_auto_logout. You may want to check the values of these two parameters. However, don't set them to infiniti either, because you don't want a situation where all work processes are running forever.
or
 
1. Time out exception (increase the value for timeout parameter value in RZ10 or restrict the data selection)
2. SAPSQL_STMNT_TOO_LARGE - The ABAP runtime environment does not support large WHERE conditions (> 64 KB). If possible, large WHERE conditions are subdivided into several smaller WHERE conditions.
3. CX_SY_FILE_OPEN_MODE - Open Dataset exception.
 
or
For time-out dumps you have to run your report in background work.

best regards

[former_member214415]

Hi Harshil,

See your error is "Time Out".So this error raise when we execute a program in foreground and after a period of time a "short dump" occur on the screen indicating an error "Time Out". The system has reached at time limit for running program in foreground. The SAP system setting for the timeout is too short.

So run the transaction RZ11 and enter a parameter rdisp/max_wprun_time. By default it is set to 600 seconds, however if you have long running jobs then you can set it to 1200 or 1800 seconds.

or

you should run the jobs in background.

Thanks,

Swapna Jain

[Former Member]

Check if you are executing multiple DSO Activation in Parallel.  If you are executing multiple DSO Data Activation processes in parallel then you need to change the max number of Parallel DSO Activation processes in the system.

Follow the below steps

RSA1–>Administration–>

Current Settings–>Batch Manager–>

Settings for Parallel Processing–>

select ” ODS Activation”–>

click on “Parameter settings” –> change the number of processes to 1 or 2 or 3  and make sure you have enough background processes.

[KamalMehta]

Hi Harshil,

This is more of Basis related rather BW.

Depending upon the configuration of the back ground and dialogue jobs in the system it checks the availability of the same at the time BW job was ran . As it was not able to find any free Dialogue or Background processes was available and also as the Max wait time was exceeded so the job was failed.

Please coordinate with Basis team for the same.

Thanks

[MGrob]

Hi

It sounds more like your basis team did not set the amouunt of DIA and BDG correctly than a BW issue itself.

Make sure that there are sufficient background processes (type BTC) available to process the BW processes in the system in parallel. More background work processes (approximately 50% more) are needed than without BW background management.

Have you checked this help.sap input?

http://help.sap.com/saphelp_nw73/helpdata/en/48/807834109a1b5ae10000000a42189c/content.htm

It also explains what process types are supported by the background process management

hope it helps

Martin

[RamanKorrapati]

Hi Joshi,

Error indicates there is no required application servers to process your request.

With help of BW team , basis team need to configure required DIA and BGD processors at prod bw.

For each and every request to process in SAP, we need DIA or BGD processors free at that time, otherwise our request will won't run.

DIA-Dialog process, when we trigger infopack immediately, DIA processors will process this request if free at that time

BGD - When we load thru process chains, most of BGD will be busy.

BW team and Basis need to discuss, maintain required processors at prod.

Always need to run loads where there is no burden on Prod servers.

Daily loads need to be finish before start of working hours. if your going run any loads at working hours time, you can check at SM50, if any process status as waiting, you can trigger your load, it will run. if all process status as running then your request will won't run  upto finishing of existing requests.

Thanks

[Former Member]

Hi Raman,

I too get the same error,i have 17 millions record in the DSO while activating i am getting error,I checked the background jobs

Error:

Resource error. No batch process available. Process terminated

i have attached error screenshot

Vickram

[RamanKorrapati]

Have you tried all replies which explerts suggested?