How To

Updating SRID values in an Oracle geometry column

Article Number: 000001086 -  Last Modified: Jul 8, 2011

To handle multiple geometry columns in an Oracle feature class you currently need to insert features for the first geometry column and then update features to update the second geometry column. However this technique does not allow you to insert an SRID value into the second geometry column.

Use the following SQL command in an SQL Statement to Execute after Translation to update the SRID value:

UPDATE <table> a SET a.<geometry_column>.sdo_srid = 90112;

In addition there will be no entry in the user_sdo_geom_metadata table for this second geometry column so you can add an entry by issuing the following command once:

INSERT INTO user_sdo_geom_metadata SELECT TABLE_NAME,'<second_geometry_column_name>',DIMINFO,SRID FROM USER_SDO_GEOM_METADATA WHERE TABLE_NAME = '<Multi_geometry_table_name>';

Suggested Similar Articles

A description of some of the functionality in the Oracle Spatial Object Reader/Writer.

For FME to make a spatial query against Oracle spatial tables or spatial views there needs to be metadata entries in the MDSYS.SDO_GEOM_METADATA table.

It is possible to use Oracle spatial tables from within ArcCatalog, within ArcMap, and via the Data Interoperability extension if the tables have been set up with the correct spatial index and an indexed column

FME is able to write multiple geometry types to an existing PostGIS table defined already with multiple geometry types. We cannot write a new geometry type column to an existing table. Example table in PostGIS: ID (int) = 1 Name (char) = test Geom (Geometry) = point Geom2 (Geometry) = line

FME is loading features into my database such as Microsoft SQL Server Spatial, Oracle Spatial, Postgis or DB2 which the GeometryOGCValidator is passing as valid but the database tools are tagging as invalid.