FAQ: Why does ArcMap fail when moving some Oracle Spatial polygon curve features in the same feature class?
Why does ArcMap fail when moving some Oracle Spatial polygon curve features in the same feature class?
This is due to a bug in Oracle Spatial (Oracle TAR 1558578.999), where selections using an ORDER BY clause that selects SDO_GEOMETRY types with more that 4000+ ordinates fail with:
ORA-22813: operand value exceeds system limits
This affects ArcMap when edits, such as move feature, are performed. This is because shape, objectid, and state_id use an ORDER BY in the version select expression.
On Windows NT you get an error on the client (underlying DBMS error). If connected to a Solaris server, you get shadow features that go away on the next refresh. In both cases you end up with the same error in the error logs.
Performing the same operation using feature classes stored using ArcSDE compressed binary works fine.