topic Re: Enable Archiving Fail in Data Management Questions

Enable Archiving Fail

GlenColgate — Tue, 15 Apr 2014 22:24:31 GMT

The error I keep getting is

Failed to enable archiving. Invalid column data type.

Setup is: ArcGIS Desktop 10.2.0.3348; SDE Enterprise Geodatabase 10.2.0; Oracle 11.2.0.3.0

I am trying to enable archiving on nonversioned data using 10.2.0. (and failing miserably). It is possible according to online help (LINK). I can't find anything describing this as an added feature for 10.2.1 or 10.2.2 (or a known bug in 10.2.0).

Any thoughts?

Re: Enable Archiving Fail

VinceAngelo — Tue, 15 Apr 2014 22:44:52 GMT

Since it's complaining about column types, please provide a list of the columns with types. Be sure to specify which one is the registered rowid, and whether it's SDE-set or USER-set. -V

Re: Enable Archiving Fail

GlenColgate — Sun, 12 Dec 2021 03:03:00 GMT

The error happens even when I create a new FC accepting all of the defaults:

Name                                      Null?    Type
----------------------------------------- -------- ----------

OBJECTID                                  NOT NULL NUMBER(38)
SHAPE                                              NUMBER(38)

no frills here... OBJECTID is the reg'd rowid (SDE-set of course), and SHAPE is the geometry.

Re: Enable Archiving Fail

GlenColgate — Sun, 12 Dec 2021 03:03:03 GMT

...just did the same test using a config keyword to create SDO_GEOMETRY and the archive seems to have completed normally...

 Name                                      Null?    Type
 ----------------------------------------- -------- --------------------

 OBJECTID                                  NOT NULL NUMBER(38)
 SHAPE                                              MDSYS.SDO_GEOMETRY
 SE_ANNO_CAD_DATA                                   BLOB
 GDB_FROM_DATE                             NOT NULL TIMESTAMP(6)
 GDB_TO_DATE                               NOT NULL TIMESTAMP(6)
 GDB_ARCHIVE_OID                           NOT NULL NUMBER(38)

Re: Enable Archiving Fail

VinceAngelo — Wed, 16 Apr 2014 00:21:22 GMT

ST_GEOMETRY should be the default storage type by now.

- V

Re: Enable Archiving Fail

GlenColgate — Wed, 16 Apr 2014 13:22:13 GMT

Guess we'll call this one solved.

The geometry column was the culprit. When default config key was used the field was being defined as a NUMBER(38), likely holding compressed binary, without versioning, nonversioned archiving did not like this field type.

Tried the same with SDO_GEOMETRY and ST_GEOMETRY and nonversioned archiving apparantly works.

Re: Enable Archiving Fail

SebastianRoberts — Tue, 29 Apr 2014 16:55:43 GMT

Thanks for this post. I was getting the same error when trying to enable archiving on a feature dataset that isn't versioned. I had some feature classes in there that were created at 10.0 or earlier so their geometry type was SDEBINARY. Confirming that the GEOMETRY_STORAGE parameter is set to GEOMETRY (SQL server) for the DEFAULTS keyword in the SDE_bdtune table, and then using the Migrate Storage geoprocessing tool with the DEFAULTS keyword fixed the issue for me.

Re: Enable Archiving Fail

TilmannSteinmetz — Mon, 05 May 2014 02:21:39 GMT

I've done the same tests as Glen (in both 10.2 and 10.2.1 Geodatabases) and see the same results (works with GEOMETRY & fails when I try it with a vanialla SDEBINARY fc). Difference being that I want my dataset to be stored as SDEBINARY. The help for 10.2/10.2.1/10.2.2 only says: "Geodatabase archiving is now supported on tables that are not registered as versioned" - no mention of storage types so I was under the impression that this would work for all available storage types.

Is this supposed to be working with SDEBINARY or not?

Thanks!

Tilmann

Re: Enable Archiving Fail

MelissaJarman — Tue, 24 Jun 2014 18:56:42 GMT

This has been logged as a documentation enhancement as non-versioned archiving is supported on tables and sql spatial types such as SQL Server Geometry\ST_GEOMETRY\SDO_geometry but not older geometry types such as SDEBINARY\SDELOB:

NIM102878 - The "Enabling archiving on nonversioned data" section of the link below doesn't highlight the unsupportability of SDEBNARY or SDELOB feature classes.

http://resources.arcgis.com/en/help/main/10.2/index.html#/Enabling_archiving/003n000000rs000000/