B
bclegg
Hi,
Does anybody know if it possible to force Oracle to release cursors that
have been generated when servicing a vb.net stored procedure call?
ie My app makes a call that populates a field in a datagrid row
This means the number of calls depends on the amount data in the grid.
The cursors are left open by Oracle and Oracle creates a new cursor for
each call, so it does take more than a few grid refreshes before you hit
ORA-1000 'Too many cursors'
Is there a way of forcing oracle to reuse the cursors.
I am asking this question here because I am expecting that this would be
provided by the Oracle Client rather than having to alter a parameter in
the database directly.
thanks
Bob
Does anybody know if it possible to force Oracle to release cursors that
have been generated when servicing a vb.net stored procedure call?
ie My app makes a call that populates a field in a datagrid row
This means the number of calls depends on the amount data in the grid.
The cursors are left open by Oracle and Oracle creates a new cursor for
each call, so it does take more than a few grid refreshes before you hit
ORA-1000 'Too many cursors'
Is there a way of forcing oracle to reuse the cursors.
I am asking this question here because I am expecting that this would be
provided by the Oracle Client rather than having to alter a parameter in
the database directly.
thanks
Bob