cancel
Showing results for 
Search instead for 
Did you mean: 

Program Error "LOAD_PROGRAM_NOT_FOUND" for SAP_COLLECTOR_FOR_PERFMONITOR

Former Member
0 Kudos

Hi,

My standard job SAP_COLLECTOR_FOR_PERFMONITOR is failing. It was working before and now it is failing. The error message i get in ST22(ABAP SHORT DUMPS) are below. Please advise?

Runtime Errors LOAD_PROGRAM_NOT_FOUND

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.

-


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 "RSLDQREORG".

However, program "RSLDQREORG" does not exist in the library.

-


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.. "DDIC"

Job Number..... 11002002

Program code error

-


532 IF itcoll-sytyp = 'S' or sys_tabl-system_mark = 'X'.

533 DO itcoll-renum TIMES.

534 SUBMIT (itcoll-rname) AND RETURN.

>>>>> rinfo-host = sy-host.

536 rinfo-rname = itcoll-rname.

537 rinfo-rpara = space.

538 rinfo-datum = sy-datum.

539 rinfo-uzeit = sy-uzeit.

540 rinfo-ltext = space.

541 * write log entry

542 PERFORM proto_fill USING sys_tabl-name

543 sys_tabl-host

544 itcoll-rname

545 sys_tabl-error.

546 ENDDO.

547 ELSE.

Accepted Solutions (0)

Answers (2)

Answers (2)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Have you upgraded the kernel ?

Thanks

Sunny

Former Member
0 Kudos

Hi,

The SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR and the report RSLDQREORGis scheduled to run everyday and every hour as per the note 966309. It was working fine just until a few days.

Our Kernal is up to day and we haven't upgraded yet. We are running our kernal SAP_BASIS : 700, SAP_ABA: 700 and etc.

Could this be a ABAP issue with my previous error message pointing to line 535 code error? If this is not an ABAP issue, what could this be? How can i solve this issue?

Former Member
0 Kudos

This issue has been resloved. I had to do the below steps.

When you get the error message on the screen above, click on the ?(help) icon in the popup box that gives you an error. The expanded help text told you specifically if the job status got hose, go to OKEQN and put a =KILL in the OK (command) field. After that command, the user plan is unlocked and they can proceed.

Former Member
0 Kudos

Hello Thareq Yahya,

Can you please tell me more exactly how did you solve the problem ? You went into transaction OKEQN ? There I cannot find where to enter a KILL in the OK command.

Thank you in advance,

Catalin Diaconu

Former Member
0 Kudos

check the contents of TCOLL table via st03n whether the report RSLDQREORG has been scheduled to run or not as per below note, according to sap release

966309 Contents of table TCOLL in SAP_BASIS 700