on 08-04-2009 9:06 PM
Good evening everybody,
The job SAP_COLLECTOR_FOR_PERFMONITOR is being canceled hourly with the log below:
Date Time Message text Message class Message no. Message type
04.08.2009 15:30:55 Job started 00 516 S
04.08.2009 15:30:55 Step 001 started (program RSCOLL00, variant , user name DDIC) 00 550 S
04.08.2009 15:30:57 ABAP/4 processor: CONVT_OVERFLOW 00 671 A
04.08.2009 15:30:57 Job cancelled 00 518 A
The dump generated in the ST22 is CONVT_OVERFLOW
Overflow when converting from 15362394
What happened?
The current ABAP/4 program "RSHOST2M " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Everyone can help me to solve this issue? Our SAP version is R/3 4.6C.
Best Regards,
Fábio Karnik Tchobnian
> Everyone can help me to solve this issue? Our SAP version is R/3 4.6C.
A good idea if you encounter such errors is to do as advised in the dump - search for notes
Searching for "RSHOST2M" and "CONVT_OVERFLOW" leads to exactly one note:
Note 903220 - Short dumps CONVT_OVERFLOW in RSHOSTDB or RSHOST2M
Does that apply?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Friend,
Thanks for your help.
I apllied the part below from the note 903220
-
-
To remove the corrupted data in table MONI:
1. Call transaction ST03
2. With Goto -> Performance database -> Contents of Database
3. Select entry you want to delete
4. Further info will be '** delete**'
5. Confirm the delete
05.08.2009 Page 2 of 2
SAP Note 903220 - Short dumps CONVT_OVERFLOW in RSHOSTDB
or RSHOST2M
A sufficient way to find out which entries to delete would be:
- check when the short dump occured first
- delete the OS entries from MONI since the day before the first
short dump occured
-
-
:
The job SAP_COLLECTOR_FOR_PERFFMONITOR now is not being canceled anymore , however it is happening the same dump dump from a differente program after the job is finished as the log below from the ST22
ABAP runtime errors CONVT_OVERFLOW
Occurred on 05.08.2009 at 15:50:38
Overflow when converting from "-3.10504e+231"
What happened?
The current ABAP/4 program "SAPLSTUW " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
When attempting to convert the value "-3.10504e+231",
an overflow occurred.
Do you have some advice?
Best Regards
Fábio Karnik Tchobnian:
i applied the note 1374239 code.
I tried to delete the entries acordding to note 1374239 by ST03 but i could not delete after i market *delete*
The path that i entered was ST03 ==> Goto ==> Performance Database ==> Contents of Database. Double-clicking an entry
selects it for deletion.
The entrie is the entrie below that is being showing in the dump
L MONI 920 SD sapdb0#2**D 200908180000
Best Regards,
Fábio Karnik Tchobnian.
Edited by: Fio Tchobnian on Aug 28, 2009 11:20 PM
The job is working Ok but the ST03 are not working
The error from ST03 is :
11.09.2009 The statistic file processing is locked
The ST22 dump error:
The termination occurred in the ABAP/4 program "SAPLSTUW " in
"ADD_RECORDS_TO_RFC_STATISTIC".
The main program was "SAPMSSY1 ".
The termination occurred in line 309
of the source code of program "LSTUWF02 " (when calling the editor 3090).
Any idea?
Best Regards,
Fábio Karnik Tchobnian
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.