Testing stored procedure does not work from procedure tab - please explain
started a topic
almost 5 years ago
[This topic is migrated from our old forums. The original author name has been removed]
(I am using DbVisualizer Pro 9.0.9 running on Windows 7, connecting to DB2 9.5.7; please note that while I'm familiar with DB2, I have no previous experience with DB2 and DbVisualizer)
I tried to define a stored procedure. Using "StoredProcedures/Create Stored Procedure", and the Procedure editor, I made a simple procedure without parameters:
CREATE PROCEDURE "DB2RN"."DUMMY_EXP1"()
DELETE FROM DB2RN.DUMMY_EXP1;
Inside the Procedure Editor Tab, I find a green triangle which, when I hover over it, I see "execute stored procedure". When I click it, I get the error message
12:27:06 [@CALL - 0 row(s), 0.000 secs] 1) [Error Code: -440, SQL State: 42884] DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=DUMMY_EXP1;PROCEDURE, DRIVER=4.13.127. 2) [Error Code: -727, SQL State: 56098] DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-440;42884;DUMMY_EXP1|PROCEDURE, DRIVER=4.13.127. 3) [Error Code: -727, SQL State: 56098] DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-440;42884;DUMMY_EXP1|PROCEDURE, DRIVER=4.13.127
However, if I open a SQL commander tab instead, type the lines
and click the green triangle there, I don't get any error message, but
12:26:27 [@CALL - 0 row(s), 0.019 secs] Command processed. No rows were affected
... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 0.019/0.000 sec [0 successful, 1 warnings, 0 errors]
which is correct, because the table is empty.
My question: Why gets the procedure called properly from the SQL commander tab, but is not found when called from the procedure editor tab?
almost 5 years ago
[This reply is migrated from our old forums.]
Re: Testing stored procedure does not work from procedure tab - please explain
I cannot reproduce this problem. Please enable Show Detailed Error Messages in the Options area for the connection, and then open Tools->Debug Window and enable debugging for DbVisualizer. Then perform this operation again and include the debug output in your reply.