Oracle FC Couldn't Displayed

freddywatimena · ‎05-14-2013

Hi Forums,

We face problem on displaying feature class in Oracle, which successfully imported from file geodatabase using Append (Data Management) Tools, my experiment on copying it to Postgre no problem on displaying it.

Is this problem on permission setting in Oracle ?
If we select the record, selected object appears.

I attach the capture screen related to the problem,
[ATTACH=CONFIG]24314[/ATTACH]

Thanks,

KonradLorch · ‎05-15-2013

Hi,
we have the same problem.
All database records of the Oracle FC are present, but not visible in the map.
Interestingly not all of them...some geometries are displayed.

When deleting the Spatial Index all geometries are visible but now it is no longer possible to start an edit session (see screenshot).

Any ideas why?

Thanks,

VinceAngelo · ‎05-15-2013

You're missing quite a number of details that are critical to getting assistance.

What version of ArcGIS are you using? What service pack?

What database are you using? (exact release to four places)

What storage type are you using?

If you're using SDO_GEOMETRY, how have you defined the USER_SDO_GEOM_METADATA?

What is the spatial extent of the layer?

While screenshots can be useful in some situations, it's critically important to get the
text of relevant error messages in your post -- This allows search engines to find the
content, and help the next person with the same problem. This particular error message
is unrelated to the problem (you can't edit without a spatial index).

- V

KonradLorch · ‎05-15-2013

Hi,

we're using:

ArcGIS 10 SP 3
Oracle 11g R1 (64bit) 11.1.0.7
Storage Type: ST_GEOMETRY (default)

Spatial Extent is:
Max X: 9006799.25474099 Degree
Max Y: 9006799.25474099 Degree
Min X: -400
Min Y: -400

Thanks,

VinceAngelo · ‎05-15-2013

I doubt you have data at nine million degrees north or east (that's the extent of
the coordinate reference). What is the spatial extent of the *data* in the layer?

How did you create the layer?

What does 'sdelayer -o describe_long' report for the layer?

Is there a common property to the features which do not render when the
spatial index is present?

How is the rowid column defined? Are any of the values negative?

- V

KonradLorch · ‎05-15-2013

Ok, the data extent is

Top: 78.929747 dd
Right: 33.634100 dd
Bottom: 24.163067 dd
Left: 31.133161 dd

Initially we created the layer with the default commands New>FeatureClass>etc., granded privileges and registered it as versioned.

The layers are quite dynamic, meaning that there are (daily) attribute changes and/or geometry adds/deletions.
And not all layers are affected...others work pretty well.

No, there are no common properties. Different areas, different geometries, etc.

Not sure what you mean with 'rowid'...we have the default OBJECTID without any negative values.

These are the reports for the layers with and without spatial index:
1) result for the layer that�??s spatial index has been removed, and that now denies editing (even for the owner VFR)

Layer Description ....: <None>
Table Owner ..........: VFR
Table Name ...........: GEOC_AVI_RWYL_COPY
Spatial Column .......: SHAPE
Layer Id .............: 1338
SRID .................: 8
Auth SRID.............: 7
Minimum Shape Id .....: 1
Offset ...............:
falsex:       -400.000000
falsey:       -400.000000
System Units .........: 1000000000.000000
Z Offset..............:          0.000000
Z Units ..............:          1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .:          0.000000008983
Spatial Index ........:
parameter:    SPIDX_GRID,GRID0=0.034,FULL
exist:        No
array form:   0.034,0,0
Layer Envelope .......:
minx:       -31.13316,      miny:        24.16307
maxx:        33.63410,      maxy:        78.92975
Entities .............: nslc+
Layer Type ...........: Extended SQL Type/ST_GEOMETRY
Creation Date ........: 05/15/13 09:38:09
I/O Mode .............: LOAD
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT, UPDATE, INSERT, DELETE
Coordinate System ....: GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]

Layer Configuration ..: DEFAULTS

2) result for the layer that does not display properly (not all features) and that has a spatial index.

Layer Description ....: <None>
Table Owner ..........: VFR
Table Name ...........: GEOC_AVI_RWYL
Spatial Column .......: SHAPE
Layer Id .............: 1205
SRID .................: 8
Auth SRID.............: 7
Minimum Shape Id .....: 1
Offset ...............:
falsex:       -400.000000
falsey:       -400.000000
System Units .........: 1000000000.000000
Z Offset..............:          0.000000
Z Units ..............:          1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .:          0.000000008983
Spatial Index ........:
parameter:    SPIDX_GRID,GRID0=0.034,FULL
exist:        Yes
array form:   0.034,0,0
Layer Envelope .......:
minx:       -31.13316,      miny:        24.16307
maxx:        33.63410,      maxy:        78.92975
Entities .............: nslc+
Layer Type ...........: Extended SQL Type/ST_GEOMETRY
Creation Date ........: 01/22/13 15:04:40
I/O Mode .............: NORMAL
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT, UPDATE, INSERT, DELETE
Coordinate System ....: GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]

Layer Configuration ..: DEFAULTS

VinceAngelo · ‎05-15-2013

The layer you can't edit is in Load-Only I/O mode. You must build the spatial index.

- V

KlausAlbert1 · ‎05-15-2013

Hello Vince,
I took over from Konrad,
thanks for your reply, but this is exactly our vicious circle.

If I recreate a spatial index (using ArcCatalg) I'm again able to edit the data, but I run into the display problems from the beginning.

regards
Klaus

VinceAngelo · ‎05-15-2013

Since you can't ever "fix" the problem of editing a layer in Load-Only I/O mode, let's work
on addressing the missing geometries. I can't help but wonder if the version tree has
been mangled, since I don't think you're supposed to be able to place a layer in load-only
I/O mode while versioned. This is probably an issue to take to Tech Support, but I can
take one more stab at it before placing you in their more capable hands.

- V

KlausAlbert1 · ‎05-15-2013

What I don't undersand is:
if I create a new SDE feature class, register it as versioned and load data, the feature class doesn't have a Spatial Index but displays correctly and can be edited. it seems it is not in Load Only I/O mode

So, why does adding a Spatial Index and deleting it later on changes the feature class in Load Only I/O mode?

klaus