It occurs when an opened cursor contains no data and there is only one viable workaround. It is fixed for Toad 12.9. On the Output Options tab disable the option to show cursor data. You could also close your cursor in your PL/SQL if it contains no data, but this is not a good option unless your PL/SQL is just sandbox code.
On 01/15/2016 02:39 PM, Allen.Zolondek wrote:
Execute Procedure (that returns multiple sys_refcursor results) throws ‘Dataset not in edit or insert mode’ exception
Thread created by Allen.Zolondek
From the Toad Schema Browser, I get a ‘Dataset not in edit or insert mode’ when I right-click a stored procedure (that returns multiple sys_refcursor results), select ‘Execute Procedure’, select ‘Fetch cursor data’, and click OK.
I never received this exception in previous versions of Toad. It first appeared only after I upgraded to my Toad for Oracle Xpert 64-Bit to 18.104.22.168.
If I click OK on the exception message (one gets generated for each sys_refcursor returned), the procedure executes and I can view the cursor results successfully. But clicking the exception message for each returned result is very inefficient.
Is there a setting that I can configure to suppress this exception?
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
this post as spam/abuse.