Select to view content in your preferred language

Archiving issue

567
2
07-25-2011 04:08 AM
RaymondGoins
Regular Contributor
I am having problems archiving my data. Here is some background and setting.

Environment:
SuSe Linux 10
arcsde 9.3
Oracle 10.2

We are a Water utility and have had some problems with our dataset. So we renamed the problem set and imported in a backed up copy. Re-enabled the versions rebuilt our geometric network and things seemed fine. I even enabled archiving and it errored out once but then after a nightly backup and compress when I enabled the backup in the morning it was fine. Now the problem...

Out of nowhere when I tried to reconcile and post data from one of our versions to the default I had an DBMS error on an A table. Looking at the TABLE_REGISTRY it seemed that table does not exist. Also I seem to have 2 history sets _H and _H1 on this particular data set. I disable archiving and then was able to reconcile and post all our versions with the default.

Now when I try to enable archiving I get an error: "Failed to enable archiving. Underlying DBMS error". No particular code or anything, just that. I am guessing it has to do with the current archiving tables and the whole process of renaming and restoring a backup data set.

I have copied all the history tables to a separate database. Is there a way to remove the current history tables, re enable archiving then import the backed up history data?? Or if someone has a solution that would be great.

Thanks in advance

Ray
0 Kudos
2 Replies
RaymondGoins
Regular Contributor
Looks like I am going to have to experiment on this one.
0 Kudos
TimLangner
Frequent Contributor
Looks like I am going to have to experiment on this one.


Hi Raymond.

Did you ever find a work around? I spoke to ESRI (UK) about this issue and they confirmed that it is not possible to create a duplicate of an archive. Using feature class to feature class causes it to become orphaned. I've not investigated it fully to see if it is the archive which is orphaned and whether ti creates many orphaned feature classes if many changes have been made over time.

I put up another thread here:
http://forums.arcgis.com/threads/40062-History-of-versioned-data-after-feature-class-to-feature-clas...

and an ArcGIS idea here, which can be promoted:
http://ideas.arcgis.com/ideaView?id=08730000000brpcAAA

Kind regards

Tim
0 Kudos