Canceling UCM rebase fails with error: cleartool: Error: View "Dev_View" is not the view in which you started this operation

Technote (troubleshooting)


Problem(Abstract)

This technote explains why canceling an IBM® Rational® ClearCase® UCM rebase operation fails with the error, cleartool: Error: Rebase in progress on stream "Development_Stream" using view "Shared_Dev_View" does not match the view specified, and provides a solution to resolve the problem.

Symptom

Attempt to cancel a rebase operation fails with the following error:


# cleartool rebase -cancel -view Dev_View

Rebase in progress on stream "Development_Stream".
Started by "Joe_User" at 09/10/01 16:15:16.
cleartool: Error: Rebase in progress on stream "Development_Stream" using view "Shared_Dev_View" does not match the view specified.
cleartool: Error: View "Dev_View" is not the view in which you started this operation.
cleartool: Error: Unable to cancel rebase.


Cause

The UCM views, Dev_View and Shared_Dev_View, are attached to the same stream, Development_Stream.

The rebase in this case was originally started in Shared_Dev_View, but the cancel operation is being attempted from Development_View.

Generally, the views can be alternated for working on the stream, however, a rebase must be started and completed or canceled in the same view.

Note: The above error will occur when the original view has been removed or for some reason cannot be accessed on the ClearCase network.


Resolving the problem


Where the Development view still exists and is accessible

When possible, the rebase operation should be canceled from within the view that it was originally started from.

Example:

To resolve the above error, the rebase needs to be canceled from Shared_Dev_View:


    # cleartool rebase -cancel -view Shared_Dev_View


Where the Development view is inaccessible

There are instances where the original development view that was used to start the rebase is no longer available on the ClearCase network.

The view may no longer exist, or it may still exist but it is not accessible.

Note: In cases where the view still exists, but is not accessible, you should attempt to resolve the problem that is preventing access to the view, then resume or cancel the rebase in that view. Otherwise, after completing this procedure, the view may be left in a corrupted state and will need to be removed.

To cancel a rebase when the original development view cannot be used, you can reset the rebase state on the stream.

Note: The rebase that is in progress cannot be resumed in a new view. It must be canceled, then start the rebase again in the new development view.

  1. Canceling the rebase in a new view fails with the same error as seen above:

    C:\>cleartool rebase -cancel -view prj1_dev_vu2
    Rebase in progress on stream "prj1_dev".
    Started by "administrator" at 6/7/2006 3:51:07 PM.
    cleartool: Error: Rebase in progress on stream "prj1_dev" using
    view "prj1_dev_vu" does not match the view specified.
    cleartool: Error: View "prj1_dev_vu2" is not the view in which you started this operation.
    cleartool: Error: Unable to cancel rebase.


  2. Attempting to resume the rebase in a new view fails with:

    C:\>cleartool rebase -resume -view prj1_dev_vu2
    Rebase in progress on stream "prj1_dev".
    Started by "administrator" at 6/7/2006 3:51:07 PM.
    cleartool: Error: Rebase in progress on stream "prj1_dev" using
    view "prj1_dev_vu" does not match the view specified.
    cleartool: Error: View "prj1_dev_vu2" is not the view in which you started this operation.
    cleartool: Error: Rebase in progress on stream "prj1_dev" using
    view "prj1_dev_vu" does not match the view specified.
    cleartool: Error: Unable to resume rebase.

  3. List the rebase status for the stream, and make note of the Integration activity:

    Note: The Integration activity is also referred to as the rebase activity.

    C:\>cleartool rebase -status -stream prj1_dev@\PVOB1
    Rebase operation in progress on stream "stream:prj1_dev@\PVOB1"
    Operation is currently being canceled - some data may already have been removed.
       Started by "administrator" on "07-Jun-06.15:51:07"
       
    Using integration activity "rebase.prj1_dev.20060607.155107".
       Using view "prj1_dev_vu".
       Integration Stream Baselines:
           baseline:comp2_INITIAL@\PVOB1
           baseline:prj1_6_7_2006@\PVOB1
           Activities included in this operation:
           activity:testfix@\PVOB1


  4. Dump the Integration activity to verify the UCM_INTEGRATION_ACTIVITY variable has a state = 1:

    Note: In this state, the activity cannot be unset using cleartool setact -none, because the activity is currently set in a view and in use for a rebase. A state = 0 indicates that it is not in use.

    C:\>cleartool dump -long activity:rebase.prj1_dev.20060607.155107@\PVOB1

    rebase.prj1_dev.20060607.155107
    oid=65ab151f.be174326.bd74.0d:b4:67:75:c1:96  dbid=182 (0xb6)
    mtype=activity  name="rebase.prj1_dev.20060607.155107"  type=73
    usid=NT:S-1-5-21-2901646739-668246498-978699657-500  gsid=NT:S-1-5-21-29016
    master replica dbid=3
    title="rebase prj1_dev on 6/7/2006 3:51:07 PM."
    process definition uuid=511ffb23.373c4375.a60f.4c:03:2f:f9:91:83
    ...
    Process variables:
    name=UCM_INTEGRATION_ACTIVITY  value=ver=1
    state=1

    ...


  5. Dump the stream that the rebase was started from, and you will see the UCM_REBASE variable is set to some number:

    Note: The UCM_REBASE variable will not be listed in the output when the stream does not have a rebase in progress.

    C:\>cleartool dump -long stream:prj1_dev@\PVOB1

    prj1_dev
    oid=9f2050b1.26244de0.aadd.88:75:70:18:6d:16  dbid=117 (0x75)
    mtype=activity  name="prj1_dev"  type=85
    usid=NT:S-1-5-21-2901646739-668246498-978699657-500  gsid=NT:S-1-5-21-29016...
    master replica dbid=3
    title=""
    process definition uuid=c1c05e41.c72b44d1.b98a.4a:17:a3:77:25:66
    state dbid=64
    role dbid=52
    user dbids: 106
    config spec:
    ucm
    ...
    Process variables:
    name=SUM_CSPEC_ID  value=0:5
    name=UCM_DELIVER_INTEGRATION_VIEW value=890d35ae.f03e4ec3.b8ad.a5:df:63:35:62:14
    name=UCM_REBASE  value=ver=2
    ...

  6. Clear the state of the Integration activity:

    C:\>ucmutil setpvar -pvar UCM_INTEGRATION_ACTIVITY -none activity:rebase.prj1_dev.20060607.155107@\PVOB1
    ucmutil: Warning: VOB is replicated; can only repair objects mastered in this replica.
    You are about to modify internal data. Any mistake will damage the objects.
    Do you want to continue? [no] y
       Set UCM_INTEGRATION_ACTIVITY = ""    [cleared]


    Refer to technote 1237620 About ucmutil for further information about the usage of the ucmutil utility referenced above.

  7. Terminate the rebase on the development stream:

    C:\>ucmutil setpvar -pvar UCM_REBASE -none stream:prj1_dev@\PVOB1
    ucmutil: Warning: VOB is replicated; can only repair objects mastered in this replica.
    You are about to modify internal data. Any mistake will damage the objects.
    Do you want to continue? [no] y
       Set UCM_REBASE = ""    [cleared]

  8. Synchronize the stream with the project to update the stream's configuration:

    C:\>cleartool chstream -generate stream:prj1_dev@\PVOB1
    Changed stream "stream:prj1_dev@\PVOB1".


  9. Update the view with the stream's configuration:

    Note: Use the new development view that you were trying to use to cancel the rebase.

    C:\>cleartool setcs -tag prj1_dev_vu2 -stream

  10. If the new development view is a snapshot view, then a cleartool update must be performed to synchronize the view with the stream.

  11. Unset the Integration activity from the old development menu:

    C:\>cleartool setact -view prj1_dev_vu -none
    cleartool: Warning: Activity being unset
    "activity:rebase.prj1_dev.20060607.155107@\PVOB1" has checkouts.

    Cleared current activity from view prj1_dev_vu.


  12. If there were checkouts in the old view, then they need to be canceled for the PVOB and all component VOBs:
    • Describe a component VOB that has checkouts for the old view:

      C:\>cleartool describe -long vob:\multivob
      versioned object base "\multivob"
       created 31-Mar-06.19:33:22 by administrator.None@IBM-8D5F4F33A08
       master replica: original@\multivob
       ...
       VOB holds objects from the following views:
         Ibm-8d5f4f33a08:C:\Rational\Storage\views\prj1_dev_vu.vws [uuid 3d0fb9ba.4c4640df.bc72.81:08:da:87:81:5d] 3d0fb9ba.4c4640df.bc72.81:08:da:87:81:5d
       Attributes:
         FeatureLevel = 4
       Hyperlinks:
         AdminVOB@47@\multivob -> vob:\AdminVOB1


    • Look for the reference to the old view and remove it:

      C:\>cleartool rmview -avobs -uuid 3d0fb9ba.4c4640df.bc72.81:08:da:87:81:5d
      Can't remove view "\\Ibm-8d5f4f33a08\Rational\Storage\views\prj1_dev_vu.vws" from VOB while view still exists.

      Remove view "\\Ibm-8d5f4f33a08\Rational\Storage\views\prj1_dev_vu.vws" references from VOB anyway?  [no] y
      Removed references to view "3d0fb9ba.4c4640df.bc72.81:08:da:87:81:5d" from VOB "\multivob".


      Note: Technote 1122515 discusses removing view references in more detail.

  13. The Integration activity can be removed if it is empty and there are no checked in versions:
    • Removing the Integration activity fails if it is not empty:

      C:\>cleartool rmactivity -force rebase.prj1_dev.20060607.155107@\PVOB1@\PVOB1
      cleartool: Error: Unable to determine VOB for pathname "\PVOB1@\PVOB1".
      cleartool: Error: Unable to remove activity
      rebase.prj1_dev.20060607.155107@\PVOB1@\PVOB1".


      Note: This activity does not need to be removed, as the versions are checked in on the stream, but if you would like to proceed with emptying the change set refer to technote 1134544 for directions (on Windows you can also use technote 1146901).

    • Removing the activity will succeed if it is empty:

      C:\>cleartool rmact -force rebase.prj1_dev.20060607.155107@\PVOB1
      Removed activity "rebase.prj1_dev.20060607.155107@\PVOB1".


  14. The rebase is now canceled:

    C:\>cleartool rebase -status -stream prj1_dev@\PVOB1
    No rebase in progress for stream "prj1_dev".

  15. The rebase can be started from the new development view.

Related information

About non-UCM and UCM views
Unset UCM Activities from a nonexistent view
About interesting versions in a VOB
Japanese technote

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational ClearCase UCM: Rebase

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational ClearCase
UCM: Rebase

Software version:

7.0, 7.0.1, 7.1

Operating system(s):

AIX, HP-UX, IRIX, Linux, Solaris, Windows

Reference #:

1146614

Modified date:

2011-09-13

Translate my page

Machine Translation

Content navigation