Frequently asked question

What are the expected type OID values for st_geometry in Oracle?


The following list reports type OID values in Oracle for various st_geometry types that are created when installing ArcSDE 9.3.

The type OID values must be the same on all Oracle instances in order to use Oracle's Datapump's export and import utilities with tables containing st_geometry attributes.

st_geometry OID 'A618FA8DD1D84E13B35784E171530100'
st_surface OID 'A618FA8DD1D84E13B35784E171530104'
st_curve OID 'A618FA8DD1D84E13B35784E171530102'
st_geomcollection OID 'A618FA8DD1D84E13B35784E171530106'
st_linestring OID 'A618FA8DD1D84E13B35784E171530103'
st_multicurve OID 'A618FA8DD1D84E13B35784E171530108'
st_multilinestring OID 'A618FA8DD1D84E13B35784E171530109'
st_multipoint OID 'A618FA8DD1D84E13B35784E171530107'
st_multipolygon OID 'A618FA8DD1D84E13B35784E17153010B'
st_multisurface OID 'A618FA8DD1D84E13B35784E17153010A'
st_point OID 'A618FA8DD1D84E13B35784E171530101'
st_polygon OID 'A618FA8DD1D84E13B35784E171530105'

If the type's OID values are not exactly the same, then Oracle is not able to import Oracle export files containing st_geometry attributes.

To list the types and their OID values, execute the following SQL statement in SQL*Plus as the SDE user.

SQL> SELECT type_name, type_oid
2 FROM user_types
3 ORDER BY type_name;

Type values may not be the same if the ArcSDE instance was created prior to ArcSDE 9.3. If this is the case, there is no work around or solution except to recreate the ArcSDE instance and to reload existing data.

Article ID:000010056

  • Legacy Products

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Related Information

Discover more on this topic