HIT 3621 When running Job

  • I had a job running to call the stored procedure to perform action. Normally this action took around 18mins but it run till 2mins hit 3621, the session is terminated.

    Can I know in what situation will hit this error?

  • chris92mars (11/2/2015)


    I had a job running to call the stored procedure to perform action. Normally this action took around 18mins but it run till 2mins hit 3621, the session is terminated.

    Can I know in what situation will hit this error?

    A foreign key or duplicate key conflict. What is the error message immediately before the 3621? That will give you more detail, including line number.

    “Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

    For fast, accurate and documented assistance in answering your questions, please read this article.
    Understanding and using APPLY, (I) and (II) Paul White
    Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

  • we'd need more details to really help.

    my research implies it's due to bad logic in the procedure:

    when i googled "sql error 3621"

    this link implied that the error was returned due to an int variable being assigned a value greater than an int max:

    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33213

    this link lists two concrete and one vague cause, all in code. Division by 0 in your application,Entry of a duplicate row during use of your application,Other illegal functions in your application

    http://www.lcard.ru/~nail/sybase/error/26595.htm

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Sorry guys, I found the reason why I hit the error.

    It is due to I inserting a empty value to a not nullable field.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply