number of parts in shape is incorrect for its geometry type error on copy/paste

[JohnFannon]

Hi

I'm trying to migrate a feature class (approx 16 million records) from a 9.2 SDE database (Oracle) to a 10.1 SDE database (SQL Server). I've extracted the data from 9.2 to a file geodatabase via copy/paste successfully. However, when attempting to copy/paste from the file geodatabase to the 10.1 SDE database it fails and gives the following error:

"number of parts in shape is incorrect for its geometry type"

I've run Check Geometry and it reveals some short segments and null geometries. I've then run Repair Geometry successfully, but when attempting to copy/paste the repaired feature class I get the same error.

What I can't quite understand is that the data originates from an SDE database, albeit 9.2, so surely shouldn't have features that are not valid in SDE. Also, I would have expected Repair Geometry to fix any geometry errors.

Anyone got any idea what might be causing the data not to copy into 10.1 SDE? Also any bright ideas for a work-around would be appreciated as I need to get this data loaded.

The source system is:

SDE 9.2 sp5
ArcGIS Desktop 9.2 sp5
Oracle 10g using binary storage

The target system is:

SDE 10.1 sp1
ArcGIS Desktop 10.1 sp1 plus SQL Server 2012 patch
SQL Server 2012 with GEOMETRY storage

Cheers

John

[WaelYahya]

Can you export the schema as xml,

then create it in the destination database

then load the data in ArcCatalog usng the simple loader.

then check the count of features (QAQC) - Data reviewer can help on this

[JohnFannon]

Yep - shortly after posting my original question I did exactly that - exported the feature class schema as xml, imported the schema into 10.1 SDE and then loaded the data using the Simple Data Loader. This still reported the same geometry errors, but continued loading the remaining data.

I still don't fully understand why these features fail to load having been sourced from SDE and also after running Repair Geometry. They are line features and surely the minimum number of parts for a line is 1, or maybe even 0 for a null geometry. I'd still be interested if anyone explain what this error is likely to refer to?

Cheers

John

[VinceAngelo]

While posting the software details was very useful (thank you), you didn't include the
properties of the layers involved.  I suspect that your layer creation methodology
generated a layer with a very low X/Y scale, resulting in duplicate vertices, which,
when duplicate weeding occurs, whittles even lines down to one vertex (the minimum
is two).

Please post the 'sdelayer -o describe_long' output for the problem layer.

- V

[WaelYahya]

Yep - shortly after posting my original question I did exactly that - exported the feature class schema as xml, imported the schema into 10.1 SDE and then loaded the data using the Simple Data Loader. This still reported the same geometry errors, but continued loading the remaining data.

I still don't fully understand why these features fail to load having been sourced from SDE and also after running Repair Geometry. They are line features and surely the minimum number of parts for a line is 1, or maybe even 0 for a null geometry. I'd still be interested if anyone explain what this error is likely to refer to?

Cheers

John

Once you finished the steps mentioned before , another feature class with all problemetic features is created. Is that true?

Please zip it and send it to me.

[JohnFannon]

As request - layer details below.

Layer details for source feature class in SDE/Oracle:

ArcSDE 9.2  for Oracle10g Build 1239 Thu Jan 24 09:35:02  2008
Layer   Administration Utility
-----------------------------------------------------
Layer Description ....: <None>
Table Owner ..........: SUPPORT
Table Name ...........: BUILDING_LINE
Spatial Column .......: SHAPE
Layer Id .............: 938
SRID .................: 37
Minimum Shape Id .....: 1
Offset ...............:
  falsex:   -5220400.000000
  falsey:  -15524300.000000
System Units .........:       8000.000000
Z Offset..............:          0.000000
Z Units ..............:          1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .:          0.00025
Spatial Index ........:
  parameter:    SPIDX_GRID,GRID0=5500,GRID1=33000,FULL
  exist:        Yes
  array form:   5500,33000,0
Layer Envelope .......:
  minx:   -849475.74538, miny:   -407915.63688
  maxx:   1994492.95850, maxy:   1658210.00000
Entities .............: nslc+
Layer Type ...........: SDE-LOB
Creation Date ........: 10/04/11 11:23:33
I/O Mode .............: NORMAL
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT
Coordinate System ....: PROJCS["British_National_Grid",GEOGCS["GCS_OSGB_1936",DATUM["D_OSGB_1936",SPHEROID["Airy_1830",6377563.396,299.3249646]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",400000.0],PARAMETER["False_Northing",-100000.0],PARAMETER["Central_Meridian",-2.0],PARAMETER["Scale_Factor",0.9996012717],PARAMETER["Latitude_Of_Origin",49.0],UNIT["Meter",1.0]]

Layer Configuration ..: DEFAULTS


Layer details for target feature class in SDE/SQL Server:

ArcSDE 10.1  for SQL Server Build 768 Thu Aug 23 15:57:13  2012
Layer   Administration Utility
-----------------------------------------------------
Layer Description ....: <None>
Database              : GISLIVE
Table Owner ..........: GIS_OWNER
Table Name ...........: BUILDING_LINE
Spatial Column .......: SHAPE
Layer Id .............: 139
SRID .................: 15
Auth SRID.............: 27700
Minimum Shape Id .....: 1
Offset ...............:
  falsex:   -5220400.000000
  falsey:  -15524300.000000
System Units .........:       8000.000000
Z Offset..............:          0.000000
Z Units ..............:          1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .:          0.00025
Spatial Index ........:
  parameter:    SPIDX_MSSQL
  exist:        Yes
  array form:   -6,0,0
Layer Envelope .......:
  minx:    -58559.76713, miny:   -120653.02525
  maxx:    671780.29950, maxy:    849063.20587
Entities .............: nslc+
Layer Type ...........: In-Line Spatial Type/GEOMETRY
Creation Date ........: 03/16/13 22:06:06
I/O Mode .............: NORMAL
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT
Coordinate System ....: PROJCS["British_National_Grid",GEOGCS["GCS_OSGB_1936",DATUM["D_OSGB_1936",SPHEROID["Airy_1830",6377563.396,299.3249646]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",400000.0],PARAMETER["False_Northing",-100000.0],PARAMETER["Central_Meridian",-2.0],PARAMETER["Scale_Factor",0.9996012717],PARAMETER["Latitude_Of_Origin",49.0],UNIT["Meter",1.0]]

Layer Configuration ..: DEFAULTS

[VinceAngelo]

Hmmm.  There's nothing obvious in the source or target coordinate reference.
You'll probably want to contact Tech Support.

- V