From: Henrik J. <hp...@gl...> - 2001-11-11 14:56:42
|
Ok, I've looked into this. The problem unfortunately seems to be in the access library I use to Oracle and not in my software. Therefore I'm not really comfortable messing with it this soon before a release. However despair not I have made some other changes that will minimize this problem. (I do something now that before lost around 20 open cursors and now I mayby loose one). It only strikes when you abort a running query, this happens when you scroll through the databrowser and continues to the next one before the tab you are looking at is not finnished updating. It is especially dangerous when you tab through objects watching the contents editor since this one executes new SQL for every object. Anyway, it's almost fixed (To the point where I can almost guarantee you'll never experience the "maximum number of open cursors exceeded" problem. However the changes are quite complex and I really need to test it a bit more before I let someone hammer on it in a production environment. It will be in the 1.1.5 release though to be released on friday hopefully. /Mauritz GlobeCom AB van Geel, Leo wrote: >Hi Hendrik, > >It happened again. > >But now after I hit the error message "maximum number of open cursors >exceeded" (=384 in our system) > >I was the only user on the system.....and I was running the schema browser >window and browsing a user with 617 tables. > >I will try to reproduce it. > |