add mosaics to mosaic dataset error

[JamieKass]

I am getting this error when trying to add mosaic datasets to a master mosaic in ArcMap 10.0 SP3, with the intention of creating a time-aware mosaic to reference my others with a year field (nearly identical to the short tutorial in the ArcGIS Help (http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//009t000000v1000000).

Error: 80042010: Could not insert a row containing a raster dataset into the mosaic catalog

Has anyone seen this error before? The tool does not fail, but keeps populating empty records into the mosaic. There is no reference online for this error.

[JeffreySwain]

Was the master mosaic dataset and the subsequently created mosaic datasets created at the same service pack?  Or was the original created at one level and the rest at other levels?  If so I would recommend creating a new geodatabase or new mosaic dataset and adding all the intermediate mosaic datasets again.

[DavidLowell]

I'm having the exact same issue. 
both mosaic datasets and master dataset were created at the same version/service pack.
Have you determined the issue?

[AngeloCirocco]

Hi,

I had the same error. 
It was due to the fact that I had Raster set to be stored as SDO_GEORASTER in the DBTUNE as a result of using the dbtune.sdo file when I installed ArcSDE to use SDO_GEOMETRY for vector data.
I updated the DBTUNE table using sdedbtune command to SDELOB and the problem was resolved.

Hope this helps,

Angelo Cirocco
Professional Services Senior Consultant
Esri Australia

[ShaunWeston]

Is the above answer the solution to this problem? I'm just encountering this problem at the moment. Works fine with file geodatabases but when trying to add mosaic datasets to another mosaic dataset in SDE, it comes up with the error above.

[JeffreySwain]

This appears to be an issue with the SDE version of a Mosaic Dataset.  It is reported in the bug report NIM084428.  It is still being worked on, as a workaround the recommendation is to use a file geodatabase.

[ShaunWeston]

Sweet thanks for confirming that as an issue 🙂