Those steps are only needed when you want to use the Oracle support of OGR. ( http://mapserver.org/input/vector/oracle.html#two-options-for-using-oracle- spatial-with-mapserver ) By setting "CONNECTIONTYPE ORACLESPATIAL", you use the native oracle through mapserver. The DLL you were talking about is not used.
So, with MapServer 5.6.1, you can reproduce the problem.. but not with 5.2.1. Thanks for the info, Alan On September 28, 2010 03:31:54 am Jorge Bellido Diez wrote: > We're using 'oraclespatial', I mean > > CONNECTIONTYPE oraclespatial > > CONNECTION user/p...@database > > We've just done what is explained in ms4w manual to get Oracle support > (http://www.maptools.org/ms4w/index.phtml?page=README_INSTALL.html#oracl > e-10g > <http://www.maptools.org/ms4w/index.phtml?page=README_INSTALL.html> ) > > Does this tell something to you?? Thanks > > > ________________________________ > > De: Alan Boudreault [mailto:[email protected]] > Enviado el: lunes, 27 de septiembre de 2010 15:04 > Para: [email protected] > CC: Jorge Bellido Diez; Sumit Sharma > Asunto: Re: [mapserver-users] Re: Coments about the Tickedt 3541 > > > > It depends on how you define your layer. In the bug, they are using the > native oracle support in MapServer and not the oracle support from OGR. > So, the ogr_OCI.dll is not used. What OCI support are you using? (The > CONNECTIONTYPE in your layer) > > Alan > > On September 27, 2010 06:16:59 am Jorge Bellido Diez wrote: > > Hi, > > > > > > > > More comments about this ticket. We're using ms4w 3.0 beta 11 > > > > (DEVELOPMENT) as commented previously, which includes MapServer 5.6.1 > > > > version. In the beginning we started using ms4w 2.3.1 (STABLE), which > > > > includes MapServer 5.2.1. We've installed again the STABLE version > > with > > > same DB server, same data, same WMS configuration and the error is not > > > > reproduced anymore. > > > > > > > > We've noticed that the ogr_OCI.dll file is different. It could be > > > > posible that problem could be there?? Or it's more likely to be a bug > > in > > > MapServer's code?? > > > > > > > > Thanks. > > > > > > > > -----Mensaje original----- > > > > De: [email protected] > > > > [mailto:[email protected]] En nombre de Sumit > > > > Sharma > > > > Enviado el: jueves, 23 de septiembre de 2010 16:17 > > > > Para: [email protected] > > > > Asunto: [mapserver-users] Re: Coments about the Tickedt 3541 > > > > > > > > > > > > Initially this bug appears random to me as well, but it is certainly > > > > not. > > > > However, there is surely some loophole in OCI, and that bug is > > exploited > > > by MapServer. I have posted this bug in Oracle forum as well, but no > > > > luck as of now. > > > > As Alan is already able to verify this behavior, hopefully we will get > > > > some patch soon ... :-) -Sumit > > > > -- > > > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Coments-about-the-Tickedt-3541-tp > > > 5558012p5563227.html > > > > Sent from the Mapserver - User mailing list archive at Nabble.com. > > > > _______________________________________________ > > > > mapserver-users mailing list > > > > [email protected] > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-users > > > > _______________________________________________ > > > > mapserver-users mailing list > > > > [email protected] > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
