Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2002
    Posts
    12

    Unanswered: DARI process terminated abnormally

    hi,

    We are using java based stored procedures , procedures are working fine but some times we got " DARI process terminated abnormally ".

    Please let me know the root cause for this error.

    Thanks.

  2. #2
    Join Date
    Jun 2002
    Location
    UK
    Posts
    525
    We get the same problems occasionally. In our case, the SPs are usually written in SQL. I posted a thread a few days ago on this forum but haven't had any response.

    All I know is that in our case, the error arises when the SP returns a result set (opens a cursor with return) that is declared using recursive SQL.

    The error only seems to manifest when an SP has first been created or released to a new environment, or the database has been restarted. I'm not sure if those are the only instances but if it helps you track down the cause, I'd be pleased if you'd keep me informed.

    Cheers, Damian

  3. #3
    Join Date
    Sep 2002
    Posts
    12
    One of the cause for this error. If statements are not closed properly in the procedure we can expect this error. please update me if I am wrong.

  4. #4
    Join Date
    Jun 2002
    Location
    UK
    Posts
    525
    I'm not sure what you mean by "if statements are not closed properly". Do you mean the the Java callable statement, or do you mean cursors in the SP? For us, the cursor would have to remain open to return a results set to the calling application.

    Below is a simple example that encounters this problem immediately after compilation ( or I believe, a database restart ). I'd be interested to hear if you encounter the same probelm.

    CREATE TABLE FAMILY
    (CHILD_ID INT, PARENT_ID INT)
    @
    INSERT INTO FAMILY
    VALUES (1, 2), (2,3), (3,4), (4,5),(5,99)
    @
    CREATE PROCEDURE SP_DAI_TEST_DARI (
    P_CHILD_ID int
    )
    LANGUAGE SQL
    ------------------------------------------------------------------------
    -- SQL Stored Procedure
    ------------------------------------------------------------------------
    P1: BEGIN

    DECLARE c_ancestors CURSOR WITH RETURN FOR
    WITH parent(parent_id, prev_generation) AS
    (
    SELECT DISTINCT
    child_id,
    0
    FROM family
    WHERE child_id = p_child_id
    UNION ALL
    SELECT c.parent_id
    , p.prev_generation + 1
    FROM family c
    , parent p
    WHERE p.parent_id = c.child_id
    )
    SELECT DISTINCT parent_id, prev_generation
    FROM parent;

    OPEN c_ancestors;

    END P1
    @

  5. #5
    Join Date
    Oct 2002
    Location
    orlando, fl
    Posts
    3
    getting the same issue. see my store proc in http://dbforums.com/showthread.php?s=&threadid=331866. i'm watching both threads.

  6. #6
    Join Date
    Jun 2002
    Location
    UK
    Posts
    525
    I hadn't noticed before but I am finding, like you, that these SPs will also fail if they haven't been used for a while.

    Could this indicate an issue with buffering? (I'm not a DBA, so I'm not well up on these things!)

  7. #7
    Join Date
    Jun 2002
    Location
    UK
    Posts
    525
    Apparently this should be fixed in fixpak 8.
    Last edited by Damian Ibbotson; 11-29-02 at 07:30.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •