Solved! Go to Solution.
... arcpy.FeatureClassToFeatureClass_conversion (input_ws + "\\" + fc, output_ws, fc_name) ...
... # Set config keyword to SDO_GEOMETRY for feature class with type LINE or POINT arcpy.FeatureClassToFeatureClass_conversion (input_ws + "\\" + fc, output_ws, fc_name, "","", "SDO_GEOMETRY") ...
I don't know what else might be going wrong, but in eighteen years of ArcSDE administration,
I have only once seen a layer that needed three levels of indexing (and its performance
was so awful we removed the features that forced the third level of indexing). You should
NOT ever add spatial indexes at the minimum interval unless the data really is distributed
so that 1+ million rows are exactly three times as large as the other 1+ million rows.
The easiest way to eliminate spatial index size from possible error status is to choose ONE
index level that is at least 1/2 as large as the gap between the coordref origin and the
center of the data envelope (e.g., with decimal degrees and a -400,400 origin, choose
a grid size of 400 -- that is, {400,0,0}). Then you can move on to the storage in the SDE
tablespace and whatever other errors which may be appearing in your database logs.
- V
The default geometry storage type changed between 9.3 and 10.1, which is probably
related to your issue
... arcpy.FeatureClassToFeatureClass_conversion (input_ws + "\\" + fc, output_ws, fc_name) ...
... # Set config keyword to SDO_GEOMETRY for feature class with type LINE or POINT arcpy.FeatureClassToFeatureClass_conversion (input_ws + "\\" + fc, output_ws, fc_name, "","", "SDO_GEOMETRY") ...