he was runnnig in sqlplus, sqlplus has stuff open as well (dbms_output for example, it might have a dbms_output.get_lines call parsed)


I didn't have such a cursor

ops$tkyte@ORA10GR1> show parameter open_cursors

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 50
ops$tkyte@ORA10GR1> @test

PL/SQL procedure successfully completed.

ops$tkyte@ORA10GR1> l 100 *
100 OPEN test47;
101 OPEN test48;
102 END;
103
104 --This last OPEN will cause an error
105 --from too many cursors.
106 OPEN last99;
107* END;
ops$tkyte@ORA10GR1>


in my session so it works. SQLPlus, when used as the test tool, must be looked at too.


adding another cursor:

ops$tkyte@ORA10GR1> @test
DECLARE
*
ERROR at line 1:
ORA-01000: maximum open cursors exceeded
ORA-06512: at line 3
ORA-06512: at line 108


ops$tkyte@ORA10GR1> l 100 109
100 OPEN test46;
101 OPEN test47;
102 OPEN test48;
103 END;
104
105 --This last OPEN will cause an error
106 --from too many cursors.
107 OPEN last99;
108 OPEN last100;
109* END;
ops$tkyte@ORA10GR1>

so that showed that plus just had something else open in his release.


but, just to add a twist :)


ops$tkyte@ORA10GR1> show parameter open_cursor

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 50

ops$tkyte@ORA10GR1> DECLARE
2 procedure p
3 is
4 cursor c is select * from dual;
5 begin
6 open c;
7 end;
8 BEGIN
9 for I in 1 .. 100
10 loop
11 p;
12 end loop;
13 END;
14 /

PL/SQL procedure successfully completed.