Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why am I unable to put my layer in normal_io mode after loading a large shapefile, coverage or sdeexport file with the ArcSDE data loading tools shp2sde, cov2sde, sdeimport?

0
Posted

Why am I unable to put my layer in normal_io mode after loading a large shapefile, coverage or sdeexport file with the ArcSDE data loading tools shp2sde, cov2sde, sdeimport?

0

If you get an OLEDB error when attempting to put a layer into normal_io mode, you will need to use one of three known workarounds: 1. Obtain and install MDAC 2.5. MDAC 2.5 is available through Windows 2000 and will be released for Windows NT in February 2000. 2. Use the ArcInfo 8.0.2 desktop data loading tools: ArcCatalog, ArcToolbox, and the feature data converters or load all data in normal_io. 3. Shut down the ArcSDE service and set the ATTRBUFSIZE to 1000 or smaller. This option may not always work. For example: Your export file loaded but failed to build the spatial index. You are now left with a layer stuck in load_only_io. Truncate the layer with sdelayer -o truncate, then place the layer into normal_io with sdelayer -o normal_io, then perform an sdeimport -o append. Most append options in the shape loader commands (shp2sde, etc) will load data in normal_io if the layer is set to normal_io. Another symptom of this problem is when shp2sde and cov2sde’s -c and -v options appear to

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123