Page 1 of 1
ODAC-NET: maximum open cursors exceeded
Posted: Thu 03 Aug 2006 07:02
by Belitski
Hi,
i get ORA-01000 working over ODAC with NET=TRUE,
while there is no error when NET=FALSE.
I have seen similar post from RR a few month ago but there was no solution suggested.
Does anybody have an idea what could it be?
Thank you in advance,
Vladimir
Posted: Mon 07 Aug 2006 12:24
by Challenger
We reproduced this situation and now we are investigating it.
Posted: Mon 07 Aug 2006 15:09
by dstrenz
challenger wrote:We reproduced this situation and now we are investigating it.
I noticed the same problem. To add to this, I changed the TOraQuery option AutoClose = True and am getting AV's in the CommitUpdates when using NET option. Works fine using oci.
Posted: Tue 08 Aug 2006 06:54
by paranoyakX
this is because Oracle's OPEN_CURSORS variable. this variable is setting the max open cursors (and dont forget every dataset starts a new cursor;))
Posted: Tue 08 Aug 2006 12:29
by Challenger
We fixed the problem with raising ORA-01000 error with Net option. This fix will be included in the next build of ODAC.
To Dstrenz:
We couldn't reproduce this problem using latest version of ODAC. Please specify the version of ODAC
you use.
Posted: Fri 11 Aug 2006 14:29
by dstrenz
challenger wrote:We fixed the problem with raising ORA-01000 error with Net option. This fix will be included in the next build of ODAC.
To Dstrenz:
We couldn't reproduce this problem using latest version of ODAC. Please specify the version of ODAC
you use.
Sorry to take so long to respond. I've been on vacation but will try to duplicate the problem today. The version is 5.70.1.34 with net option.
explicit call
Posted: Tue 29 Aug 2006 01:01
by nfridley
use the GC.Collect()