Re: Memory Usage

We had the same problem with Oracle 8.1.5 connecting with OleDb. When opening and closing a connection using the same connection string 100 times in a row, the server shows 100 open connections. We don't have the problem in Oracle 9i.

For our 8i customers (which is most of them) we have had to implement our own connection pooling. We just keep a pool of connections open and recycle them for new calls. We are using .NET, and the only gotcha is that we have to be sure to close the DataReaders (cursors/recordsets), since the connections aren't being closed.

"Marc Perry" <marc.perry03_at_cox.net> wrote in message news:c937c2f9.0305130736.23905291_at_posting.google.com...
> I am a software developer and I have written a program that uses
> Oracle for its data source. I have about 600 users on it and it is
> running out of memory. I watched in Enterprise Manager to see what the
> memory usage for each user was. The interesting thing I found out was
> that when a recordset was closed from the application the memory was
> still being taken up by the server. I tried both server side and
> client side cursors and had the same result. Has anyone had a similar
> problem? I really do not want the app to close the connection and
> re-open every hour to free up the memory.
Received on Tue May 13 2003 - 17:49:50 CEST