Loading Oracle Spatial Data

There are things to be aware of when uploading data tables to an Oracle database, such as:
  • You cannot replace version-enabled tables in Oracle. This would make child versions of these tables obsolete.
  • Oracle has a limit on identifier names, which cannot be more than 30 bytes. For details, see http://docs.oracle.com/database/121/SQLRF/sql_elements008.htm#SQLRF51129. The total number of bytes for table names, columns names, primary key constraint names (table name + "_PK") and index names (column name + "_IX") must not exceed 30 bytes. The number of bytes that each character uses is dependent upon the character set that Oracle is using. If you see the message "Identifier is too long", then make server table names or column names shorter.

Validating Oracle Data

There are two functions that allow you to validate data in Oracle:

  1. SDO_GEOM.VALIDATE_GEOMETRY( )
  2. SDO_GEOM.VALIDATE_LAYER( )

These functions may result in validation errors due to the tolerance level set by MapInfo EasyLoader. You may get error messages such as:

"ORA-13356 adjacent points in a geometry are redundant", or "ORA-13022 polygon crosses itself"

To resolve these errors, reset the tolerance within the USER_SDO-GEOM_METADATA by adjusting them downwards (by a factor of 10) and rerun the validation.

Note: If you adjust the tolerance, you must re-create the spatial indexes because they use the tolerance when they are created.

To view the unsupported geometries in Oracle, see Unsupported Geometry.

Loading for Oracle Locator

MapInfo EasyLoader loads data for the Oracle Locator, which is the same as loading data for Oracle Spatial.