on 09-03-2014 5:53 AM
Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.
Hi Bharat,
Please share your SP level and dump that you are getting.
Divyanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
----------------------------------------------------------------------------------------------------
|Short text |
| Program "RSORA811" not found. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| There are several possibilities: |
| |
| Error in the ABAP Application Program |
| |
| The current ABAP program "RSCOLL00" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
| or |
| Error in the SAP kernel. |
| |
| The current ABAP "RSCOLL00" program had to be terminated because the |
| ABAP processor detected an internal system error. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|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 |
| On account of a branch in the program |
| (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT) |
| or a transaction call, another ABAP/4 program |
| is to be loaded, namely "RSORA811". |
| |
| However, program "RSORA811" does not exist in the library. |
| |
| Possible reasons: |
| a) Wrong program name specified in an external PERFORM or |
| SUBMIT or, when defining a new transaction, a new |
| dialog module or a new function module. |
| b) Transport error |
|Information on where terminated |
| Termination occurred in the ABAP program "RSCOLL00" - in |
| "LOOP_AT_SYSTEMS_AND_REPORTS". |
| The main program was "RSCOLL00 ". |
| |
| In the source code you have the termination point in line 535 |
| of the (Include) program "RSCOLL00". |
| The program "RSCOLL00" was started as a background job. |
| Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR" |
| Job Initiator.. " bharath" |
| Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.
Hi Bharath,
Did you make any changes to your system recently ?
There are few notes addressing same dump but are release and SP specific.
One of them is - refer: 1841778 - LOAD_PROGRAM_NOT_FOUND in RSCOLL00
Check is this qualifies the criteria.
If any job is failing at a particular time, you should look for other changes happening in you system.
Perhaps, any other job running causing problems.
Regards
Dear Experts,
The issue got resolved after deleting the entry from the table TCOLL. I have not seen any more SAP_COLLECTOR_FOR_PERFMONITOR failed jobs in our system.
Thanks for your suggestions..
Thanks,
Bharath.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bharath,
the report RSORA811 was removed from the table TCOLL as of certain basis release and this report is obsolete. RSORA811 was needed to reorganize old backup logs. You can use cleanup function of BRCONNECT instead of this report. You can schedule this action with DB13.
Regards,
Alwina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.