Vault Folder Export Error

[dmurty]

We have a repository that started with a VSS import. We are trying to clean this repository up and want to move a Folder called Archived to a different repository. To do this we are using the Vault Folder Export/Import tool. We are using Vault 4.1.3.18402. When we try to export this folder we get an error that states:
The tree structure could not be built.

When exporting this folder we chose not to export deleted items.
What can we do?

Thanks,
Damien

[Beth]

Do you know if you have ever performed any obliterates on this repository?

[dmurty]

Probably, but am not 100% for sure.

[dmurty]

Looked at the sgvault.log and found the following:
----2/25/2010 10:38:18 AM admin--HSI-NB-0268(10.0.1.20)--SSL Enabled VaultServiceSQL.VaultDbTreeException: An error was encountered looking up the owner of a folder or file for the source code tree. The tree was not built. Base TreeRevision: 48144 Target TreeRevision: 47543 TreeLevel: 3 ParentObjVerID: 0 ObjID: 7608 ObjVersion: 15 Name: Class PinFrom: 0 ParentPathHash: 0x16ED60117ED9DFE9A24F03FB9E385355 PathHash: 0x060F45BDC5C21207CA7D15AF802D7457
at VaultServiceSQL.VaultRepUtil.BuildTreeDelta(SqlDataReader dr, Int64 nBaseRevID, Int64 nTargetRevID, Hashtable htSharedItems)
at VaultServiceSQL.VaultSqlSCC.GetFolderExportRepositoryDelta(VaultSqlConn conn, String strSessionID, Int32 nRepID, Int64 nBaseRevID, Int64 nTargetRevID, VaultRepositoryDelta& rep) at VaultServiceSQL.VaultRepUtil.BuildTreeDelta(SqlDataReader dr, Int64 nBaseRevID, Int64 nTargetRevID, Hashtable htSharedItems)
at VaultServiceSQL.VaultSqlSCC.GetFolderExportRepositoryDelta(VaultSqlConn conn, String strSessionID, Int32 nRepID, Int64 nBaseRevID, Int64 nTargetRevID, VaultRepositoryDelta& rep)
----2/25/2010 10:38:18 AM admin--HSI-NB-0268(10.0.1.20)--SSL Enabled GetFolderExportRepositoryDelta returned: FailDBInvalidTreeRecords


Hope this can help pin point the issue.

Please HELP!!!!

[dmurty]

From searching some of the posts regarding this issue, I am a bit concerned that our Vault DB may be corrupt? I cannot export folders from any folder in the repository. I am affraid that there are deleted items that have not been deleted/obliterated correctly. We also have been having problems with obliterate not being able to delete items because of some branching, but we no longer have any branching. I was trying to use the vault folder export/import to move the current items to a new repository since this repository seems to have some many issues.

What can I do. I have a feeling that his has been an issue for quite some time therefore we do not have the luxury of restoring from a backup.

[Beth]

This doesn't indicate a problem with your database. At least, not at this point.

1) In the repository you want to export, select $ and perform a Show History. When the window for options comes up, click on the Actions tab. Uncheck all actions except for obliterate and click OK. Do any obliterate actions show? If there are any obliterates, then we are done troubleshooting the Export/Import, because Export/Import will not be successful with any obliterates at all in that repository.

2) With obliterate and branches, you can't obliterate the root folder the branch was made from until the branch is obliterated. That's just the rule. The branch relies on the root folder for history, and it can't exist without the root folder. If it doesn't tell you what to obliterate first, then you have deleted it. The function picks up the path from what it sees in existence now, so if the branch was deleted, but not obliterated, you will need to run a history query on your branching actions to find out what branches you made from the root folder. If you are performing this action on the repository you want to obliterate from, then you are putting it in a state where Export/Import will not work.

[dmurty]

1. I got the history of the root in the repository that I am trying to export folders from and there are obliterate actions in the history. So there is nothing I can do about moving folders from this repository to another repository?

2. I am trying to obliterate a file and it says that I have to remove the branch first, but the file I am trying to obliterate is the only file listed as being deleted. How do I fix this?

[Beth]

1) You are correct. Do you know how many updates that folder has went through? If it's just a few, then there's a manual way to move it over. If it's hundreds to thousands, then you could pick the most important versions of that folder and rebuild a reduced history. If you are interested in instructions, just let me know and I'll write some up.

2) Does the error about the branch give you a path to the branch? If so, is it possible for you to remove the file from that branch as well?

If you don't have a path to the branch, then I would suggest undeleting the file and then looking at that file's history. That should tell you about where it was branched to. Then you need to decide if you want to delete and obliterate the branch. If it's something you need, then you won't be able to do an obliterate on the file you want to obliterate. It might be possible to come up with a work-around. It will depend on how long ago the branch was made and how many changes have happened since then. Let me know up to this point what you know about it.

[dmurty]

1) OK, I can just get the latest and then add it to the other repository. Thanks.

2) When I go to the folder that the file was branched from there are no files to be undeleted. Something seems to be wrong with the state of our database. Is there anything that we can do to fix this?

[Beth]

If you right-click the folder that the file was deleted from and select properties, do you see anything in the tab labeled deleted items?

If you would like I can take a closer look. Just send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.

[dmurty]

Just sent you an email right now.

Thanks

[Beth]

I've received your email and will respond. Thanks.

HS: 219296