>>My question is, what would
cause Oracle to bypass c:\orant\bin and try to use the OCIW32.DLL found
in \system32? (How the DLL got into \system32 in the first place is a
question I'm taking up with our desktop support team!)
<<
Ed,
MS Windows.
A normal search patern for DLL is :
1. Current application folder.
2. <Windows> folder
3. <WIndows>\System32 folder
and in the end , if all above fails to search PATH:
HTH
"Ed Stevens" <ed.stevens_at_home.com> wrote in message
news:94ppi9$q49$1_at_nnrp1.deja.com...
> Subject: Oracle's method of locating its DLLs.
>
> We recently received some "beta" versions of a new standard PC
> configuration for our IT department, as configured by our desktop
> support group. Everything worked fine except our Powerbuilder apps,
> which were getting an ORA-03121 when trying to connect to the database.
> SQL*Plus connected with no problem. After some lengthy comparisons of
> older (working) systems and these new ones, we found a copy of
> OCIW32.DLL (version 7.x, 35.5kb, dated 1-3-96) located in
> c:\winnt\system32. When we deleted this file, everything began to work
> properly.
>
> What we found puzzling is that the system path was set to "C:\orant\bin;
> <snip some other stuff>; c:\winnt\system32; My question is, what would
> cause Oracle to bypass c:\orant\bin and try to use the OCIW32.DLL found
> in \system32? (How the DLL got into \system32 in the first place is a
> question I'm taking up with our desktop support team!)
>
>
> --
> - Ed Stevens
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Sat Jan 27 2001 - 22:10:55 CST
