Hi Deepak, you may want to query the v$open_cursor view for the relevant session to diagnose if there is a cursor leak or the open cursors limit is simple too low. Jaromir > You can generate either Oracle trace or error stack (alter session set > events '1000 trace name errorstack level 3' or event="1000 trace > name errorstack level 3" in init.ora/spfile) to diagnose the issue. I.e. > see if it's really the cursor you think that is being problemmatic. > > > On 9/26/07, DBA Deepak <oracle.tutorials@xxxxxxxxx> wrote: >> >> Hi All, >> >> Have a PL/SQL stored procedure, which is doing DELETE from a table >> 1000 time. And the same procedure is getting called many times from >> the application. (Am not using any explicit cursors inside the stored >> procedure) >> >> >> My problem is am getting "ORA-01000: maximum open cursors exceeded" >> exception. >> >> I think Oracle should sclose the implicit cursor opened by the DELETE >> after the execution goes out of scope. >> -- //www.freelists.org/webpage/oracle-l