Heap Error during Windows OCIEnvCreate() call

Question

During a call to:
OCIEnvCreate(&m_handles.m_pOCIEnv,
                         OCI_THREADED | OCI_OBJECT,
                         NULL,
                         NULL, NULL, NULL,
                         0, (dvoid **)0);
A crash occurs which reports the following in the MSVC 2005 debug output window:
HEAP[AutoTest.EnvironmentPkg.DatabaseConnectionManager.exe]: Invalid Address specified to RtlFreeHeap( 00150000, 0015ED80 )
Windows has triggered a breakpoint in AutoTest.EnvironmentPkg.DatabaseConnectionManager.exe.
This may be due to a corruption of the heap, and indicates a bug in AutoTest.EnvironmentPkg.DatabaseConnectionManager.exe or any of the DLLs it has loaded.
We are using version 10.2.0.3 of the Oracle Basic Lite client on Windows XP, called via SQLAPI++.
I have verified that the memory we allocate is not being corrupted before this call. Using Compuware's Boundschecker VS add-in, I've verified that the heap error is in a memory range allocated by oraociicus10.dll. Since the OCIEnvCreate call is the first time that oraociicus10.dll allocates memory (i.e. my code doesn't have a chance to trample Oracle's data structures), there's a good chance IMO that it's an internal Oracle problem.
Boundschecker reports errors such as:
Pointer Error: When calling LocalFree, pointer 0x03A60A5C is not at the beginning of the block 0x03A60998 (65536) allocated by LocalAlloc.
These errors are reported in a Debug build; the same kind of error happens during a Release build.
According to a previous thread, a special release of the OCCI interface DLLs was needed to fix MSVC 2005 compatibility issues like this one. (See Debug in Visual Studio 2005 (vs8) ? )
I've posted looking for any such release for OCI DLLs, but haven't found any yet ( MSVC 2005 compatible OCI DLLs? )
My questions:
1. Could this be a compatibility problem between the OCI DLLs and MSVC 2005? and
2. If not, what could the problem be?
Thanks in advance for your help.

Answer 1

Are you using the oracle thin client ...?? Try using the full client install.
Is it working with OCI_DEFAULT or OCI_THREADED alone ???
Please note the following points in WINDOWS Platform.;
1)Try always a fresh installation for Oracle and VS products.Preferably a clean install of the OS.
2)If don't want to remove OS , do a clean UNINSTALL (This should include a complete clean up in the Registry and file systems).
3)Always reboot the system before and after installations and try your code.
If the above sequences are followed most of the DLL/LIB problem are solved for me.