BUG: Microsoft Oracle Provider Leaks Memory Through ICommandText[oledb]

ID: Q236583

The information in this article applies to:

Microsoft OLE DB Provider for Oracle, version 2.1

SYMPTOMS

The Microsoft OLE DB Provider for Oracle leaks memory when you use ICommandText::SetCommandText(), ICommandText::Execute(), and ICommandText::Release().

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:



File Name        Date       Size      Version       
---------------- --------- --------- ------------- 
 msdaora.dll      7/28/99   188,176   2.12.4328.0

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

The following code reproduces the memory leak:


hr = pIDBCreateCommand->CreateCommand( NULL,
	IID_ICommandText, ( IUnknown ** ) & pICommandText );

hr = pICommandText->SetCommandText( DBGUID_DBSQL, wSQLString );

hr = pICommandText->Execute( NULL, IID_IRowset, NULL,
	& cRowsAffected, ( IUnknown ** ) & pIRowset );

if( pIRowset )
	pIRowset->Release();

hr = pICommandText->Release();

Additional query words:

Keywords : kbOLEDB kbGrpMDAC kbDSupport kbGrpOLEDB
Version : WINDOWS:2.1
Platform : WINDOWS
Issue type : kbbug