Ask a Question related to Coldfusion Database Access, Design and Development.
-
CF_DAWG #1
Re: [Macromedia][Oracle JDBC Driver][Oracle]ORA-01000:maximum open cursors exceeded
Here is the technote from Macromedia regarding this issue:
[url]http://www.macromedia.com/go/tn_17660[/url]
Hope this helps!
CF_DAWG Guest
-
Oracle JDBC driver and CF MX 7 Standard edition
hi, guys. is it possible to use Oracle JDBC driver with CF MX 7 Standard edition? all our CF servers are Enterprise edition so we never ran into... -
Oracle JDBC driver and CF Standard edition
hi, guys. is it possible to use JDBC driver for Oracle with CF MX 7 Standard edition? all our CF servers are Enterprise edition and we've been... -
[Macromedia][Oracle JDBC Driver]No more data availableto read.
I get the following error when I change the SQL statement layout in my ColdFusion code - No more data available to read. For Example: The... -
[Macromedia][Oracle JDBC Driver]No more dataavailable to read.
Are you on Coldfusion MX6.1? There was http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18807. Download and install the Datadirect... -
SQLException: [Oracle JDBC Driver]No more data availableto read ?!?!?
Hello, I am trying to instantiate a database source. I got it to work with an 8.1.7 oracle DB, but when I try an oracle 9i DB I get: ----... -
ldbc #2
Re: [Macromedia][Oracle JDBC Driver][Oracle]ORA-01000:maximum open cursors exceeded
I ran into this problem last week. I was using the <cfqueryparam> tag in my
code. I just had to remove the tags and the code ran fine. I found the
solution in this article:
[url]http://jehiah.com/archive/maximum-open-cursors-exceeded[/url]
ldbc Guest
-
sdupre #3
Re: [Macromedia][Oracle JDBC Driver][Oracle]ORA-01000:maximum open cursors exceeded
The technote is for an older version of ColdFusion. CF_DAWG is right. My
guess is it's bug 53884. The number of 'max pooled statements' (default 1000)
in the CF admin datasource is set higher than the number of open cursors Oracle
allows (max cursor setting). The evidence is getting rid of <CFQUERYPARAM>
for CF_DAWG. Since users may need <CFQUERYPARAM> for input validation for
queries (to avoid SQL injection attacks), you're probably better off putting
that back in. Lower the Max Pooled Statements setting. We recommend 0 on many
applications. There was only one other issue I'm aware of but it only happened
with looping (CFQUERY in a loop). That was fixed in 3.3 build 67. What
ColdFusion MX are you running? CFMX 6.1 + Updater? CF 7.0? Regards,
Stephen Dupre Macromedia QA
sdupre Guest



Reply With Quote

