Skip to Content
author's profile photo Former Member
Former Member

COMPUTE_INT_TIMES_OVERFLOW & CX_SY_ARITHMETIC_OVERFLOW

I submit that a dump on my system, when running a job SAP_COLLECTOR_FOR_PERFMONITOR,

===========================================================================

JOb Error:

===========================================================================

Job started

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

Clean_Plan:Cleanup of DB13 Plannings

Clean_Plan:started by RSDBPREV

Clean_Plan:Jobs in System R3D werden bereinigt

You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> R3D <Windows authentication> 03)

Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error

Clean_Plan:terminated with error

REASON=Job error

ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW

Job cancelled

===========================================================================

ST22 "Abap Dump"

===========================================================================

Runtime Errors COMPUTE_INT_TIMES_OVERFLOW

Exception CX_SY_ARITHMETIC_OVERFLOW

Date and Time 03.06.2009 08:43:12

Short text

Whole number overflow on multiplication.

What happened?

Error in the ABAP Application Program

The current ABAP program "RSMSQSNP" 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_ARITHMETIC_OVERFLOW', was not

caught in

procedure "GET_ELAPSEDSECS" "(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:

In the current program "RSMSQSNP", multiplying the numbers 733562 and

86400 (using the operation '*' or 'MULTIPLY') resulted in a value

greater than 2147483647 or smaller than -2147483648. This

results in a whole number overflow.

to correct the error

It may be possible to break the current process down into subprocesses

so that only smaller values occur.

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

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:

"COMPUTE_INT_TIMES_OVERFLOW" "CX_SY_ARITHMETIC_OVERFLOW"

"RSMSQSNP" or "RSMSQSNP"

"GET_ELAPSEDSECS"

System environment

SAP-Release 700

Application server... "srvctrsapd01"

Network address...... "200.200.1.2"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x Intel 80686"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 15

Shortdump setting.... "full"

Database server... "SRVCTRSAPD01"

Database type..... "MSSQL"

Database name..... "R3D"

Database user ID.. "r3d"

Char.set.... "Spanish_Spain.1252"

SAP kernel....... 700

created (date)... "Aug 25 2008 01:11:49"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQL_Server_8.00 "

Patch level. 175

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Termination occurred in the ABAP program "RSMSQSNP" - in "GET_ELAPSEDSECS".

The main program was "RSMSQSNP ".

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

of the (Include) program "RSMSQSNP".

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

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

Job Initiator.. "MGBAUTE"

Job Number..... 07431004

The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"

occurred in

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

declared

in the RAISING clause of its signature.

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

172 of the (Include program "RSMSQSNP ".

Thank and regards for your help.

Gustavo Gonzalez.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 09, 2014 at 06:06 PM

    I assume by now you resolved this problem -- I just had the same thing in my Solution Manager 7.1 system, and the solution was the manual steps from Note 1908010. I found Note 1738605 which describes the same solution to the same problem as well, but doesn't claim it as being Solution Manager specific. Essentially, the solution is to deschedule the SAP_COLLECTOR_FOR_PERFMONITOR job from your productive client, and then reschedule it as user DDIC in client 000 (program RSCOLL00, no variant, hourly).

    --Matt

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 03, 2009 at 05:08 PM

    > An exception occurred that is explained in detail below.

    > The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not

    > caught in

    > procedure "GET_ELAPSEDSECS" "(FORM)", nor was it propagated by a RAISING

    > clause.

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

    Try the following:

    - open a browser

    - enter "http://service.sap.com/notes"

    - enter "GET_ELAPSEDSECS" as search term

    Markus

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.