|
|
|
|
|
| | |
| |
Active Server Pages help tutorial how to ASP Help ASP Tutorials ASP Programming ASP Code - ASP Free CJWSoft ASPProtect ASPBanner ASPClassifieds
(Advanced)
(Components)
(Database)
(General)
(Vbscript)
|
|
|
|
Subject: |
max number of cursors exceeded in oracle |
|
From: |
wanker8000 |
|
Date: |
8/29/2001 9:41:31 AM |
|
IP: |
65.105.120.2 |
I have a situation where I'm calling an Oracle stored procedure many times in a loop on an ASP page. The procedure is called using the ADODB.Command object. I find that if I create the object using the Server.CreateObject call, Oracle will return a message indicating that the max number of open cursors has been exceeded; after running 99 iterations through the loop. If I create the object using CreateObject (without the Server.), I don't get this error. Any idea why the command object is being kept open in the first case?
Here are the two different versions of the call:
for i = 1 to 900
'causes error:
set cmd=Server.CreateObject("ADODB.Command")
'does not cause error:
'set cmd=CreateObject("ADODB.Command")
'...
with cmd
.ActiveConnection = cnx
.CommandType = 4
.CommandText = "p_test_procedure"
.Execute
end with
set cmd = nothing
next
I'm using IIS 4.0. Is there a way to get the Server object to release these cursors? Thanks...
-w8k |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
