Posted 16 June 2005 - 01:10 PM
We have an error 361 - SQL ERROR: NO CURSORS AVAILABLE
We are testing after migrating to 5.5 and Oracle 9i
I increased SQL_CURSORS to 64 and this seemed to fix it but if I access enough screens in our application the error comes back.
Any suggestions appreciated.
Posted 16 June 2005 - 02:42 PM
This software we are running has not recently been changed,
we've just recently ported from 4.6 & ORA 7 to 5.5 and ORA 9.i. on Win2003
we are confident its not a Loop
the cursor problems have occurred just going thru simple transaction and/or enquiry type screens where some file processing may occur for building temp files etc., and its defintely Random
We are NOW setting the cursors value in pro-iv to be 128
What values are you or similar users of 5.5 and ORA 9 got cursors set to ?
Any other PRO-IV or oracle config advice for our environment much appreciated
Posted 16 June 2005 - 03:24 PM
If I recall correctly, an earlier version of the 5.5 kernel didn't always release open cursors.
We added the SQL_CURSORS=AUTO parameter into our pro4.ini and changed our open_cursors value in the init.ora (or spfile.ora depending on configuration) to around 500.
Posted 17 June 2007 - 09:13 PM
I had the same error and it turned out that a function was in a loop.
We corrected it and it went away.
I too had this error and I increased my SQL_CURSORS to 64 in the pro4.ini. You can set it to AUTO but I am not sure if there is a performance impact.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users