Prune Branch History Not Working

[LRoberts_RDM]

We are using a Trace Network which requires us to use branch versioning. One of our layers is updated each night with new information so the layer is growing very quickly, and we are beginning to see performance issues. We found that in the latest ArcGIS Pro release there is a new tool called Prune Branch History. When we run it, we get the following error. I cannot find any useful information online as to why this would be. We are using a branch version connection to the feature data set, we are disconnecting all users from the database before running.

Here are a few more shots of our environment.

GDB version

ArcGIS Pro version

Trace Network version

[AyanPalit]

@LRoberts_RDM Yeah, as stated Prune Branch History is new at Pro 3.5.

Looks like the error is specific to Water_TN - Check the layer properties > Manage. Is it branch versioned correctly?

Here are some tips:

• The dataset must be registered as branch versioned.

• The tool can only be run by the data owner.

• An exclusive schema lock is required to run the tool. Services referencing the input data will need to be stopped using ArcGIS Server Manager.

• Conduct a test run—Use the tool with the Report Only option enabled. This method will not prune any data; it simply provides a report in the Output Log File result on the number of archived records that could be pruned.

• Log file review—After running the tool, review the Output Log File result created to see how many archive records are eligible for pruning. Monitor log files for any warnings or errors related to the pruning process and take appropriate action.

• Timing of running the tool—To reduce system impact, it's best to run the tool during off-peak hours, on weekends, or at times when the feature service referencing the branch-versioned dataset can be stopped.

Reference: Prune branch history

Please share your findings with the community.

[JCGuarneri]

I'm trying to run this tool and running into a different issue. I'm unable to get an exclusive schema lock. I've shut off all the services that access the DB in question, and confirmed that there are no other connections or locks (at least as far as Pro can see). The tool fails with a schema lock error every time. This is a dev database that has basically no traffic except when I am testing against it. Anything else I should be looking at?

For additional context, I'm pruning the history of a non-spatial table that's related to a Utility Network feature class.

[NanaDei · Accepted solution]

@LRoberts_RDM - The tool currently doesn’t support the Trace Network. We have plans to extend it to support Trace Network and Parcel Fabric datasets in a future release.

[AmyRoust]

What about Utility Networks? Same situation?

[AyanPalit]

@AmyRoust Utility Network dataset is supported. Give it a try following the pre-requisites posted in links above. Please share back your experience. 

[AmyRoust]

I ended up unregistering the entire dataset, which cleared out the entire history. The tool seemed to work fine, but unregistering really got things moving fast again. I re-registered as branch versioned and plan to incorporate that pruning tool in my workflows where I have Python scripts that batch update data.

[AyanPalit]

@LRoberts_RDM Quick follow-up, please post a screenshot of the Prune Branch History tool parameters.

Specifically,  the Only Prune System Tables parameter. Do you see any difference checking/unchecking this option.