Tags: completes, database, error, executed, fails, job, message, microsoft, mysql, oracle, runs, server, sql, sqlstate, successfully

SQLSTATE 2203 Error 8115

On Database » Microsoft SQL Server

1,964 words with 1 Comments; publish: Mon, 02 Jun 2008 00:48:00 GMT; (250109.01, « »)

Hi,

I have this job that runs sometimes it completes successfully, sometimes it

fails.

When it fails it gives this error message -->

--

Executed as user: sqlagent. Arithmetic overflow error converting expression

to data type int.

[SQLSTATE 22003] (Error 8115) The statement has been terminated. [SQLSTATE

01000] (Error 3621).

The step failed.

--

When I did the research on all the codes in the error looks like one of the

statements such as -->

SELECT ABS(convert(int, -2147483648))

is causing the problem. The problem I am having is that stored procedure

that runs has many 'converts' and I do not know which one is causing the

problem. Can I setup some kind of monitor that will catch exact cause or

declared 'int' that it is unable to convert to "int"?

How should I go about it?

Thanks

-D

All Comments

Leave a comment...

  • 1 Comments
    • How do I setup job monitor?

      -D

      "D''Animal" wrote:

      > Hi,

      > I have this job that runs sometimes it completes successfully, sometimes it

      > fails.

      > When it fails it gives this error message -->

      > --

      > Executed as user: sqlagent. Arithmetic overflow error converting expression

      > to data type int.

      > [SQLSTATE 22003] (Error 8115) The statement has been terminated. [SQLSTATE

      > 01000] (Error 3621).

      > The step failed.

      > --

      > When I did the research on all the codes in the error looks like one of the

      > statements such as -->

      > SELECT ABS(convert(int, -2147483648))

      > is causing the problem. The problem I am having is that stored procedure

      > that runs has many 'converts' and I do not know which one is causing the

      > problem. Can I setup some kind of monitor that will catch exact cause or

      > declared 'int' that it is unable to convert to "int"?

      > How should I go about it?

      > Thanks

      > -D

      #1; Mon, 02 Jun 2008 00:49:00 GMT