AFAIK, Stored Procs sometimes intentionally leave Cursors
open, so that the callers at the client side can fetch the results.
If your Stored Proc does this intentionally, CLOSE CURSOR is
no option, because the client will not be able to fetch the results
after that. I think, in this case you depend on the COMMIT that
is issued by the client (or a DB2 timeout).
Kind regards
Bernd
Am 08.02.2015 um 08:03 schrieb Z.Z.:
>
>
> hi
>
> I have a StoredProcedure that uses CURSOR WITH HOLD, How can I release its connection?
>
> best regards
>
> z.
>
|