Extra Versions appearing

[robe070]

Hi,

We have recently noticed that an extra version has appeared for a file. In the attached image, version 19 is not part of this branch. Its part of a branch that is the PARENT of the current branch.

A GetLatestVersion gets version 18.

The Parent branch seems OK - version 19 is retrieved by a GetLatestVersion.

This is one instance of this we have found. We are concerned there are others and that it may have a detrimental effect in the future, though right now it is purely cosmetic.
Do you have a means of checking the database consistency?
How can we check if there are other situations like this?
Is it a known issue?
What future effects may there be?

regards

Rob Goodridge

[robe070]

...and the version is:
[26/10/2009 2:48:08 PM] Version Check: This Vault client is version 4.1.3.18336
[26/10/2009 2:48:08 PM] Version Check: Your Vault server is version 4.1.3.18336

[Beth]

What do you see for a history if you go to the file that was supposed to have that transaction?

When branching, I have seen Visual Studio continue pointing back to the original location, so we need to make sure that isn't what's happening here.

[robe070]

get of c:\dev\L4W11500_EPC845\work\x_win95\x_lansa\source\x_pdf5.c v19

GetLatest v19 Error

0-41266417e64fa4fa.png (4.09 KiB) Viewed 2637 times

GetLatest on this file gets v18

Parent and child as follows.
Parent = L4W11500_UNIX
Branch=L4W11500_EPC845
Branched at v16
Parent has had 3 more versions added to take it to v19
Branch has had one more version added plus the branch itself to take it to v18
All labels ONLY applied to branch, but Parent has 2 of those labels - the spurious labels on the branch that are in question.
Recent branch-only labels have appeared only on the branch on v18, not v19, which is correct.
Also not that the branch took place on the 8/10 but the labels occurred BEFORE this, yet are listed on a later non-existent version.

Make sure you scroll this image to see both version histories!

Comparision of Parent and Branch history

3737-41266417e6d524ca.png (33.63 KiB) Viewed 2637 times

Another file that has been physically branched in the same manner a week earlier is fine. It has the label 091006 applied, but not on the Parent. Label was applied just the once to all the files in the Branch.

Note that around about the date that this occurred, Vault became extremely slow and the Web Administrator was inaccessible. It was resolved by re-booting the Vault Server machine.
Also note that in general this is a SPARSE branch. We start by Share and Pin into this 'branch'. At some stage the branch may become different to the Parent file so only at that point do we need to physically branch just the one file. This is what has occurred with this particular file - x_pdf5.c. To obtain the correct versions of the source you get the label from the Parent that is related to the files in the branch. Then we get all the files in the Branch over the top of the label get. This gives us 2 benefits over a complete branch 1) Its far smaller so we are not chewing up heaps of disk space 2) the branch stream is directly related to the parent until we HAVE to branch. This reduces merges and makes it clear what is different between the 2 at a glance.

[Beth]

I'd like to see your entire tree layout. I think we should take this offline so that you won't have to post your entire project here. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?