Obliterate Issues

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Obliterate Issues

Post by cs » Fri Sep 30, 2005 4:35 am

The Vault Admin program appears to hang and is unresponsive after I click on Obliterate.

V3.1.2 is the version.

Background:

I tried to import a large project into Vault using the import tool from VSS 6.0c.

I originally had 65Gb free space. The disk filled up and the import failed after three days.

This is a large top-level project with no branches but much history.

I now realise we may have to only import the most recent labels to get a usable size database.

I am trying to delete the failed import using Obliterate before we attempt another import.

I don't want to delete the entire database as we have other projects in there which are being worked on.

I have read the various posts about obliterate, IIS timeouts, etc., and changed the various timeouts.

I ran a trace of an attempted Obliterate using SQL Profiler, of which a screenshot is attached.

The last call to spcheckadmingroup is only ever followed by repeated Audit Login/Audit Logout entries by Vault.

How long is the spcheckadmingroup stored procedure (or whatever is running) likely to take?

It runs for hours with ~100% CPU from SQL Server but I am unsure if anything worthwhile is happening.

Do I leave it to run longer?

Any guidance in removing the failed import would be appreciated.

Update:

After a few hours, the Obliterate timed-out with the 'session timeout' error dialog appearing. I have increased the timeouts as per your KB article, in IIS Manager.

Thanks
Attachments
trace.JPG
Sample Obliterate Trace
trace.JPG (271.12 KiB) Viewed 11352 times

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Sep 30, 2005 8:08 am

Although we've made improvements to Obliterate, it is still slower than we'd like and we're continuing to work on it.

In the meantime --

Some users have had better results using Obliterate from the Command Line Client rather than from the Admin Tool.

For documentation on the CLC, cd to the Vault Client directory from a command prompt and type "Vault help obliterate" or "Vault helphtml" for help in HTML format.
Linda Bauer
SourceGear
Technical Support Manager

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Project Gone

Post by cs » Fri Sep 30, 2005 8:14 am

The project has disappeared from view in the projects list using the Windows Vault Client.

Can I still Obliterate it?

Note the 60Gb of space is still used up.

How can I recover the space and cleanly delete the 'project'?

Thanks

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Syntax Help

Post by cs » Fri Sep 30, 2005 9:07 am

I am attempting to use the command line client to Obliterate 'myproject' as:

vault.exe OBLITERATE myproject -host myserver -user myadmin -password myadminpwd -repository default

I get the error:

Invalid repository path: myproject

(This happens with any project, even ones which are visible in the Windows Client)

Please can you correct my syntax.

Thanks

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Sep 30, 2005 9:20 am

Repository path would be "$/myproject" or "$/parentfolder/myproject", etc., whatever the path was in the folder tree.

Also, is your repository named "default" or "Default Repository" ?

Obliterate is only for items which have been deleted, not for items viewable in the tree. You can see deleted items in the Folder Properties of the parent folder.
Linda Bauer
SourceGear
Technical Support Manager

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Thanks

Post by cs » Fri Sep 30, 2005 9:41 am

Running now via command line.

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Failed

Post by cs » Mon Oct 03, 2005 2:09 am

After a few hours, Obliterate failed from command prompt with following errors:

<vault>
<error>
The Vault server could not be contacted to perform the operation. Your network
connection to the server may have been interrupted. Please verify your network
settings using the Options dialog under the Tools menu in the Vault GUI Client.T
he operation has timed-out.
</error>
<exception>
System.Exception: The Vault server could not be contacted to perform the operati
on. Your network connection to the server may have been interrupted. Please ve
rify your network settings using the Options dialog under the Tools menu in the
Vault GUI Client.The operation has timed-out.
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]
& requests, String& strTxID, String comment)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandObliterate(String strR
eposPath)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>

The command line was running on the Vault server.

The Vault Windows client connected to the server no problem afterwards.

No disk space was recovered.

The project I was attempting to obliterate is still listed as a Deleted Item in its parent project.

How can I obliterate the project?

I'm prepared to do any manual operations to recover the 60Gb disk space and tidy up the database.

Thanks

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Mon Oct 03, 2005 7:46 am

At this point I'd recommend that you attempt the obliterate right on the SQL Server. Near the beginning of the profile you were running, you should see a call to the stored procedure that performs the obliterate. Something like this:

<snip>
Note from Ian: this script is not "safe" under all circumstances, so it has been removed. See http://support.sourcegear.com/viewtopic ... 9094#19094
</snip>
Last edited by ian_sg on Wed Oct 12, 2005 9:02 am, edited 2 times in total.
Ian Olsen
SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Started

Post by cs » Mon Oct 03, 2005 8:23 am

Started with @reallyobliterate = 0

Thanks

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Still Running

Post by cs » Tue Oct 04, 2005 5:18 am

21 hours running.

No disk space recovered as yet.

SQL Server process using ~90% CPU

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Still Running

Post by cs » Wed Oct 05, 2005 2:20 am

42 hours running.

No disk space recovered as yet.

SQL Server process using ~90% CPU

No users are using Vault during the obliterate. Can they safely?

Thanks

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Wed Oct 05, 2005 7:17 am

With @reallyobliterate=0, you should have no trouble using the system other than a perceptible slowness while it's running.

With @reallyobliterate=1, running directly from SQL as you are, you would be safest letting the obliterate finish before using the repository.
Ian Olsen
SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Still Running

Post by cs » Thu Oct 06, 2005 1:42 am

65 hours, SQL Server high CPU.

To clarify, I'm using @reallyobliterate=0 to get ballpark of how long this will take, so shouldn't expect any disk space recovered this time.

Vault is unresponsive to other users and Vault Client program is reporting transaction failures when check-ins are attempted. I can live with this for now if the dummy obliterate ends in the next few days.

Thanks

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Still Running

Post by cs » Fri Oct 07, 2005 2:32 am

90 hours

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Still Running

Post by cs » Mon Oct 10, 2005 6:37 am

166 hours

Locked