RAISE_EXCEPTION:Exception condition "ALREADY_RUNNING" raised

[mahesh_phegade1]

Dear All,

In our Production system,ABAP dump RAISE_EXCEPTION is generated on daily basis(15-20).

*************************************************************************************************

Runtime Errors RAISE_EXCEPTION

Date and Time 11.05.2009 13:56:19

Short text

Exception condition "ALREADY_RUNNING" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

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

A RAISE statement in the program "SAPLTHFB" raised the exception

condition "ALREADY_RUNNING".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

How to correct the error

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:

"RAISE_EXCEPTION" " "

"SAPLTHFB" or "LTHFBU09"

"TH_INIT_COLLECTOR_ARRAY"

or

"SAPLTHFB" "ALREADY_RUNNING"

or

"RSM13000 " "ALREADY_RUNNING"

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)

***************************************************************************************************************

BGD job RSM13005 frequency is every minute.

What be the solution to stop this dumps?

Thanks & Regards,

Mahesh Phegade

[Former Member · Accepted solution]

Mahesh

The problem is with the frequency of this job since it is scheduled every 1 minute,so when the next job starts,the previous job has not finished and hence this exception

what is the normal runtime of this job,I think you can reschedule to run every 2 mins

If that doesnt help,refer to Note 573036,it referes to your problem only

Rohit