Topic
  • 5 replies
  • Latest Post - ‏2013-04-01T23:50:38Z by SystemAdmin
SystemAdmin
SystemAdmin
47293 Posts

Pinned topic cannot create a snapshot view due to vob components not available

‏2013-03-30T15:02:25Z |
Hello everyone,

I can't create a snapshot view on windows because the vob doesn't have any components to select from the list. I mounted all vobs (cleartool mount -all) and I can see the components of another vob and can create a snapshot successfully on that particular vob.
But on this vob, I can't see any components on windows site even though all components can be seen on unix site.

why can't i see the components of vob on windows?

Thanks
DOC
Updated on 2013-04-01T23:50:38Z at 2013-04-01T23:50:38Z by SystemAdmin
  • Dave-Robinson
    Dave-Robinson
    116 Posts

    Re: cannot create a snapshot view due to vob components not available

    ‏2013-04-01T02:44:03Z  
    To determine your component root directories do the following command in a view:
    cleartool lscomp -long -invob <PVOB-tag>

    You might also compare the VOB tag from the registry for Windows and UNIX regions
    cleartool lsvob -long <PVOB-tag>
    cleartool lsvob -long <CVOB-tag>
    Basically it sounds like you may not have the same set of VOBs tagged in your two regions OR a VOB is tagged incorrectly.
  • SystemAdmin
    SystemAdmin
    47293 Posts

    Re: cannot create a snapshot view due to vob components not available

    ‏2013-04-01T13:47:08Z  
    To determine your component root directories do the following command in a view:
    cleartool lscomp -long -invob <PVOB-tag>

    You might also compare the VOB tag from the registry for Windows and UNIX regions
    cleartool lsvob -long <PVOB-tag>
    cleartool lsvob -long <CVOB-tag>
    Basically it sounds like you may not have the same set of VOBs tagged in your two regions OR a VOB is tagged incorrectly.
    I can see the components inside the PVOB while listing it (cleartool lscomp -l -invob <PVOB>.

    Everytime I try to create a snapshot, it gives me an error "Error determining recommended baseline. Unable to find replica in registry vob with object id"

    Do I need to import the components insode the project?

    Thanks
    DOC
  • jeff98air
    jeff98air
    817 Posts

    Re: cannot create a snapshot view due to vob components not available

    ‏2013-04-01T19:29:11Z  
    I can see the components inside the PVOB while listing it (cleartool lscomp -l -invob <PVOB>.

    Everytime I try to create a snapshot, it gives me an error "Error determining recommended baseline. Unable to find replica in registry vob with object id"

    Do I need to import the components insode the project?

    Thanks
    DOC
    As long as the PVOB is tagged in the region, you will always see all of the component names in that PVOB REGARDLESS of whether the CVOB is tagged in that region. Therefore, it may still be the case that the CVOB you can't load is not tagged in your Windows region.

    Do you see the desired VOB tag when you run `cleartool lsvob`?

    -Jeff Ng
  • brcowan
    brcowan
    733 Posts

    Re: cannot create a snapshot view due to vob components not available

    ‏2013-04-01T19:31:47Z  
    I can see the components inside the PVOB while listing it (cleartool lscomp -l -invob <PVOB>.

    Everytime I try to create a snapshot, it gives me an error "Error determining recommended baseline. Unable to find replica in registry vob with object id"

    Do I need to import the components insode the project?

    Thanks
    DOC
    At this point, you may need to look more closely at what is happening. Specifically:

    1. What are the "root directory:" entries saying for those components? If they all say <unavailable> then you need to dig deeper into why this is happening.
    2. What registry regions do you have?
    3. Is this a replicated environment? if so, did you get all the Component VOBs and their admin VOBS over to this site?
    4. Is this a restored PVOB? If so, how were the VOBs removed? And when was this backup taken in relation to the VOB removal? (perhaps during?)
    5. What is the "object ID?" This is normally a vob FAMILY identifier. So, as long as it's not a NULL object ID (all 0's) and there is only one registry server, you could try something like this (assuming Windows)
    for /f %x in ('cleartool lsregion -short') do @cleartool lsvob -region %x -family {object ID from error message}

    If you don't find it, then there is at least one missing VOB in your environment.

    =================================================================
    Brian Cowan
    Advisory Software Engineer
    ClearCase Software Advisory Team (SWAT)
    Rational Software
    IBM Software Group
    550 King St
    Littleton, MA 01460

    Phone: 1.978.899.5436
    Web: http://www.ibm.com/software/rational/support/
  • SystemAdmin
    SystemAdmin
    47293 Posts

    Re: cannot create a snapshot view due to vob components not available

    ‏2013-04-01T23:50:38Z  
    • jeff98air
    • ‏2013-04-01T19:29:11Z
    As long as the PVOB is tagged in the region, you will always see all of the component names in that PVOB REGARDLESS of whether the CVOB is tagged in that region. Therefore, it may still be the case that the CVOB you can't load is not tagged in your Windows region.

    Do you see the desired VOB tag when you run `cleartool lsvob`?

    -Jeff Ng
    Thanks all for your response.

    I have to sync some vob-tag and the issue is resolved.