on 11-15-2007 7:51 AM
Dear All,
The job SAP_COLLECTOR_FOR_PERFMONITOR is getting cancelled daily at 7.00 AM. It is scheduled to run hourly. All other times it finishes succesfully. But only 1 time at 7 it gets cancelled. The job log is :-
Date Time Message text Message class Message no. Message type
15.11.2007 07:00:17 Job started 00 516 S
15.11.2007 07:00:17 Step 001 started (program RSCOLL00, variant , user ID DDIC) 00 550 S
15.11.2007 07:00:38 ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE 00 671 A
15.11.2007 07:00:38 Job cancelled 00 518 A
the Dump is pasted below:-
ShrtText
Error when attempting to IMPORT object "HIST2".
What happened?
Error in ABAP application program.
The current ABAP program "RSORAT4M" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither
caught nor passed along using a RAISING clause, in the procedure
"AKT_DAY_HIST2" "(FORM)"
.
Since the caller of the procedure could not have expected this exception
to occur, the running program was 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 is different.
There are several possible reasons:
--- In the ABAP Dictionary, the type of the imported | field has changed. Make sure that the type of the imported | field matches the length of the Dictionary field. |
| If the data could not be restored from another source, this data
| must be read with the "old" structure, then converted and exported
| back with the new structure, so that future IMPORTs always work
| with the new structure.
|
--- A new program version is active, and it no longer matches the
dataset. Try to solve the error by generating the program "RSORAT4M" again
as follows:
In the SAP System, choose the transaction SE38. Enter the program
name "RSORAT4M". Then choose the "Activate" function.
===
It is saying
The data type is "I" in the dataset, but "P" in the program.
But it runs 23 times correctly except 1 time.
Can Anyone help me in this please
Thanks
Tajinder
Hi,
Thnaks all. I got it. But just a confusion that why it is getting cancelled just in a day and that too at a specific time. But all other times the job is successfull. What can be the reason for it
Thanks
Tajinder
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Kindly refer to OSS Note 997535 "DB02: Problems with History Data".
Regards
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can u please suggest me what will be the monikey here. below is the dump for that
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.
Thanks
tajinder
to clear the dump just follow the note 997535 which already given by madhu.
Please apply the following correction manually.
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
cheers,
-Sunil
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
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.