Memory Leak In Oracle Database Provider CommandBuilder Through System.Data.Common

(Doc ID 1587995.1)

Last updated on SEPTEMBER 27, 2013

Applies to:

Oracle Data Provider for .NET - Version and later
Information in this document applies to any platform.


Memory leak occurs when using the OracleCommandBuilder objects through the factory. As soon as the UpdateCommand from the OracleCommandBuilder is called, a new DataReader object is open and left hanging until the connection is closed. If we does this in a loop, eventually run into a "ORA-01000: maximum open cursors exceeded" error


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms