Row cannot be located for updating oracle
Geometries can be described as having linear interpolation between coordinates as defined by the Open GIS Simple Feature Specification.Geometries can also be constructed from circular curves or a combination of both interpolation methods.Oracle geometry validation routines do not implement precisely the same set of rules as the Arc GIS geometry validation.However, Arc GIS is designed to write SDO_Geometry that satisfies the Oracle validation rules.It was designed to make efficient use of database resources, to be compatible with database features such as replication and partitioning, and to provide rapid access to spatial data.Although you can define a column as type ST_Geometry, you do not insert ST_Geometry values into the column since it cannot be instantiated. ST_Geometry itself is an abstract, noninstantiated superclass. An instantiated data type is one that can be defined as a table column and have values of its type inserted into it.A text field will be created as NVARCHAR2 if the database is set to use Unicode encoding.(This is the default setting for geodatabases in Oracle.) If you set the text field size larger than 2,000 and the database is set to use Unicode encoding, the Oracle data type will be NCLOB.
For information specific to the Oracle implementation, see ST_Geometry in Oracle.
Oracle provides geometry validation routines that can be executed after inserting geometries.
Additionally, beginning with Oracle 126.96.36.199, geometry is validated on index inserts.
Information about every SDO_Geometry column should be recorded in the Oracle Spatial metadata schema, though Oracle Spatial does not do this automatically.
(The Oracle Spatial metadata schema is exposed for each schema as the view USER_SDO_GEOM_METADATA.) The software that creates SDO_Geometry columns must insert the metadata for those columns.
ST_Geometry's subclasses are divided into two categories: the base geometry subclasses and the homogeneous collection subclasses.