Select to view content in your preferred language

Oracle FC Couldn't Displayed

2335
15
05-14-2013 10:09 PM
freddywatimena
Deactivated User
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,
0 Kudos
15 Replies
VinceAngelo
Esri Esteemed Contributor
Initial load is a special case.  After the initial data is loaded, there's enough information
to calculate an appropriate grid size, which is then used on the layer.  After that, removing
the index places the layer in load-only I/O mode.

- V
0 Kudos
KlausAlbert1
Emerging Contributor
Understood, thank's for that hint.
The layers with display errors all have a Spatial Index. Is it possible that the Spatial Indexes have been created during 'Compress'? I can't remember creating Spatial indexes acitvely (except for test feature classes).

However ESRI recommend to work with Spatial Indexes, and I would do so if I would have a solution for the display problems.

klaus
0 Kudos
VinceAngelo
Esri Esteemed Contributor
I'm not familiar enough with your workflow, but once there's enough data, the "0,0,0" index grid
is updated with something that should work, and the spatial index is built.

It isn't really a "recommendation" to edit with a spatial index present -- that's like saying that
nature feels that gravity is a good idea.

I strongly urge you to take the missing geometries problem to your Tech Support provider.
Don't get distracted by the editing without indexes issue -- you want to be using the software
as designed and supported.

- V
0 Kudos
KlausAlbert1
Emerging Contributor
Hi,
after getting in contact with ESRI support eventually we found a solution:

It is assumed, that the display problem has to do with an existing bug (NIM075426) .

The workaround is: Set the Spatial Index of the feature class > 1

We tried:
Grid1 = 1.1
Grid2 = 4
Grid3 = 15
and had success.

regards
Klaus
0 Kudos
freddywatimena
Deactivated User
My problem comes from installed oracle client.
After fix/ reinstall the oracle client ( 64 and 32 ), and rebuild the index,
everything works fine.

Thanks
0 Kudos
VinceAngelo
Esri Esteemed Contributor
You should not casually use three index levels for the spatial index grid.  In 18+ years
of ArcSDE use, I only encountered *ONE* dataset where three levels were necessary,
and the performance impact was so great that we reorganized data storage so that
three layers, each with a single-level index, were used.

One grid (N,0,0) is generally best, and if you must use two, then use N,N*5,0.
It is highly likely that 1.1,4,15 is an inappropriate grid setting, and that 1.5,15,0
will yield better performance.

- V
0 Kudos