Unsupported data type for column(s); GEOLOC Unable to fetch records into table

[raulami]

"Unsupported data type for column(s); GEOLOC Unable to fetch records
into table

Error message is coming while open database functionallity used in Map INFO

[Peter Horsbøll Møller]

The table you are opening from the database has a spatial column that MapInfo Pro isn’t aware of.

 

Have you tried registering the table in the map catalog (making the DBMS table mappable)?

 

Peter Horsbøll Møller
Pitney Bowes
Sent from my mobile - typos may occur

--
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en

---
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

---

[raulami]

How to do that please specify me in steps.

[StA]

Good morning all, i hope everyone is well in these interesting times,

I have an Oracle view which is being "fed" a large number of tables, and it has been working ok. 

I have tried to remove and add some tables from the view, with the script in Oracle running successfully and having the view created without errors. But when i try to load the view in mapinfo i get the error message: Unsupported data type for column(s); GEOLOC Unable to fetch records into table" followed by "the table you have chosen cannot be made mappable, a table must contain a spatial column or at least two numeric columns".

Having read some of the previous posts in this group, i did try also to alter the SDO_GEOM table in oracle so as to include these tables but it does not populate the SDO_DIMIFO field which contains that spatial reference. 

I also did try to use the "make DBMS table mappable" function in mapinfo with no success.

I am using Mapinfo Professional 11.0 and Oracle SQL developer 1.5.4.

Any advice would be really appreciated

Kind Regards

Stathis

[Peter Horsbøll Møller]

Hi

 

Is the view registered in the table MapInfo.MapInfo_MapCatalog?

That’s where MapInfo Pro will look to understand how it should interpret the spatial information in any table/view.

 

Peter Horsbøll Møller

www.precisely.com

 

—

Peter Horsbøll Møller

Principal Sales Engineer - Distinguished Engineer

Precisely.com

 

From: mapi...@googlegroups.com <mapi...@googlegroups.com> On Behalf Of StA
Sent: 2. februar 2021 11:43
To: MapInfo-L <mapi...@googlegroups.com>
Subject: [MI-L] Re: Unsupported data type for column(s); GEOLOC Unable to fetch records into table

 

This message originated Externally. Use proper judgement and caution with attachments, links, or responses.

 

--

--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en

---
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/2b47b931-5382-4dc7-954b-eaece02cde1cn%40googlegroups.com.

[StA]

Good afternoon Peter and thank you for your reply, 

I am afraid no, i can't see the view listed in Mapcatalog. Does this give an indicator that there is an issue?

thank you very much again

Stathis

[Peter Horsbøll Møller]

Yes, that’s the cause of the problem.

You can use MapInfo Pro to add the view to the MapCatalog by specifying the spatial column, the coordinate system etc.

 

Look for “Make DBMS Table Mappable”, in the Maintenance menu

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/078f6b89-2913-4f8d-b623-90d363be6391n%40googlegroups.com.

[StA]

Hello Peter and thank you for your reply, 

As mentioned in my initial post, in my last sentence, i did try this too, but i get the same error.

Index Column: GEOLOC

Style Column: MI_STYLE

Kind Regards

Stathis

[Peter Horsbøll Møller]

OK, sorry I missed that.

But if the view isn’t to be found in the MapInfo_MapCatalog table, it hasn’t been registered.

Can you try to add it again?

Note that if the view already exists in the MapInfo_MapCatalog you can’t see the view in the dialog where you are asked to select the table to make mappable.

 

You are using a rather “classic” version of MapInfo Pro 😊

Are you sure the version of Oracle is compatible with your version of Pro?

 

Another thing to note is that unless you have a column named MI_PRINX, you will not be able to open the view as live.

Without the MI_PRINX column, Pro can’t detect the primary index column and will only allow you to open the data as a linked read-only table.

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/0c39d49d-394d-40a5-ad85-e97dd1dcdc07n%40googlegroups.com.

[StA]

Good afternoon Peter and thank you very much for you assistance in this matter,

Well i did also try Mapinfo v15 but i get the same errors. I tried both downloading from the Oracle server and making the table mappable.  

 

Now the synergy between Mapinfo v11 and Oracle has been there for over a decade and we never had any issues, as far as i am aware. This is a sort of first for me.

Also the view contains MI_STYLE, MI_PRINX and GEOLOC columns

Thank you very much again

Stathis

[Peter Horsbøll Møller]

Hi

 

OK, I just wanted to make sure about the versions. I’m pretty sure we work with most versions of Oracle even with the older versions.

But I haven’t kept up with he changes in Oracle and we typically only test on the newer versions with the current version of Pro.

 

OK, good to hear about the MI_STYLE, MI_PRINX and GEOLOC columns.

You seem to have that well under control.

 

Can you check the MapInfo_MapCatalog again after making the table mappable?

Maybe there is something preventing you from adding the table to the MapCatalog?

 

If you know the values, youc an try to add the view manually to the MapCatalog.

Maybe you can use the settings from the base table holding the GEOLOC column?

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/3744ef8f-faf4-47d4-a479-50a04da8ec75n%40googlegroups.com.

[in...@viewshed.co.uk]

Stathis,

 

Just a thought, can you add a filter to your view so that it only includes valid spatial objects? It could be your view contains a NULL or unstructured object type in the GEOLOC column. Also, make sure your MI_PRINX column contains only unique integers. Generally MapInfo Pro is very forgiving whilst Oracle is more strict.

 

It might help if you can you post your view schema and mapcatalog row?

 

Regards

 

GIS Specialists Adrian Gray 07929 212566 adr...@viewshed.co.uk

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/MN2PR16MB311702543C69E9C6DD326A5396B59%40MN2PR16MB3117.namprd16.prod.outlook.com.

[Peter Horsbøll Møller]

Another thing that came to me yesterday evening:

Make sure you only have one column of type SDO_GEOMETRY

 

Peter Horsbøll Møller

www.precisely.com

 

—

Peter Horsbøll Møller

Principal Sales Engineer - Distinguished Engineer

Precisely.com

 

From: mapi...@googlegroups.com <mapi...@googlegroups.com> On Behalf Of in...@viewshed.co.uk
Sent: 2. februar 2021 19:51
To: mapi...@googlegroups.com
Subject: RE: [MI-L] Re: Unsupported data type for column(s); GEOLOC Unable to fetch records into table

 

This message originated Externally. Use proper judgement and caution with attachments, links, or responses.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/003501d6f994%244cdd0ec0%24e6972c40%24%40viewshed.co.uk.

[StA]

Good afternoon Peter and Adrian and thank you very much for your suggestions,

apologies for my delayed response.

Attached is an example format of the GEOLOC column, 

also after running a select command in SQL to identify entries where GEOLOC is null i got 15 rows which would be a good indicator, BUT these also existed in the previous view (the one i'm trying to update/change) so the question is how did it run ok before with these "errors" ?

Thank you very much for your time on this matter,  I really do appreciate it

Kind Regards

Stathis

[In...@viewshed.co.uk]

By way of troubleshooting this, I would add a filter in the view to ensure it only returns one valid row e.g. mi_prinx needs to be an integer primary key, geoloc must have a valid object or be null, rownum=1, and the view of registered in the map catalog.

If that works then you can focus on the data to track down the issue.

Regards

Adrian

To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/60628ccd-26f6-43cf-9919-aa6f0fc7e520n%40googlegroups.com.