Creating folder with same name as Obliterated folder

Patrickf · Post by **Patrickf** » Thu Apr 10, 2008 12:13 pm

Vault keeps meta-data about obliterated objects. During implementation, a folder was created and then was obliterated. In trying to create a folder using the same name as the obliterated folder, Vault refuses to let this happen. Is there any way around this?

lbauer · Post by **lbauer** » Fri Apr 11, 2008 8:29 am

What version of Vault are you using?

I was able to create a folder in Vault 4.1.1, obliterate it, and create a folder with the same name.

What error do you get when you try to re-create the folder? Is there anything in your Vault server log file? The log is in % windir% \temp\sgvault on the Vault server machine.

Patrickf · Post by **Patrickf** » Sun Apr 13, 2008 12:37 pm

The version in use is 4.1.0. This issue came up with Toad and CodeControl Groups. The folder was deleted first the obliterated. Next, a new folder was added but would not show up in the Vault client although it continued to appear in the web-based administration part. The obliterated folder, in fact, never disappeared from the admin tool at all when it was obliterated. When the new folder was created, it did not show in the client and, although it would check out a package spec in Toad, the associated package body was "locked". Something keeps tell that it existed even though obliterated.

lbauer · Post by **lbauer** » Mon Apr 14, 2008 12:33 pm

You may have a pending delete action for the folder, which could explain why it is removed from the folder list. Check your pending change set list to see if an uncommitted delete transaction is listed there.

Patrickf · Post by **Patrickf** » Mon Apr 14, 2008 1:03 pm

Did you mean Undo Check Out? I did that already.

lbauer · Post by **lbauer** » Tue Apr 22, 2008 3:16 pm

No, not an undo checkout, but an orphaned transaction.

You may have an "orphaned transaction," which can happen if a commit fails, you fix the problem, but evoke the same command again with the previous command still in the pending change set.

Patrickf · Post by **Patrickf** » Tue Apr 22, 2008 3:46 pm

You may have an "orphaned transaction," which can happen if a commit fails, you fix the problem, but evoke the same command again with the previous command still in the pending change set.

I do not understand this. There are no commit failures in the pending change set. I see no "orphaned transactions". I do not know how to "fix the problem".

lbauer · Post by **lbauer** » Mon Apr 28, 2008 9:34 am

It is possible that the items survived an obliterate. Perhaps the operation timed out.

However, it is possible that your client side view is out of sync with the repository.

The first thing I would suggest is to delete your client-side cache files and flush out the server cache.
http://support.sourcegear.com/viewtopic.php?t=6

I'd suggest renaming the Vault_1 file and allow a new to be created.

So the steps would be:

Close any open clients.
Delete the client-side cache
Restart IIS, which restarts the Vault Server
Then open your client and re-connect.
You'll need to reset working directories.

Has the client-side view changed after this?

Patrickf · Post by **Patrickf** » Mon Apr 28, 2008 10:34 am

Thank you Linda. I undid everything in the Pending Change Sets that had not yet committed. After that I was able to go in and re-sync everything to the proper folders. I deleted, but did not obliterate, a folder I was using for temporary storage until this was resolved. The deleted folder does not show in either the client or admin tool so it seems we have a working solution.

Lesson learned: don't use obliterate.

lbauer · Post by **lbauer** » Tue Apr 29, 2008 12:19 pm

Thanks for the update. Glad things are in sync now.

SourceGear Support

Creating folder with same name as Obliterated folder

Creating folder with same name as Obliterated folder

Vault Obliterate