The hotfix you mentioned is for NT 4.0 or MDAC 2.1, which should already be
included in W2K3 SP2. Therefore, this may be another memory leak.
To troubleshoot a memory leak, you may try "umdh" which is shipped together
with Windbg. And it can be downloaded from:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
If you confirm this is a leak from MS products and it causes a big impact to
your product/company, you may consider to contact Microsoft customer support,
since troubleshooting a memory leak on forum is not efficient at all.
=================================================
btw, what is the state of your product (in development, or shipped)? If your
product has not yet shipped, I advise you to stop using the driver "Microsoft
ODBC for Oracle" (provided by Microsoft) which can only connect to Oracle v.7
or v.8 (basically, our driver has already been deprecated and will not
support latest Oracle databases). Instead, you should try the driver shipped
by Oracle, which should support all latest features in Oracle database. More
information about the limitation of our driver can be found at:
http://support.microsoft.com/default.aspx/kb/244661/en-us
Thanks,
Ming.
WDAC Team, Microsoft.
P.S. We recommend customers to use the forum to ask questions in the future,
where you can obtain a faster response (Forum is at:
http://social.msdn.microsoft.com/forums/en-US/sqldataaccess/threads/)
"techcpp" wrote:
> Hi,
> I am facing a problem of memory leak in my C++ application on frequent
> connect and disonnect to oracle database using microsoft odbc driver. The
> problem seemed to have been reported earlier at
> http://support.microsoft.com/kb/232351.
> I am using Windows Server 2003 standard edition with service pack 2.
> Can someone provide me help on this isse?