My four and half year old told us the other day, "I think Nemo is dead."
"Why?" surprised by his comment, we asked him. "Because the drainage is full of peepee and poopoo. It is so dirty, Nemo can't survive there."
It was not easy for us to think of a reason that Nemo could survive it.
Monday, June 25, 2007
Friday, June 22, 2007
Move a dynamic view locally
Followed the Admin Guide. But there is one step missing in the doc. Here is a full list of steps.
1. Log on to the view host.
Log on as the view owner or privileged user.
2. Deactivate the view.
cleartool chview –readonly fs137_ucm0
3. Stop the view’s server process.
cleartool endview –server fs137_ucm0
4. Remove its tag and then unregister it.
cleartool rmtag –view –all fs137_ucm0
cleartool unregister –view /tmp/fs137_ucm0.vws
5. Copy the view. Log on as root
cd /tmp
cp -p fs137_ucm0.vws /ccstorage/views/fs137_ucm0.vws
6. Register the view at its new location and create a new view tag. Log on as the view owner,
cleartool register –view /ccstorage/views/fs137_ucm0.vws
cleartool mktag –view –tag fs137_ucm0 /ccstorage/views/v5_integration.vws
7. Make the view writable.
cleartool chview -readwrite fs137_ucm0
cleartool lsview -properties -full fs137_ucm0
8. Reactivate and test the view.
access the view and verify the following:
You can check out versions and, in a dynamic view, create view-private files.
All view-private objects were moved.
9. Update VOB references to this view. The view’s old location is still recorded by all VOBs that the view has accessed. To update this information, go to the view check out any element from each VOB that holds such a reference. (You can cancel the checkout immediately if you want).
10. Delete the old view storage directory.
11. Create additional tags as needed.
If the view has tags in other network regions, replace them with tags that reference the new location.
1. Log on to the view host.
Log on as the view owner or privileged user.
2. Deactivate the view.
cleartool chview –readonly fs137_ucm0
3. Stop the view’s server process.
cleartool endview –server fs137_ucm0
4. Remove its tag and then unregister it.
cleartool rmtag –view –all fs137_ucm0
cleartool unregister –view /tmp/fs137_ucm0.vws
5. Copy the view. Log on as root
cd /tmp
cp -p fs137_ucm0.vws /ccstorage/views/fs137_ucm0.vws
6. Register the view at its new location and create a new view tag. Log on as the view owner,
cleartool register –view /ccstorage/views/fs137_ucm0.vws
cleartool mktag –view –tag fs137_ucm0 /ccstorage/views/v5_integration.vws
7. Make the view writable.
cleartool chview -readwrite fs137_ucm0
cleartool lsview -properties -full fs137_ucm0
8. Reactivate and test the view.
access the view and verify the following:
You can check out versions and, in a dynamic view, create view-private files.
All view-private objects were moved.
9. Update VOB references to this view. The view’s old location is still recorded by all VOBs that the view has accessed. To update this information, go to the view check out any element from each VOB that holds such a reference. (You can cancel the checkout immediately if you want).
10. Delete the old view storage directory.
11. Create additional tags as needed.
If the view has tags in other network regions, replace them with tags that reference the new location.
Wednesday, June 20, 2007
Could not Copy Data to View Storage
We have experiencing some strange behavior of ClearCase dynamic view from some developers these few days.
The vob server is on Unix, the view storage is located locally on developers desktop. We use TAS as the interop solution. When some developers tried to check out, the ClearCase explorer reported: "The element is checkout, but could not copy to view storage". We checked everything, and finally narrowed down the behavior to Windows 2000 users. And we found out that when they try start-> run-> "\\10.2.194.153\ccstore", it prompt for id/password logon.
The problem can be solved by a reboot, or explicitly run "net use * \\10.2.194.153\cctore" command. It seems that the networking setting has been changed, the cached data is no longer valid.
The vob server is on Unix, the view storage is located locally on developers desktop. We use TAS as the interop solution. When some developers tried to check out, the ClearCase explorer reported: "The element is checkout, but could not copy to view storage". We checked everything, and finally narrowed down the behavior to Windows 2000 users. And we found out that when they try start-> run-> "\\10.2.194.153\ccstore", it prompt for id/password logon.
The problem can be solved by a reboot, or explicitly run "net use * \\10.2.194.153\cctore" command. It seems that the networking setting has been changed, the cached data is no longer valid.
Subscribe to:
Posts (Atom)