job died but why?

[B D Jensen]

Hi!
Sometimes I have som jobs that dies.
In the job history I found such as:

Message
Executed as user: domain\batchuse r. ...r SET operation. [SQLSTATE
01003] (Message 8153) Warning: Null value is eliminated by an
aggregate or other SET operation. [SQLSTATE 01003] (Message 8153)
Warning: Null value is eliminated by an aggregate or other SET
operation. [SQLSTATE 01003] (Message 8153) Warning: Null value is
eliminated by an aggregate or other SET operation. [SQLSTATE 01003]
(Message 8153) Warning: Null value is eliminated by an aggregate or
other SET operation. [SQLSTATE 01003] (Message 8153) Warning: Null
value is eliminated by an aggregate or other SET operation. [SQLSTATE
01003] (Message 8153) Warning: Null value is eliminated by an
aggregate or other SET operation. [SQLSTATE 01003] (Message 8153)
Warning: Null value is eliminated by an aggregate or other SET
operation. [SQLSTATE 01003] (Message 8153) Warning: Null value is
eliminated by an aggregate or other SET operation. [SQLSTATE 01003]
(Message 8153) Warning: Null value is eliminated by an aggregate or
ot... The step failed

Message
Executed as user: domain\batchuse r. ...ted by an aggregate or other
SET operation. [SQLSTATE 01003] (Message 8153) Warning: Null value is
eliminated by an aggregate or other SET operation. [SQLSTATE 01003]
(Message 8153) Warning: Null value is eliminated by an aggregate or
other SET operation. [SQLSTATE 01003] (Message 8153) Warning: Null
value is eliminated by an aggregate or other SET operation. [SQLSTATE
01003] (Message 8153) Warning: Null value is eliminated by an
aggregate or other SET operation. [SQLSTATE 01003] (Message 8153)
Warning: Null value is eliminated by an aggregate or other SET
operation. [SQLSTATE 01003] (Message 8153) Warning: Null value is
eliminated by an aggregate or other SET operation. [SQLSTATE 01003]
(Message 8153) Warning: Null value is eliminated by an aggregate or
other SET operation. [SQLSTATE 01003] (Message 8153) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) The statement
has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.

Whats going on?
Normally I got errors catched and logged in table, but not in this
case...

Suggestions how to find root cause?
/Bjorn

[B D Jensen]

Re: job died but why?

Hi!
Sorry about the guessing game here.
I actually use batchlogging to avoid this game.

Running the same batchjob manual I got no error.
I hoped maybe it look similar to another kind of problem seen in
practice by people.
I now identified the proc that result in warning, which I now disabled
(SET ANSI_WARNINGS OFF, not that I'm happy about that,
but it should not harm in this case) Now I hope to see more from the
error message.
Remark that they are not exactly the same, or maybe they are, but it
seems that errormessage is truncated...

-thanks
Bjorn