You run a Microsoft COM+ application that uses the Microsoft ODBC
Driver for Oracle and that performs distributed transactions. If you cannot open a statement cursor (this behavior may occur when the transaction
timeout value is exceeded), the application may stop responding or may behave
unexpectedly.
You cannot open a
statement cursor because a call to the
OCI_oopen method fails. When this call fails, the ODBC
Driver for Oracle passes an incorrect parameter to the error reporting
routine of Oracle (oerhms). If you cannot open a statement cursor, the ODBC Driver for
Oracle incorrectly passes a newly allocated cursor information structure
(Cda_Def) to oerhms instead of passing the Login Data Area (LDA) structure of the connection. Because
the cursor information structure is newly allocated, it contains NULL values
instead of valid data. Therefore, when the ODBC Driver for Oracle passes this
structure to oerhms, the behavior that is mentioned in the
"Symptoms" section occurs.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
MDAC 2.7
Date Time Version Size File name
--------------------------------------------------------------
06-Jun-2003 11:06 2.573.9001.26 131,072 Msorcl32.dll
MDAC 2.7 Service Pack 1 (SP1)
Date Time Version Size File name
--------------------------------------------------------------
09-May-2003 06:54 2.573.9031.44 131,072 Msorcl32.dll
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.