I think setting the runtime parameterNONBLOCKSQL will solve this problem, I
did this a few times with suc6 maybe a coincidence but nevertheless. It has
to do with the fast clients we have nowadays.
Wilson Lee heeft geschreven in bericht
<81mb1g$7lr$1_at_justice.csc.cuhk.edu.hk>...
>Hello, I have the same problem on Oracle report.
>
>Oracle Report 2.5 is used in client side(PC) and Oracle server ver7.3
>is installed in UNIX machine.
>
>At least two reports had encountered such errors, one of which only
>contain one master query with 15 to 16 records to fetch. When using
>TRACE utility provided in Oracle Report, it seems that after fetching
>all the records, the report cannot close the cursor and continue to fetch
>next record. Howover, the opening and closing of cursor should be
>implicitly done by the Report.
>
>I have changed Report Options such as buffer size, array size and
>NONBLOCKSQL flag, but the error still occur sometimes. It is interesting
>that for the same report, it can be successfully run in one instance but
>encounter the error when used in another instance. And it is also quite
>interesting that after a period of time (main be one or two hours), a
>report
>,which originally encounters this error, can be run successfully.
>
>For such error, it is quite difficult to explain to users of the
>application.
>
>Thanks for JOC and all who have contributed solution. And hope
>someone can solve the problem.
>
>
>WL
>
>
>
>
Received on Fri Nov 26 1999 - 15:37:53 CST
