Sorry to reply to my own message but I figured out the step I missed
out, turns out that when I used EasyLoader to re-import the data, it
created a MAPINFO_MAPCATALOG entry that referred to the EasyLoader
imported version of the table, with the SDO_GEOMETRY column named GEOLOC.
When I dropped the table then attempted to recreate the new LICENCE_POLY
table with actual field names. The map catalog was left out of date.
Deleting the correct row from the map catalog then using the "Make DBMS
table mappable function..." to recreate the catalog entry solved this
problem.
Cheers,
Michael
Michael Sharman wrote:
> Hi,
>
> I've been working with an Oracle Spatial database recently, and until
> now I've been able to get things working flawlessly, until today that is
> when I've somehow made the table incompatible with MapInfo Pro:
>
> I was trying to drop and recreate a spatial table from an existing
> database, but after recreation of the data, MapInfo refuses to open the
> table responding with:
> "Unsupported data type for column(s): GEOMETRY Unable to fetch records
> into table"
>
> This is the SQL I'm using to create the table (both originally and now):
>
> CREATE TABLE TIGER_PROD.LICENCE_POLY
> (
> GID NUMBER(38),
> GEOMETRY MDSYS.SDO_GEOMETRY,
> TEN_ID NUMBER
> );
>
> CREATE INDEX TIGER_PROD.LICENCE_POLY_I ON TIGER_PROD.LICENCE_POLY
> (GEOMETRY)
> INDEXTYPE IS MDSYS.SPATIAL_INDEX;
>
> INSERT INTO mdsys.sdo_geom_metadata_table
> ( SDO_TABLE_NAME, SDO_COLUMN_NAME,
> SDO_DIMINFO,
> SDO_SRID,
> SDO_OWNER)
> VALUES ( 'LICENCE_POLY', 'GEOMETRY',
> MDSYS.SDO_DIM_ARRAY(
> MDSYS.SDO_DIM_ELEMENT('X', 229000, 616000, .001),
> MDSYS.SDO_DIM_ELEMENT('Y', 5160000, 5640000, .001)
> ),
> 81936,
> 'TIGER_PROD'
> );
>
> Now previously I'm sure this is how I created the table in the first
> place, is there a step I've missed out?
>
> As you can see I've created the spatial index and added the meta data,
> Oracle doesn't seem to have any problems perform spatial queries over
> it, but the exact same MapBasic code that did work yesterday in MapInfo
> now fails with the error:
> "The keyword Object cannot be translated because the table is not
> mappable"
>
> Also, the this exact same error occurs if I try to make the table
> mappable via the MapInfo "Make DBMS table mappable..." dialogue.
>
> Like I said the same table structure was working previously, has anyone
> got any ideas as to what I'm doing wrong?
>
> Incidently, tables created using EasyLoader into the same database, work
> fine
>
> Also I've got a backup of the data for this table in an form that can be
> imported by the "imp" oracle tool, this also creates a table that is
> unusable.
>
>
> Regards,
>
> Michael
>
>
>
--
Michael Sharman <[EMAIL PROTECTED]>
Insight.GIS +61-3-6234-5833
Suite 6, Level 1, 175 Collins Street, Hobart, Tasmania
_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l
