I glad to know that it solved your problem, even with my poor cellphone typing.
It seems like Windows doesn't detect that the oci.dll version/architecture is
wrong and loads it with without a problem, but when the GDAL driver try to
call the OCI API to open a connection that error comes as a default. What is
very misleading. It has nothing to deal with SID or the Listener setting.
> Date: Fri, 11 Apr 2014 12:08:35 +0200
> Subject: Re: [gdal-dev] [EXTERNAL] oci and oracle express 11
> From: landa.mar...@gmail.com
> To: lucena_i...@hotmail.com
> CC: mate...@loskot.net; gdal-dev@lists.osgeo.org; michael.sm...@erdc.dren.mil
>
> Hi all,
>
> 2014-04-11 4:00 GMT+02:00 Ivan Lucena <lucena_i...@hotmail.com>:
>
> [...]
>
> > I know that is not the same situation you have, but when I need to run GDAL
> > build for Win32 on my Win64 machine I need to place an OCI.DLL from a
> > InstantClient-32 first on my PATH. Otherwise it will try to load the default
> > on DLL my system, that happens to a Win64 OCI.DLL.
>
> that was! When I removed oci.dll from c:\osgeo4w than it started magically
> work!
>
> ogrinfo -ro OCI:user/passwd
>
> Thanks for saving me from madness :-) Martin
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
