eazyloader oracle spatial

[thierry.baulu]

Hello fellow Mapinfo'ers.

looking through this board for info regarding mapinfo pro having difficulty reading and writing oracle spatial tables (using either easyloader or dbms connection).

I saw a few posts stating they cannot connect to oracle 11g at all.

that was my case in the beginning until I figured out I needed a 32 bit oracle client for Mapinfo to see the oracle database.

Now that I can see the database, I am however unable to read or write any oracle spatial table (SDO_GEOMETRY)

If I use the DBMS connection and then try to open a table in the database, Mapinfo is able to recognize the table which are spatial and even displays beside the table the icon that informs us wheter it is a point, line or pokygon geometry table. bur when I select one of the spatial tables and try to open it nothing happens, it runs for a few seconds and then returns me to the table list!!!!!!

If I try eazyloader, I can connect with ODBC but the oracle button is greyed out!!!!

Any thoughts on what could be the cause, and ultimately the solution to this strange behaviour?

I am running Mapinfo 12.0.3 on a windows 7 64 bit OS, I have both the 64 and  the 32 bit oracle client 11.2

thanks in advance

Thierry

[Eric Blasenheim]

There are a few different questions here. I will try and address them.

Yes you need the 32-bit client dlls to talk to Oracle as MapInfo Professional is currently a 32-bit application. All 32 bit applications need this. The client does not have to be the big formal client, the "instant client" (Oracle's name) will work fine. The end result that matters is two fold:

Can the software (easyloader or Professional) load the Oracle client dlls? (Must be 32-bit and they are on the system path)

Can the software use alias names for the database connections? Generally this means that the tnsnames.ora file can be found by the oracle software so that it knows what a simple alias like "Oracel11" that you might enter in the connect dialog actually evaluates to. This is not a requirement as one can specify the longer form but it quite common.

 

So if Professional is connecting is it via OCI or ODBC? The ODBC connection can only be used for non-spatial. You just use the OCI connection type. That should be available when and only when Professional can find the dlls as specified above. If this is not the case, check your system path and see if the 32-bit location for oracle was added.  If you are using OCI from within Professional, I am stumped. I would call support.

 

For Easyloader you say the Oracle connection is grayed out so that is why I am thinking something like above is amiss.

 

Eric Blasenheim

Pitney Bowes Software

[thierry.baulu]

Hi Eric

thanks for pointing me in the right directions.

turns out the system variable was pointing to the /bin directory of the oracle 32 bit client when in fact it should have pointed to the root directory of the client.

as soon as I corrected this issue the oracle spatial button on the easy loader came alive.

thanks again

Thierry