Select to view content in your preferred language

Continue support for registering an Oracle Spatial layer with the geodatabase without adding the SE_ANNO_CAD_DATA field to the underlying table.

912
3
11-17-2015 05:39 AM
Status: Closed
Labels (1)
AprilWilliford
Occasional Contributor

Prior to 10.3, while registering an Oracle Spatial (SDO_GEOMETRY) layer using the SDE command line, if you did not include the option for CAD data in the entity mask, the underlying table was left as-is (no additional columns were added). However, that option was not ported over in 10.3 with the deprecation of the SDE command line, so anytime you register an Oracle Spatial layer in 10.3, regardless of the type of geometry (point, line, area, CAD, etc.) a new field named SE_ANNO_CAD_DATA is automatically added to the underlying table. Adding this field changes the structure of the table unnecessarily and may break any script, application, form, procedure, etc. that relies on that structure to remain as-is.

 

Please continue to add the SE_ANNO_CAD_DATA field only when the user explicitly chooses the CAD data option.

Tags (2)
3 Comments
by Anonymous User
Changing structure of tables in order to register them is a problem.
EricVacher
I don't need and don't want this useless column added to my table.
 
ShannonShields
Status changed to: Closed

The SDO_GEOMETRY type cannot store all types of geometric elements that ArcGIS storage must support. These additional elements are written to the SE_ANNO_CAD_DATA field for Oracle Spatial data, the GDB_GEOMATTR_DATA field for SQL Server Geometry & Geography data, and PostgreSQL PostGIS data. These fields are not optional for data that is registered with the geodatabase.