Bug: Enabling archiving on an annotation class in Oracle can potentially result in a Network I/O error
Enabling geodatabase archiving that contains a large number of attribute fields on an annotation class in Oracle and where the annotation element attribute is stored as an Oracle LONG RAW type, can result in a Network I/O error.
The combination of the number of attributes and the element attribute being stored as an Oracle LONG RAW attribute can lead to a Network I/O error.
Ensure the annotation class element attribute is stored as an Oracle BLOB attribute.
The annotation class can either be reloaded and the ArcSDE DBTUNE parameter attribute_binary can be set to 'BLOB' or by following the instructions in the ESRI White Paper, "Converting from LONG RAW to BLOB in an ArcSDE for Oracle Geodatabase".
Once the element attribute is no longer stored using Oracle's LONG RAW attribute, enabling archiving is successful.
- Can reconcile performance be improved by converting Oracle LONG RAW attributes to BLOB attributes?
- Converting from LONG RAW to BLOB in an ArcSDE for Oracle Geodatabase