Community

Annotation class in ArcSDE Geodatabase

651
2
09-26-2013 06:32 PM
NguyenThachThao
by
New Contributor III
‎09-26-2013 06:32 PM
Hi all,

I imported a Annotation Class from personal Geodatabase to ArcSDE Geodatabase but Output Feature Class have not any rows.

Error: [ATTACH=CONFIG]27810[/ATTACH]

I tried to create a Annotation Class into ArcSDE Geodatabase, after trying to load data into feature class, but Load Data is not active while I click right on Annotation Class and select Load.

So, how do I import Annotation Class from a Geodatabase to another ArcSDE Geodatabase?

Help me!
Preview file
72 KB
0 Kudos
2 Replies
NidhinKarthikeyan
by
Occasional Contributor III
‎09-27-2013 03:14 AM
A record/feature from the input could not be inserted into the output table/feature class due to problems with one of the field's values. Potential causes for this are:

The input record's text fields contain values which are longer than the output field.
The input record fields contain <NULL> values, but the output or target field does not allow NULL.
The input feature's geometry has problems (run Check Geometry on the input).
The input feature is outside the allowable extent (x, y, z, or m) of the output feature class.

Evaluate the lvalues in the input record's fields and verify that they can be stored in the output fields. If the input is a feature class or layer, run the Check Geometry tool on it.

Is it possible to attach the copy of annotation feature class for testing. If yes, then mention the version of Client/ArcSDE/RDBMS (Oracle/SQL Server).
0 Kudos
NguyenThachThao
by
New Contributor III
‎10-06-2013 11:46 PM
A record/feature from the input could not be inserted into the output table/feature class due to problems with one of the field's values. Potential causes for this are:

The input record's text fields contain values which are longer than the output field.
The input record fields contain <NULL> values, but the output or target field does not allow NULL.
The input feature's geometry has problems (run Check Geometry on the input).
The input feature is outside the allowable extent (x, y, z, or m) of the output feature class.

Evaluate the lvalues in the input record's fields and verify that they can be stored in the output fields. If the input is a feature class or layer, run the Check Geometry tool on it.

Is it possible to attach the copy of annotation feature class for testing. If yes, then mention the version of Client/ArcSDE/RDBMS (Oracle/SQL Server).


Maybe wrong is at "The input record's text fields contain values which are longer than the output field".

Thanks so much, Nidhinkn!

-ThachThao
0 Kudos