DB state after a failed obliterate

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
BenV
Posts: 10
Joined: Sat Mar 29, 2008 10:43 am

DB state after a failed obliterate

Post by BenV » Sat Mar 29, 2008 10:55 am

I am trying to obliterate a folder and after some time of waiting I get a message saying that the connection to Vault have timed out. I then open up my Vault Client and saw that the folder I tried to obliterate is no longer there.

My question now is, what is the state of the data in the database when the obliterate command loses connection to the Vault server due to a timeout. Is the data still in the database? Have they been successfully removed? If the data is still in the database, how do I remove them?

Thank you,

Ben V.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Mar 31, 2008 9:12 am

The way to tell if it's still in the database is to return to the obliterate tab in the admin tool and see if it's listed there.

When looking in the client, you won't see a deleted folder in the regular tree, but could find it if you view the properties of its parent folder. If the folder was obliterated, then you wouldn't see it listed as deleted.

To change your timeout time, go to your vault.config file on the Vault server in the Vault virtual directory. There will be an entry for a SQL timeout in that file that is set to 360 by default. I usually have people add a '0' to the end for the first number to try. It may take performing an iisreset for the change.

Could you also check your Vault Server Log for errors from that transaction?

BenV
Posts: 10
Joined: Sat Mar 29, 2008 10:43 am

Post by BenV » Mon Mar 31, 2008 10:38 am

Beth,

Thank you very much for your reply. The SQL time that you mentioned, is that in the units of seconds or minutes? The timeout usually occurs after around 3 hours so I am not quite sure how to guage this value of 360.

Increasing this SQLCommandTimeout will increase the time that have caused this error, "The Vault server could not be contacted to perform the operation. Your network connection to the server may have been interrupted.", is that correct?

Thank you so much for your response.
Ben V.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Mar 31, 2008 12:37 pm

If the error in the server log is a SQL timeout, then that's correct. Without seeing either the log or a chunk from a couple minutes before the errors through about half a dozen lines of the error I couldn't tell exactly. Can you either post the server log here or email it to me? If you choose email, send it to support at sourcegear.com (attn: Beth) with a link to this forum thread.

The losing connection to the database could also be a networking problem.

BenV
Posts: 10
Joined: Sat Mar 29, 2008 10:43 am

Post by BenV » Mon Mar 31, 2008 4:27 pm

I doubt that I will be able to find the portion of the server log from where the error occurred. However, I am glad to hear that the folder is actually obliterated even though this timeout have occurred. I would hate to have this error come up again and leave the data in the database without a way to remove them.

Once again, thank you for your help.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Mar 31, 2008 5:13 pm

The information on the log to check can be found here: Vault Server Log. That's where you want to check for errors.

Post Reply