any news yet about this?
we have the same problem:
- when we use cursors as output of our stored procedures towards webMethods, it doesnt work. we have to leave them open otherwise it doesnt work!!! is this a normal way of doing???
As a result of this, we were programming many stored procedures that use cursors and silently we accepted this strange thing… now we have big problems due to this on our production environment:
Error: maximum open cursors exceeded
How can we avoid this?
Is it required to close cursors within the stored procedure or does WM takes care of this?
(as this is the first time in years we have this problem, we think that it’s because the stored proc falls in exception and there the closing of the cursor is a problem)
who and when to close cursors ???
#Integration-Server-and-ESB#webMethods#Adapters-and-E-Standards