Select to view content in your preferred language

ArcGIS Pro Data Index stalls

254
4
4 weeks ago
Labels (2)
LyonMNGIS
Frequent Contributor

Hello,

ArcGIS Pro will only index a portion of my GIS data before canceling out after about 50,000 records. Is there any reason why the index will not complete?

*note, the Arc Catalog index is quicker and does not have any issues.

LyonMNGIS_0-1744984431171.png

 

0 Kudos
4 Replies
Robert_LeClair
Esri Esteemed Contributor

Two of the most common reasons this fails in ArcGIS Pro are your spatial grid indexes and attribute indexes may be stale and need to be refreshed/recalculated.  If you're working in eGBD's, you can use the Rebuild Indexes (Data Management) GP tool to rebuild indexes.  If a fGDB, then in the Catalog Pane, you can right-click on the FC->properties, click the Index tab on the left and rebuild indexes on the right side of the pane.

0 Kudos
LyonMNGIS
Frequent Contributor

Robert,

I apologize.  I am referring to a data catalog index not a attribute/spatial index.

 

LyonMNGIS_0-1745327379645.png

 

TimOrmsby
Esri Regular Contributor

Hi LyonMNGIS,

I don't think there's an obvious reason why the indexer would fail on you--there's no record limitation, for instance. It might be encountering bad data somewhere in the file, but that seems questionable since you're able to index the same data (right?) without problems in ArcCatalog.

You should probably open a case with technical support so they can repro and diagnose the problem. If you don't have support authorization, I think you can still open a case with them because it's a software bug--at least it seems to be.

Btw, this index is referred to in our doc as the "resource index." See How projects are indexed. But I'm not sure that name is widely known, and your suggestion on the ArcGIS Ideas site of "Data catalog index" or something like that might be better.

KoryKramer
Esri Community Moderator

@LyonMNGIS as stated on the thread, there isn't a know reason why indexing would stop as there is no built-in limit. If you're able to share the data that causes the problem, the best way to do that will be through submitting a case with Technical Support. Thank you

0 Kudos