I'm receiving an error writing geometry (in ArcObjects) that has a large number of vertices (around 900). So big, but not ridiculously big. I would expect this to be no problem and I don't recall this issue in SQL Server or PostGreSQL. The geometry storage is ST_GEOMETRY.
The error is:
ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
..and it appears to be related to the number of vertices that the polyline has on it. Lots of vertices: I get the above-mentioned error. Less vertices: no problems.
As a test, I generalized the geometry down to two points: success.
I've started to work my way up and gotten up to 120 vertices with success. Is there a better way to determine that limit? Is there a way to increase the number of vertices that I can have on a line? Is there a DBTUNE parameter that manages this? I've googled the actual ORA error, but I'm uncertain as to how to apply this to an ArcSDE repository.
A couple of notes:
- I don't own or administer the ArcSDE repository and can't modify it.
- Breaking the long polyline feature into several smaller ones is not an option (for this project).
- Write using
feature.Shape = geometry; feature.Store();
- Code executes as expected for most of the features--I have 2 that have high number of points that cause the ORA error.
Oracle Database 11g Enterprise Edition Release 184.108.40.206.0 - 64bit Production
PL/SQL Release 220.127.116.11.0 - Production
CORE 18.104.22.168.0 Production
TNS for Linux: Version 22.214.171.124.0 - Production
NLSRTL Version 126.96.36.199.0 - Production