We are running an ArcGIS 10.0 geoprocessing script written in Python that (as part of many steps above & below) runs the NEAR command.
Both the input and output datasets (shapefiles & personal geodatabase, respectively) are on a network drive, in the same projection, and we are not using a search distance (which by default = infinity, I believe). When we run the near command, sometime it successfully runs to completion and sometimes (usually) it only partially works.
When it partially works (but runs to completion), the results typically have anywhere from 1/4 to 1/2 of the features with a NEAR_DIST value = -1 (and it is always the top portion of the records, as sorted by the OID). In these cases, it also takes forever to process the top records, sometimes going from full success runs in 20 seconds to partial success runs in 1.5 hours.
Has anyone else experienced this kind of issue? Any suggestions on WHY the issue is occurring or HOW to fix the issue? I've spent countless number of hours trying to debug the issue and I am stumped...