Error : CONNE_IMPORT_WRONG_COMP_TYPE

[Former Member]

Hi,

We update the SP stack on Solution manager before 15 days, I observed that Job “SAP_COLLECTOR_FOR_PERFMONITOR” failed only at 07:00 o’clock & at 20:00 o’clock, rest of the times Job is finished successfully, When I checked the Job log it give following details.

Job started

Step 001 started (program RSCOLL00, variant , user ID DDIC)

ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE

Job cancelled

I am not getting why the job is cancelled at the particular time & rest of the times it completed successfully? Please suggest what I should do.

Regards,

Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

Can you please post the corresponding ABAP dump.

Regards.

Ruchit.

[Former Member · Accepted solution]

Also please check this:

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Ruchit,

The abap dump is as follows

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.

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.

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'.

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:

"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"

"RSORAT4M" or "RSORAT4M"

"AKT_DAY_HIST2"

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)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"AKT_DAY_HIST2" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

o prevent the exception, note the following:

Information on where terminated

Termination occurred in the ABAP program "RSORAT4M" - in "AKT_DAY_HIST2".

The main program was "RSORAT4M ".

In the source code you have the termination point in line 163

of the (Include) program "RSORAT4M".

The program "RSORAT4M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 06004808

The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"

occurred in

procedure "AKT_DAY_HIST2" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "RSORAT4M "; its source code begins in line

161 of the (Include program "RSORAT4M ".

[Former Member · Accepted solution]

Hi Ruchit,

I gone through the thread, it has the same problem as mine.

But I am unable to find the moni key. When I try to find in ABAP dumps I get the following,

Directory of Application Tables

Name Date Time Lngth

Val.

Program RSORAT4M

SYST 16.12.2004 20:31:11 00002408

00000000x010000000000000000000

MONI . . : : 00002920

DB--SMD days h/2 0000 Vx02ÿx06x02x01x02

Is this a mony key?

Please suggest

Regards,

Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

Can you post the code part of the ABAP dump. I however get the feeling that the moni key is DB. I want to still confirm with the code though.

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Rajesh,

I think SMD is your system id. I think you need to delete all the entries with the key DB--SMD days h/2 .

But may be entires like DBSMD days h/3 or DBSMD days h/1 also need to be deleted. That is why I am looking for the code.

In any case have a back up ready before deletion. An OSS note is mentioned in the thread for that.

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Ruchit,

Thanks for reply, the code is as follows & yes ID is DB

Line SourceCde

133

134 REFRESH HIST2_DAY.

135 CLEAR HIST2_DAY.

136

137 HIST2_DAY-SIZE = TD110-TSSI.

138 HIST2_DAY-FREE = TD110-TSFR.

139 HIST2_DAY-USED = 100 - TD110-TSFRP.

140 HIST2_DAY-TABLES = TD110-TANO.

141 HIST2_DAY-INDICES = TD110-TINO.

142 HIST2_DAY-TSIZE = TD110-TASI.

143 HIST2_DAY-ISIZE = TD110-TISI.

144

145 * PERFORM new_analysis_db.

146 HIST2_DAY-DATE = DATE.

147 HIST2_DAY-TIME = TIME.

148 APPEND HIST2_DAY.

149 ENDFORM.

150 *----

-

---

Beschaffung neuer Analyse-Daten für Historien <<<

151

152 *----

-

---

Historie, Tage >>>

153 FORM DELETE_AKT_DAY_HIST2.

154 DATA: FLAG VALUE ' '.

155 LOOP AT HIST2.

156 IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.

157 ENDLOOP.

158 IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.

159 ENDFORM.

160

161 FORM AKT_DAY_HIST2. " Aktualisiere Tage-Historie

162 PERFORM PREPARE_MONIKEY USING 36. " Lese Historie

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

164 IF SY-SUBRC <> 0.

165 REFRESH HIST2. CLEAR HIST2.

166 PERFORM LOGBUCH_INIT USING 1.

167 PERFORM TRANSFORM_ALL_HISTORIES. " Strukturaenderung fuer Dynami

168 PERFORM PREPARE_MONIKEY USING 36. " Lese Historie

169 IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.

170 ENDIF.

171 READ TABLE HIST2 INDEX 1.

172 IF SY-SUBRC <> 0.

173 REFRESH HIST2. CLEAR HIST2.

174 PERFORM LOGBUCH_INIT USING 1.

175 ENDIF.

176 PERFORM DELETE_AKT_DAY_HIST2. " Delete aktuellen Tag

177 LOOP AT HIST2_DAY. " Füge neue Analyse an

178 MOVE-CORRESPONDING HIST2_DAY TO HIST2.

179 APPEND HIST2.

180 ENDLOOP.

181 ADD 1 TO LOGBUCH-ANZDAYS.

182 MOVE DATE TO LOGBUCH-LASTDAY.

What I should do?

Regards,

Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

Please proceed accordingl to OSS notes 1000275 and 533020 .

Also check the SDN thread link for reference purposes

I hope it will solve the issue for you certainly.

Regards.

Ruchit.

[former_member2300 · Accepted solution]

transaction ST03N then >COllector and perfomance DB->perfomance DB->Monitor DB->Contents-->then i Selected delete all MONI data,at first and afterwards i used Delete REILD there

[Former Member · Accepted solution]

Dear Rajesh,

Has your issue been resolved , please let me know the solution as iam alsong facing the same issue. Can you please help me out . Please could you give me the step by step.

regards

divya

[Former Member · Accepted solution]

Divya,

Please follow note 997535 to delete the monikey. Below are the steps to do it as per the Note.

1. Go to transaction ST03N

2. Change user from 'Administrator' to 'Expert Mode'.

3. Go to Collector and performance analysis -> Performance database

-> Monitoring database -> Contents

4. Search where further info contains the string "h/2"

like the following monikeys:

- 'days h/2'

- 'weeks h/2'

- 'months h/2' (see point 3 below)

5. Double click on each, so that they become red and show ** delete

6. Finally SAVE

This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.

If you need to archive the data before deletion follow note 1000275, create the Zprogram and follow the steps. You can also check note 533020, if that meets your runtime error.

Note 997535 - DB02: Problems with History Data.

Note 1000275 - DB02: history data backup procedure.

Note 533020 - CONNE_IMPORT_WRONG_COMP_TYPE with IMPORT FROM DATABASE MONI

-Mahesh

[former_member313870]

thanks a lot for the information... this worked very well...

Kapil Jain.

Sr. Basis Consultant.

Jaipur 992 885 7700