Skip to main content
Question

Global Temporary Table that Contains ST_GEOMETRY

  • March 5, 2013
  • 4 replies
  • 42 views

Good evening.

 

 

I have created the below global temporary table on our development schema, and within the FME workbench, I am trying to create an ARCSde reader that will use this table.   

 

 

CREATE GLOBAL TEMPORARY TABLE myglobal(

 

  IGEOM              ST_GEOMETRY,

 

  HU100                   NUMBER,

 

  POP100                  NUMBER,

 

  POPPEP                  NUMBER

 

) ON COMMIT PRESERVE ROWS;

 

 

When I attempt to create the reader, I receive the below error message:

 

 

An error occurred while attempting to open the table, feature class or relationship class 'myglobal'. The error number from ArcObjects is: '-2147155648'. The error message from ArcObjects is: {Abstract Data Types not supported [myglobal][STATE_ID = 24]}

 

 

I tried creating the table with the ST_GEOMETRY column and then creating a reader to access the table within the FME workbench and there were no issues.  Is there something special I need to do to work with ST_GEOMETRY?  I'm encountering a lot of issues using that type, whereas I encountered none when using SDO_GEOMETRY.

 

 

Thanks very much.

 

 

Joe

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

  • Author
  • March 5, 2013
Correting a type:

 

 

I tried creating the table without the ST_GEOMETRY column and then creating a reader to access the table within the FME workbench and there were no issues.

  • Author
  • March 5, 2013
(I can't type too well this afternoon :))

 

 

Correcting a typo:

 

 


david_r
Celebrity
  • March 6, 2013
Hi Joe,

 

 

A couple of questions: Both of the above needs to be in place before the ArcObjects-based reader will be able to access the data.

 

 

Hope this helps.

 

 

David

  • Author
  • March 6, 2013
Ah, thanks David--I knew there was something basic I was missing!  I'm brand new to ST_GEOMETRY and so didn't know the table had to be registered.  Unfortunately our office is closed today because of snow, but tomorrow I will try this and see if I can view the table using ArcCatalog.

 

 

Thank you!

 

 

Joe