topic Re: table not found and unable to allocate memory errors with cell statistics in ArcGIS Spatial Analyst Questions

table not found and unable to allocate memory errors with cell statistics

PamFroemke — Tue, 04 Nov 2014 14:45:18 GMT

I'm trying to run Cell Statistics in ArcMap 10.2.2 on a Win7 computer with 32GB RAM and 2TB HD. I'm getting the following errors both in Python and using modelbuilder:

The table was not found. [VAT_Qavg_53_10]

ERROR 010213: Error in reading raster Band_1.

ERROR 010325: Run-time error - ***.

ERROR 010067: Error in executing grid expression.

and

ERROR 999999: Error executing function.

The table was not found. [VAT_Qavg_53_94]

No spatial reference exists.

ERROR 010298: Unable to allocate memory.

ERROR 010067: Error in executing grid expression.

Failed to execute (CellStatistics).

I was previously able to run Cell Stats for both of these outputs using the same procedures. The output is being saved to a file geodatabase.

Re: table not found and unable to allocate memory errors with cell statistics

PamFroemke — Tue, 04 Nov 2014 20:37:59 GMT

More info on this error. This is the full error message:

Executing (Cell Statistics): CellStatistics D:\Yields.gdb\y1953_rasterV;D:\Yields.gdb\y1954_rasterV;D:\Yields.gdb\y1955_rasterV;D:\Yields.gdb\y1956_rasterV;D:\Yields.gdb\y1957_rasterV;D:\Yields.gdb\y1958_rasterV;D:\Yields.gdb\y1959_rasterV;D:\Yields.gdb\y1960_rasterV;D:\Yields.gdb\y1961_rasterV;D:\Yields.gdb\y1962_rasterV;D:\Yields.gdb\y1963_rasterV;D:\Yields.gdb\y1964_rasterV;D:\Yields.gdb\y1965_rasterV;D:\Yields.gdb\y1966_rasterV;D:\Yields.gdb\y1967_rasterV;D:\Yields.gdb\y1968_rasterV;D:\Yields.gdb\y1969_rasterV;D:\Yields.gdb\y1970_rasterV;D:\Yields.gdb\y1971_rasterV;D:\Yields.gdb\y1972_rasterV;D:\Yields.gdb\y1973_rasterV;D:\Yields.gdb\y1974_rasterV;D:\Yields.gdb\y1975_rasterV;D:\Yields.gdb\y1976_rasterV;D:\Yields.gdb\y1977_rasterV;D:\Yields.gdb\y1978_rasterV;D:\Yields.gdb\y1979_rasterV;D:\Yields.gdb\y1980_rasterV;D:\Yields.gdb\y1981_rasterV;D:\Yields.gdb\y1982_rasterV;D:\Yields.gdb\y1983_rasterV;D:\Yields.gdb\y1984_rasterV;D:\Yields.gdb\y1985_rasterV;D:\Yields.gdb\y1986_rasterV;D:\Yields.gdb\y1987_rasterV;D:\Yields.gdb\y1988_rasterV;D:\Yields.gdb\y1989_rasterV;D:\Yields.gdb\y1990_rasterV;D:\Yields.gdb\y1991_rasterV;D:\Yields.gdb\y1992_rasterV;D:\Yields.gdb\y1993_rasterV;D:\Yields.gdb\y1994_rasterV D:\Yields.gdb\Qavg_53_94_Vinod_mm MEAN DATA

Start Time: Tue Nov 04 13:35:58 2014

The table was not found. [VAT_Qavg_53_94_Vinod_mm]

ERROR 010298: Unable to allocate memory.

ERROR 010067: Error in executing grid expression.

Failed to execute (Cell Statistics).

Failed at Tue Nov 04 13:36:02 2014 (Elapsed Time: 4.28 seconds)

Re: table not found and unable to allocate memory errors with cell statistics

RebeccaStrauch__GISP — Tue, 04 Nov 2014 21:20:15 GMT

Although this may have nothing to do with it, we where getting an empty table when trying to clip two feature classes that were in two different projections. In ArcMap, of course, if you have valid spatial reference assigned, the arcmap session will take the SR of the first feature class added, and the other will project on the fly. But when we performed the clip, the projet-on-the-fly doesn't happen, so the result was blank.

So first, in ArcCatalog, look at your raster to make sure it has a valid spatial reference. If so, it should recognize it, but if you have it in an ArcMap session with a different projection, it may be having issues. My guess is it is related to one of the inputs having a different projection.

At least that is something to try. The 9999999 error is pretty much the "anyone's guess" code.

Good luck!

Re: table not found and unable to allocate memory errors with cell statistics

curtvprice — Thu, 06 Nov 2014 07:17:50 GMT

42 rasters is a pretty long list. Does it work with 30 rasters?

You may be running into a Windows operating system limits on number of simultaneously opened files. You may have to average the first half and the second half and then average the two means.

Re: table not found and unable to allocate memory errors with cell statistics

PamFroemke — Thu, 06 Nov 2014 16:59:36 GMT

I did finally get this to run yesterday by doing exactly that. I split the original number of input grids in half, ran it twice and averaged the resulting 2 grids.