A call to certain stored procedures that contain parameters may fail, resulting in OLE DB error 0x80004005 when using the Microsoft OLEDB Provider for Oracle older than version 2.10.3912.0.

In the MS Oracle OLEDB Provider at times there is not enough memory allocated to handle stored procedure parameters of a specific cumulative size or greater. This condition appears to generate an Oracle error 6215, but the provider does not trap for this particular error and simply fails the call with the generic "0x80004005 Errors occurred" error.

It is possible to reduce the number of parameters in your SQL Statement and thereby avoid this error. Or you can choose to select the Microsoft OLEDB Provider for ODBC, so you may connect to the Oracle database through an Oracle ODBC driver.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This fix has also been released in MDAC 2.1 SP2 which is available on the web:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx (http://msdn2.microsoft.com/en-us/data/aa937695.aspx)

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 computers experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix.

To obtain this feature immediately, 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:
The English version of this fix should have the following file attributes or later:


Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.