6 replies to this topic

[Rory]

Hi

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.

Rory

[Bill Loven]

I had the same error and it turned out that a function was in a loop.

We corrected it and it went away.

HTH

Bill.

[George Macken]

Hi

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

tnks

george macken

[chuckl]

try SQL_CURSORS=AUTO

[Rory]

Hi all

We have SQL_CURSORS=128 and the problem seems to have gone away.

Thanks for your replies.

Regards
Rory

[tom braider]

I had the same error and it turned out that a function was in a loop.

We corrected it and it went away.

HTH

Bill.

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.