SAP_COLLECTOR_FOR_PERFMONITOR failed

[Former Member]

Hello,

Std. Job SAP_COLLECTOR_FOR_PERFMONITOR failed.

Its job log says :

21.06.2007 20:10:27 Job started

21.06.2007 20:10:27 Step 001 started (program RSCOLL00, variant , user ID BATCHSCHE)

21.06.2007 20:10:29 Clean_Plan:started by RSDBPREV

21.06.2007 20:10:30 Clean_Plan:finished

21.06.2007 20:14:38 ABAP/4 processor: <b>CONNE_IMPORT_WRONG_COMP_TYPE</b>

21.06.2007 20:14:38 Job cancelled

same job is finished successfully: says:

21.06.2007 00:11:10 Job started

21.06.2007 00:11:10 Step 001 started (program RSCOLL00, variant , user ID BATCHSCHE)

21.06.2007 00:11:12 Clean_Plan:started by RSDBPREV

21.06.2007 00:11:12 Clean_Plan:finished

21.06.2007 00:11:15 Job finished

Can somebody pl. give a hint.

Regards,

Tushar

[Former Member · Accepted solution]

Hello,

Just found note 533020.

It talks about deleteing data from MONI table with afftected data id.

Im my case

IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY

here data id is DB.

Has anybosy tested it before.Thanks

Regards,

Tushar

[Former Member]

Thanks

[Former Member]

Hi Thushar,

Please check whether the program is active or not?

If not Select transaction SE38 in the SAP system. Enter the program name "RSORAT4M". Then activate the function 'Generate'.

Regards,

Suarj

[Former Member]

Hello JC Llanes,

Thanks. but what surprise is , It gets cancelled at perticular time.( same time ) every day. It is a hourly job and get canceled only two time at same time.

Can you suggest me what should i check for this.

Thanks in advance.

Regards,

Tushar

[Former Member]

Hi Tushar,

Yes, i got the same problem and i have resolved it for me by using the note 1000275. the problem is jobs are failing all the time. i got the same problem when i applied the new support package stack. but your problem looks strange at particular time only may be try applying the notes 1000275 and 533020 as our friend mentioned above.

Best Regards

Rao Narayana

[Former Member]

Hello JC Llanes,

This job get cancelled at the same time every day ( 07:11:13, 20:10:23 )

Also with same job log .It finished successfully exculding above timings.

Its strange. Any hint for this..

Regards,

Tushar

[Former Member]

Hi Thushar,

I would try to apply the note. It will solve the dump you attached.

Regards,

JC Llanes.

[Former Member]

Short text: Error when attempting to IMPORT object "HIST2".

What happened?

Error in the ABAP Application Program

The current ABAP program "RSORAT4M" had to be terminated because it has

come across a statement that unfortunately cannot be executed

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

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was

not caught in

procedure "AKT_DAY_HIST2" "(FORM)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

When importing the object "HIST2", the component no. 8 in the

dataset has a different type from the corresponding component

of the target object in the program "RSORAT4M".

The data type is "I" in the dataset, but "P" in the program.

How to correct the error

Try to find out why the type of the object should be different.

There are various possible options:

1. The type of the imported field has changed in the Data Dictionary.

Make sure that the type of the imported field matches the type

of the field in the Data Dictionary.

If the data cannot be restored from another source, the data must be

read by the 'old' structure, converted und again eported with the new

structure, so that future IMPORTs will always function with the new

structure.

2. A new program version is active, which no longer fits the dataset.

Try to solve the error generating the program "RSORAT4M" again. This

works as follows: Select transaction SE38 in the SAP system. Enter

the program name "RSORAT4M". Then activate the function 'Generate'.

Program code where error occured

FORM AKT_DAY_HIST2. " Aktualisiere Tage-Historie

PERFORM PREPARE_MONIKEY USING 36. " Lese Historie

>><b>>>> IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.</b>

IF SY-SUBRC <> 0.

System Details:

SCM 5.0

SAP_BASIS 700 Sp11

Regards,

Tushar

[Former Member]

Hi,

I recently solved this problem with Note 1000275.

Simply create the report (attached to the Note as txt file), and you can save the history data, delete it by applying Note 533020 you referred. Test again to see if short dump is solved. If not, maybe there´s another different corrupted monikey. Use the report again to save it, and delete it again...

After that, with the same report you can re-load your history data and nothing is lost.

Best Regards,

JC Llanes.

[Former Member]

Hi,

At Sap Note 73945 you'll find a solution for this issue.

Best Regards,

JC Llanes.