Hi Guys,

While you are running to be prepared to Holidays, let talk about CCRC WAN, this feature on ClearCase 8.x replaces the CM_Server (from CC 7.1.x), the big difference here is WebSphere and IBM HTTP must be installed before you add the feature, in orther words WAS and IBM HTTP is not on ClearCase media anymore.  Actually this post aims to talk about some post-installation commands - on Unix/Linux machines, anyhow let me share a link and one tip regarding the installation:

1) Guidelines regarding to prepare a machine to CCRC WAN are available on:

Installing or Upgrading to ClearCase and ClearQuest V8.0.1 with WebSphere Application Server and IBM HTTP Server V8.5

http://www-01.ibm.com/support/docview.wss?uid=swg21634430

2)  After you have WAS and IBM HTTP installed, and while you are running Installation Manager to install or to add CCRC WAN feature,  you will be asked to
to provide   " CCRC WAN for WebSphere Application  Server home directory",   although the example on Installation Manager window shows

 "/opt/IBM/WebSphere"  if did a default installation of WebSphere,  the WAS Application Server home directory should be instead:

 /opt/IBM/WebSphere/AppServer

Ok, let me provide some commands to use to check your CCRC WAN installation:

NOTE: On my examples below my WAS application was installed on  /opt/IBM/WebSphere/AppServer path:

a) Listing the profiles.

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -listProfiles

[ccrcprofile]  

 

b) Getting the path related to a profile.

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -getPath -profileName  REPLACE-HERE-WITH-PROFILE-NAME

Example:

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -getPath -profileName  ccrcprofile

/opt/ibm/RationalSDLC/common/ccrcprofile

c) Getting details about the profile.

cat  REPLACE-HERE-THE-PATH-TO-THE-PROFILE/logs/AboutThisProfile.txt

cat  /opt/ibm/RationalSDLC/common/ccrcprofile/logs/AboutThisProfile.txt

Application server environment to create: Application server
Location: /opt/ibm/RationalSDLC/common/ccrcprofile
Disk space required: 200 MB
Profile name: ccrcprofile
Make this profile the default: True
Node name: dfltNode
Host name: localhost
Enable administrative security (recommended): False
Administrative console port: 16060
Administrative console secure port: 16043
HTTP transport port: 16080
HTTPS transport port: 16443
Bootstrap port: 16809
SOAP connector port: 16880
Run application server as a service: False
Create a Web server definition: False
Performance tuning setting: Development
 

d) Verifying the CCRC server config file.

cat /opt/rational/clearcase/config/ccrc/server.conf

#Fri, 18 Oct 2013 16:07:47 -0400

ccrcTempDir=/var/tmp/ccrctemp
## ALERT : The default value of ccrcmaxSessionsOverall (was maxServerCount in previous release)
##         has changed. Please check server.conf.sample before uncommenting the following line.
#ccrcMaxSessionsOverall=200
## ALERT : The default value of #ccrcMaxRequestsPerSession has changed.
##         Please check server.conf.sample before uncommenting the following line.
#ccrcMaxRequestsPerSession=10
 

e) Stop/Start IBM HTTP Server and WAS.

Stop Process:

/opt/rational/common/ccrcprofile/bin/stopServer.sh server1  # Which  is  the PATH-TO-PROFILE/bin/stopServer.sh server1

/opt/IBM/HTTPServer/bin/apachectl -k stop

Start Process:

/opt/IBM/HTTPServer/bin/apachectl -k start

/opt/rational/common/ccrcprofile/bin/startServer.sh server1 # Which  is  the PATH-TO-PROFILE/bin/startServer.sh server1

Regards,

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

Hi Everyone,

Lets talk about how to  how to configure ClearCase to run tasks on  timely basis.

NOTE:  On my example I'll do a task each 5 minutes on every day (on a CC 7.1.2.9 Linux Machine).
Do the Time changes to reflect your needs.
 


######### Index ##################

1) Create the task by editing /var/adm/rational/clearcase/scheduler/tasks/task_registry file.

2) Then create the new Job.

3) Monitor the behavior.

########################################

 

1) Create the task by editing /var/adm/rational/clearcase/scheduler/tasks/task_registry file.

1.1) Creates a script file with the desired tasks to be done.

ATTENTION: This script is just an ilustration. DOT NOT use it on production without validade it.

My example will just list the vobs and redirect the output to a file.


vi /var/adm/rational/clearcase/scheduler/tasks/lsvob.sh



#!/bin/bash

cleartool=/usr/atria/bin/cleartool

$cleartool lsvob >> /tmp/$(date +%F:%H:%M:%S)-vobs.txt

echo $(date) >> /tmp/$(date +%F:%H:%M:%S)-vobs.txt
                                                                                                                                                           
#######################################################                                                                   

1.2) Test the script:

[root@XYZ-machine config]# chmod +x /var/adm/rational/clearcase/scheduler/tasks/lsvob.sh

root@XYZ-machine config]# /var/adm/rational/clearcase/scheduler/tasks/lsvob.sh
[root@XYZ-machine config]# ls /tmp/2013*

-rw-r--r-- 1 root root 864 Ago 13 15:58 /tmp/2013-08-1347-vobs.txt

1.3) Add the task on task_registry file.

1.3.1) Make a copy from the original file.

 cp -v  /var/adm/rational/clearcase/scheduler/tasks/task_registry{,.original}
`/var/adm/rational/clearcase/scheduler/tasks/task_registry' -> `/var/adm/rational/clearcase/scheduler/tasks/task_registry.original

1.3.2) Add the task on   /var/adm/rational/clearcase/scheduler/tasks/task_registry file:

Add the lines below on hte end of the file (note 102 is the first available number on my case)

Task.Begin
    Task.Id:       102
    Task.Name:     "My customized Task to list vobs"
    Task.Pathname: lsvob.sh
Task.End


2) Then create the new Job.

Run:
cleartool schedule –edit –schedule

Create a new Job (on my case Job id 19 is the first available number), see my example below:


Job.Begin
    # Job.Id: 19
    Job.Name: "customized Listing vobs each hour"
    Job.Description.Begin:
List each Vob creating a new file list on /tmp
    Job.Description.End:
    Job.Schedule.Daily.Frequency: 1
    Job.Schedule.StartDate: 2013-08-13
    Job.Schedule.FirstStartTime: 00:00:00
    Job.Schedule.StartTimeRestartFrequency: 00:05:00
    Job.Schedule.LastStartTime: 23:59:59
    Job.DeleteWhenCompleted: FALSE
    # Job.Task: 102
    Job.Task: "My customized Task to list vobs"
    Job.Args:
    Job.NotifyInfo.OnEvents: JobEndOKWithMsgs,JobEndFail
    Job.NotifyInfo.Using: email
    Job.NotifyInfo.Recipients: root
    Job.Created: 2013-08-13T15:44:03-04:00 by root@XYZ-machine
    Job.LastModified: 2013-08-13T15:44:03-04:00 by root@XYZ-machine
    Job.NextRunTime: 2013-08-13T16:00:00-04:00
    Job.LastCompletionInfo.ProcessId: 18496
    Job.LastCompletionInfo.Started: 2013-08-13T15:55:00-04:00
    Job.LastCompletionInfo.Ended: 2013-08-13T15:55:00-04:00
    Job.LastCompletionInfo.ExitStatus: 0x0
Job.End


####
Note: Pay special attention on the lines:

    Job.Schedule.Daily.Frequency: 1   # Which means Daily frequency.
 
    Job.Schedule.StartDate: 2013-08-13  # When (date) the Job starts
    Job.Schedule.FirstStartTime: 00:00:00  # When (time of the day) the Job starts
    Job.Schedule.StartTimeRestartFrequency: 00:05:00  # Frequency on each our (here is each 5 minutes).

Once you save the file, if you have NO syntax errors the new Job will be created and is available to run

3) Monitor the behavior:


[root@XYZ-machine log]# tail -n 4 -f /var/adm/rational/clearcase/log/albd_log
2013-08-13T15:44:03-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" Created: 2013-08-13T15:44:03-04:00 by root@XYZ-machine
2013-08-13T15:45:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18277) Started.
2013-08-13T15:45:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18277) Completed: OK.
2013-08-13T15:50:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18417) Started.
2013-08-13T15:50:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18417) Completed: OK.
2013-08-13T15:55:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18496) Started.
2013-08-13T15:55:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18496) Completed: OK.
2013-08-13T16:00:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18569) Started.
2013-08-13T16:00:00-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" (18569) Completed: OK.
2013-08-13T16:02:46-04:00 albd_server(4043): Ok: Job 19 "customized Listing vobs each hour" Properties Modified: 2013-08-13T16:02:46-04:00 by root@XYZ-machine



References:
"The Rational ClearCase scheduler"
http://pic.dhe.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.rational.clearcase.cc_admin.doc%2Ftopics%2Fc_maint_sched.htm

"cleartool schedule man page"
http://pic.dhe.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.rational.clearcase.cc_ref.doc%2Ftopics%2Fct_schedule.htm
 

Best Regards,

 

Pedro Moura

 

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

##### NOTE (2013-04-19) For Ubuntu 10.04 (BEGIN) ###############

One attempt to run SCT on a Ubuntu 10.04 fail (even after the changes above, so I have to change more details:

1) Seems the SCT code is hard coded to work on "eth0" interface, if you haven't eth0, get the interface  and change the script:

Example:

#ifconfig
 


eth2      Link encap:Ethernet  HWaddr 00:50:56:98:5f:13  
          inet addr:192.168.199.254  Bcast:192.168.199.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:410246 errors:9 dropped:11 overruns:0 frame:0
          TX packets:246076 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:528576066 (528.5 MB)  TX bytes:31961525 (31.9 MB)
          Interrupt:18 Base address:0x2000

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:513 errors:0 dropped:0 overruns:0 frame:0
          TX packets:513 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:85348 (85.3 KB)  TX bytes:85348 (85.3 KB)

So my interface name is "eth2". I replace that on the script by running:

sed -i 's/ifconfig eth0/ifconfig eth2/' SCTv5

2) scs script uses /bin/sh replace that to /bin/bash otherwise the function that requires "let" (built in on shell will fail).

First make a copy from "scs" script

cp scs scs.original

Then  edit "scs" file and change de first line from    "#!/bin/sh"  to "#!/bin/bash" or do data using "sed"

sed -i 's/!\/bin\/sh/!\/bin\/bash/' scs

#####   NOTE (2013-04-19) For Ubuntu 10.04 (END) ###############

################################

On client machine:

3.1) Set a view.

cleartool  setview  myview

3.2) Alternate to Vob directory.

cd /vobs/myvob

$ ls -l   abc.txt
-r-xr-xr-x 1 ibmer users  13203 Mar  4 14:50 abc.txt

3.3) Try to read some files.
cat abc.txt                                               
cat: abc.txt: Not a directory                 

 

 

### Update on 2013-06-11 ##########

This is fixed in ClearCase 7.1.2.10 and 8.0.0.6.

Reference: http://www-01.ibm.com/support/docview.wss?uid=swg1PM68068

###################################

If you cannot upgrade CC yet, use the the Workaround below:

 Remount the VobStore using nfs version 3 instead 4.
(use nfsvers=3 option).

        
4.1) For hard mount                                                                         
                                                                                          
Edit  /etc/fstab and use nfsvers=3 on the nfs mount options for                           
instance:                                                                                 
                                                                                          
9.xx.xxx.239:/vobstore  /vobstore  nfs    nfsvers=3,defaults 0 0                          
                                                                                          
                                                                                          
                                                                                          
                                                                                          
4.2) For automount                                                                          
                                                                                          

Edit the default behavior for mount:
For instance  on Red Hat

Edit the Client side by changing /etc/nfsmount.conf
file

Changing from:
# Defaultvers=4

Changing to:
Defaultvers=3                                                            
                                                                                          
test it                                                                                   
                                                                                          
 cd /net/9.xx.xxx.239/vobstore                                                            
                                                                                          
                                                                                          
                                                                                          
]# nfsstat -m                                                  
/net/9.32.252.239/vobstore from 9.32.252.239:/vobstore                                    
 Flags:                                                                                   
rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,                  
proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=9.32.252.239,mountvers=3                  
,mountport=600,mountproto=udp,local_lock=none,addr=9.32.252.239                           
---                                                                                    

 

Hi Everyone,

Tomorrow will be Friday, and let me share this tips to close this Week.

When having Vobs or View Stores on NAS, while the Vobs/views Server are Linux/Unix machine what could be the the correct permissions to have on the stores?

Answer:

The permissons for Vob and View Storages on NAS, must allow read/write/excute (that will allow the directory browsing) for  the          
Vobs/views account and group owners, and  if you are squashing remote root access (making it as nobody) you must  have  read  and execute permission to others also.

Otherwise you (if you  are NOT squashing remote root) you can have just 770 on Vob/View Stores. (see    

See my example below.     

######### Index ################################

 I - In case remote root access  is being squashed.   

II - If I have  root NOT squashed             

##############################################    

                                                                                  
I - In case remote root access  is being squashed.                                  
                                                                                    
machinexyz is a Vob Server.                                                         
                                                                                    
filerA is a NAS.                                                                    
                                                                                    
1) If others has no access                                                          
                                                                                    
[pmoura@machinexyz pmoura]$ ls -ld /net/filerA/vol1/vobs/                           
                                                                                    
drwxrwx--- 3 pmoura ccusers 4096 May 28 11:13 /net/filerA/vol1/vobs/                
                                                                                    
                                                                                    
$ cleartool mkvob -tag /vobs/vobremote1 -public  -host machinexyz -hpath  /net/filerA/vol1/vobs/vobremote1.vbs  -gpath                                        
/net/filerA/vol1/vobs/vobremote1.vbs  /net/filerA/vol1/vobs/vobremote1.vbs      

#(Note: The two lines above represent just one command  line).

                                          
cleartool: Warning: Storage pathname "/net/filerA/vol1/vobs" may not                
reside on host "machinexyz".                                                        
Registry password:                                                                  
Comments for "/net/filerA/vol1/vobs/vobremote1.vbs":                                
.                                                                                   
cleartool: Error: Failed to record hostname "machinexyz" in storage                 
directory "/net/filerA/vol1/vobs/vobremote1.vbs". Check that root or the            
ClearCase administrators group has permission to write to this                      
directory.                                                                          
cleartool: Error: Problem starting vob_server for vob                               
machinexyz:/net/filerA/vol1/vobs/vobremote1.vbs                                     
cleartool: Error: See albd or vob error logs on host machinexyz                     
cleartool: Error: Unable to create versioned object base                            
"/net/filerA/vol1/vobs/vobremote1.vbs".                                             
                                                                                    
                                                                                    
2) Seting 5 permissions to others will work fine on creating the vobs.              
                                                                                    
[pmoura@machinexyz pmoura]$ chmod 775 vobs/                                         
[pmoura@machinexyz pmoura]$ ls -ld /net/filerA/vol1/vobs/     

                      
drwxrwxr-x 3 pmoura ccusers 4096 May 28 11:13 /net/filerA/vol1/vobs/                
                                                                                    
                                                                                    
cleartool mkvob -tag /vobs/vobremote1 -public  -host machinexyz -hpath  /net/filerA/vol1/vobs/vobremote1.vbs  -gpath                                        
/net/filerA/vol1/vobs/vobremote1.vbs  /net/filerA/vol1/vobs/vobremote1.vbs  

#(Note: The two lines above represent just one command  line).

                                             
cleartool: Warning: Storage pathname "/net/filerA/vol1/vobs" may not                
reside on host "machinexyz".                                                        
Registry password:                                                                  
Comments for "/net/filerA/vol1/vobs/vobremote1.vbs":                                
.                                                                                   
Created versioned object base.                                                      
Host-local path: machinexyz:/net/filerA/vol1/vobs/vobremote1.vbs                    
Global path:     /net/filerA/vol1/vobs/vobremote1.vbs                               
VOB ownership:                                                                      
  owner pmoura                                                                      
  group ccusers                                                                     
Additional groups:                                                                  
  group abc                                                                         
                                                                                    
VOBs have special data backup considerations.  For more information on              
how to                                                                              
back up your VOB properly, see the documentation for administering                  
ClearCase.                                                                          
If the backups aren't done properly, you are putting your data at risk!             
                                                                                    
                                                                                    
II - If I have  root NOT squashed                                                   
                                                                                    
machinexyz - vob Server.                                                            
                                                                                    
filerB - NAS device.                                                                
                                                                                    
1) Share details                                                                    
                                                                                    
From a client:                                                                      
                                                                                    
ls -ld /net/filerB/test     

                                                        
drwxrwx--- 3 pmoura ccusers 4096 Nov  8  2012 /net/filerB/test         

From the NAS:                                                                       
                                                                                    
cat /etc/exports                                                                   
/test *(rw,no_root_squash)                                                          
                                                                                    
NOTE: On Netapp "anon=0" is the equivalent of "no_root_squash" to be                
used on /etc/exports file to at least the Vob Server.                                                       
                                                                                    
                                                                           
                                                                                    
2) Attempt to create a vob worked fine.                                             
                                                                                    
cleartool mkvob -tag /vobs/vob-root-no-squash  -public  -host machinexyz  -hpath /net/filerB/test/vob-root-no-squash.vbs -gpath                               
/net/filerB/test/vob-root-no-squash.vbs   /net/filerB/test/vob-root-no-squash.vbs    

#(Note: The two lines above represent just one command  line).

                    
cleartool: Warning: Storage pathname "/net/filerB/test" may not reside              
on host "machinexyz".                                                               
Registry password:                                                                  
Comments for "/net/filerB/test/vob-root-no-squash.vbs":                             
.                                                                                   
Created versioned object base.                                                      
Host-local path: machinexyz:/net/filerB/test/vob-root-no-squash.vbs                 
Global path:     /net/filerB/test/vob-root-no-squash.vbs                            
VOB ownership:                                                                      
  owner pmoura                                                                      
  group ccusers                                                                     
Additional groups:                                                                  
  group abc                                                                         
                                                                                    
VOBs have special data backup considerations.  For more information on              
how to                                                                              
back up your VOB properly, see the documentation for administering                  
ClearCase.                                                                          
If the backups aren't done properly, you are putting your data at risk!             
                                                                                    
                                                                                    
3) NOTE: If I unset the "no_root_squash" option on the Share                        
/net/filerB/test/ , while its permission is 770, I cannot create the Vob            
(same that I saw on item I above).                                                  
                                                                                    
cleartool mkvob -tag /vobs/vob-root-SQUASHED   -public  -host machinexyz              
-hpath /net/filerB/test/vob-root-SQUASHED.vbs -gpath  /net/filerB/test/vob-root-SQUASHED.vbs  /net/filerB/test/vob-root-SQUASHED.vbs   

#(Note: The two lines above represent just one command  line).

                                          
cleartool: Warning: Storage pathname "/net/filerB/test" may not reside              
on host "machinexyz".                                                               
Registry password:                                                                  
Comments for "/net/filerB/test/vob-root-SQUASHED.vbs":                              
.                                                                                   
cleartool: Error: Failed to record hostname "machinexyz" in storage                 
directory "/net/filerB/test/vob-root-SQUASHED.vbs". Check that root or              
the ClearCase administrators group has permission to write to this                  
directory.                                                                          
cleartool: Error: Problem starting vob_server for vob                               
machinexyz:/net/filerB/test/vob-root-SQUASHED.vbs                                   
cleartool: Error: See albd or vob error logs on host machinexyz                     
cleartool: Error: Unable to create versioned object base                            
"/net/filerB/test/vob-root-SQUASHED.vbs".                                           
                                                                                 

 

See also: http://www-01.ibm.com/support/docview.wss?uid=swg21461976

 

I hope you have a Great Friday and Weekend!!!!

 

### Update on 2013-06-10 Regarding additional groups ###########

If you have NO permissions to others on VobStores, any additional groups  of a Vob will NOT able to work properly on the vob, see the example below:

a) If I limit the access to others:

[root@RHEL5U764B ~]# chmod 750 /vobstore/vobmaria.vbs

Then inside the vob I have failure.

[pmoura@RHEL5U764B dirabc]$ cleartool mkelem test3.txt
Creation comments for "test3.txt":
.
text_file_delta: Error: Unable to open file "/vobstore/vobmaria.vbs/s/sdft/16/40/tmp_20437.1": Permission denied
cleartool: Error: Type manager "text_file_delta" failed create_element operation.
cleartool: Error: Unable to create element "test3.txt".
[pmoura@RHEL5U764B dirabc]$ ls -ld .
drwxrwx--- 2 maria abc 136 Jun  7 12:32 .

b) If I allow the others to read and access the VobStore, members of Additional group will be able to work properly inside the vob.


[root@RHEL5U764B ~]# chmod 755 /vobstore/vobmaria.vbs


[pmoura@RHEL5U764B dirabc]$ ls -ld .
drwxrwx--- 2 maria abc 136 Jun  7 12:32 .
[pmoura@RHEL5U764B dirabc]$ cleartool mkelem test3.txt
Creation comments for "test3.txt":
.
Created element "test3.txt" (type "text_file").
Checked out "test3.txt" from version "/main/0".
[pmoura@RHEL5U764B dirabc]$ echo 111 > test3.txt
[pmoura@RHEL5U764B dirabc]$ cleartool ci test3.txt
Checkin comments for "test3.txt":
.
Checked in "test3.txt" version "/main/1".
[pmoura@RHEL5U764B dirabc]$ cleartool ci -nc .
Checked in "." version "/main/3".
[pmoura@RHEL5U764B dirabc]$

 

 

############################################################

Regards,

 

Pedro Moura

 

 

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

Hi,

If you just upgraded a Red Hat to version 6.3 (or if you are using old RHN medias/repositories) and ClearCase is not getting started, failing with errors like that:

arc automount[<PID NUMBER>]: rpc_get_exports_proto           
arc kernel: automount[<PID NUMBER>]: segfault at 28 ip  ....  ....  0 error 4 in lookup_hosts.so[....]                  

Seems you are running on the autofs bug, so verify if you have "autofs-5.0.5-54.el6.x86_64" or lower, by running:
                                                                                                                                 
rpm -q autofs

If so, raise the package to  "autofs-5.0.5-55.el6_3 "  or higher by running (as root):

yum install autofs

                                                         
                                                                                      
Then restart ClearCase.

Note: If the problem was on CC installation/Upgrade process and the task was not completed you shoud reinstall/upgrade CC again.
 

Reference: https://access.redhat.com/site/solutions/155523

                 

Note: This problem could be also related to install hanging with "Starting ClearCase services" on Red Hat.

                                                                                      
Regards,                                                                           

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################

Hi Everyone,

Let me share this uncommon situation and how to deal with it.

1) What is the problem?

 Attempt to Full uninstall ClearCase by using response files provided by http://www-01.ibm.com/support/docview.wss?uid=swg21376355

failed to remove the related directories.

2) How to verify the problem?

For instance:

/var/ibm/InstallationManager/uninstall/uninstallc -input /tmp/clearcase_uninstall_response_linux_x86.xml                                                                                         
                                                                                            
After that if you verify if ClearCase it was uninstalled you can't see the features anymore, however ClearCase mention still there:

Running:                                                                                           
/opt/IBM/InstallationManager/eclipse/tools/imcl listInstalledPackages                       
-features -long                  

It returns:

                                                         
/opt/IBM/InstallationManager/eclipse :                                                      
com.ibm.cic.agent_1.7.1000.20131119_2219 : IBM® Installation Manager :                     
1.7.1 :                                                                                     
/opt/ibm/RationalSDLC :                                                                     
com.ibm.rational.clearcase.linux_x86_8.0.1003.0000-8-0-1-03-00-2014A-D1                     
40304                                                                                       
: IBM® Rational® ClearCase® - Linux x86 : 8.0.1.03 :                        

 If you use find command (regular OS command) you see the ClearCase related  files were deleted (-type f), but the directories (-type d) still there.

                                                       
                                                                                            
find /opt/ibm/RationalSDLC -type d | wc -l                                                 
    43                                                                              
find /opt/ibm/RationalSDLC -type f | wc   -l                                              
    0                                                                              

3) What is the cause of the problem?

Based on some tests seems missing "com.ibm.rational.clearcase.check.unix.libraries.feature" on the response file is the current cause.                                                                                           
4) How to fix the problem?

Option 1:                                                                     

To determine the features installed on the system,  instead to use the command below - as suggested on the response files examples from http://www-01.ibm.com/support/docview.wss?uid=swg21376355

    #grep -i feature /var/ibm/InstallationManager/installed.xml | grep clearcaseunix


should be better if we run:

 grep -i feature /var/ibm/InstallationManager/installed.xml |grep com.ibm.rational

which will provide all features and also com.ibm.rational.clearcase.check.unix.libraries.feature that missed on the response file.

      <package kind='feature' id='com.ibm.rational.check.link.feature'>
      <package kind='feature' id='com.ibm.rational.clearcase.check.unix.libraries.feature'>
      <package kind='feature' id='com.ibm.rational.clearcase.ctexplorer'>
      <package kind='feature' id='com.ibm.rational.clearcase.was.removal.warning.feature'>
      <package kind='feature' id='com.ibm.rational.clearcaseunix.CC_FULL'>
      <package kind='feature' id='com.ibm.rational.clearcaseunix.CC_MIN_STD_X'>
      <package kind='feature' id='com.ibm.rational.clearcaseunix.CM_Server'>
      <package kind='feature' id='com.ibm.rational.clearcaseunix.core'>
      <package kind='feature' id='com.ibm.rational.is.supported.unix.cc.feature'>
      <package kind='feature' id='com.ibm.rational.team.check.v7.feature'>

 

Using the information above you can edit the uninstall response file to:

<agent-input>                                                                   
    <uninstall modify='false'>                                                  
        <offering                                                               
            profile='IBM Rational SDLC'                                         
            id='com.ibm.rational.clearcase.linux_x86'                           
version='8.0.1003.0000-8-0-1-03-00-2014A-D140304'                               
            features='com.ibm.rational.team.check.v7.feature,                   
            com.ibm.rational.clearcase.check.unix.libraries.feature,            
            com.ibm.rational.is.supported.unix.cc.feature,                      
            com.ibm.rational.check.link.feature,                                
            com.ibm.rational.clearcase.was.removal.warning.feature,             
            com.ibm.rational.clearcaseunix.core,                                
            com.ibm.rational.clearcase.ctexplorer,                              
            com.ibm.rational.clearcase.cteupdatesite,                           
            com.ibm.rational.cc.cadence.virtuoso.integration,                   
            com.ibm.rational.clearcaseunix.CC_FULL,                             
            com.ibm.rational.clearcaseunix.CC_MIN_STD_X,                        
            com.ibm.rational.clearcaseunix.CC_ONLY_SERVER_X,                    
            com.ibm.rational.clearcaseunix.CC_MFC,                              
            com.ibm.rational.clearcaseunix.MS_FULL,                             
            com.ibm.rational.clearcaseunix.MS_ONLY_SHIPPING_SERVER,             
            com.ibm.rational.clearcaseunix.CQ_CC_int,                           
            com.ibm.rational.clearcaseunix.CM_Server' />                        
    </uninstall>                                                                
</agent-input>  

 

Option 2:

                                                                                   
We could use "imcl uninstall" command pointing to the CC version ID installed.                               
                                                                                     
/opt/IBM/InstallationManager/eclipse/tools/imcl  uninstall  <Version ID>             
                                                                                     
For instance:                                                                        
                                                                                     
                                                                                     
/opt/IBM/InstallationManager/eclipse/tools/imcl  uninstall                           
com.ibm.rational.clearcase.linux_x86_8.0.1003.0000-8-0-1-03-00-2014A-D1                     
40304 
             

Best Regards,

 

Pedro Moura                                                                         

##########################################Disclaimer ###################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
######################################################################################

Hello!

How are you doing? New week, new post!

Let me share this situation:

Attempts to build mvfs - while installing ClearCase, or on a mvfs manually build attempt - fails with:

/var/adm/rational/clearcase/mvfs/mvfs_src/mvfs_vfsops.c:1: error: code
model kernel not supported in the 32 bit mode          

              
/var/adm/rational/clearcase/mvfs/mvfs_src/mvfs_vfsops.c:1: sorry,      
unimplemented: 64-bit mode not compiled in                             
make[2]: *** [/var/adm/rational/clearcase/mvfs/mvfs_src/    

Probably the root cause of this problem  the default C compiler is for 32 Bit, instead for 64 Bit.

To solve this problem do the following:

1) Verify if you have gcc for 64 Bit installed:

2) Double check which gcc version is using by default:

For instance, for a 64 Bit kernel you should have something like that:

$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC)

In other hand, if the line Target is NOT showing a 64 Bit version (x86_64-redhat-linux)  we know gcc is wrongly configured here:

I wrong configuration could be:
                                                                   
"Target: i686-pc-linux-gnu"

If that is your case run

whereis gcc; type gcc

To see what is the path of gcc used by default.

Then using "rpm -ql gcc |grep gcc$"  looking for the path to your correct gcc (for each one run <path-to-gcc> -v).                                         

3) To fix the issue you have two solutions:

3.1) Change your OS configuration to use the correct  gcc.

OR

3.2) Edit the mvfs_param.mk.config pointing to the path to the correct  gcc for 64Bit.

On my example the correct gcc is on /usr/bin/gcc

To do that follow the steps below:

3.2.1) Change to the mvfs source directory:

cd /var/adm/rational/clearcase/mvfs/mvfs_src/

3.2.2) Create mvfs_param.mk.config file

A easy way to do that is to run:

"make clean; make"

Then we have  mvfs_param.mk.config file created.

3.2.3) Then edit  mvfs_param.mk.config file adding the "CC=/usr/bin/gcc" (replace with the path to your gcc for 64Bit).

                                                                           
So on my case I'll have this:                                                     
                                                                                  
                                                                                  
RATL_EXTRAFLAGS := -DRATL_REDHAT -DRATL_VENDOR_VER=500                            
-DRATL_EXTRA_VER=0 -DRATL_COMPAT32                                                
LINUX_KERNEL_DIR=/lib/modules/2.6.18-274.12.1.el5/build                           
CONFIG_MVFS=m                                                                     
CC=/usr/bin/gcc                                                                   
                             
Then, if the only problem was the wrong C compiler you will be able to run "make; make install"  and have mvfs installed.       

Have a Great Week!

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################

                                       

Hi Everyone.

Once you have ClearCase started (on environments where you installed mvfs) we expected to have a file called ".specdev" inside "/view" directory, and if that is NOT true as stated on TN 1135104 (http://www-01.ibm.com/support/docview.wss?rs=984&uid=swg21135104) you should reinstall Clearcase.

Here you have one alternative to Recreate that file without reinstalling CC on Linux machines:

Note: You must to it as root.

 1) Change to /view directory:

cd /view

2) Recreate the special file and set the apropriate permissions/ownership.

mknod .specdev c 0 0x000000


chmod 444 .specdev


chown root:root .specdev

3) Verify the expected symbolic links.

Check if  /var/adm/rational/clearcase/cache/clearcase_specdev is          

pointing to the file above                                                      

                                                                             

ls -l /var/adm/rational/clearcase/cache/clearcase_specdev                       

                                                                                

We expected to have:                                                            

                                                                                

ls -l /var/adm/rational/clearcase/cache/clearcase_specdev                       

                                     

/var/adm/rational/clearcase/cache/clearcase_specdev -> /view/.specdev           


If that is NOT true recreate the link by running:

 

ln -s /view/.specdev /var/adm/rational/clearcase/cache/clearcase_specdev 

Regards,

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################

Hi  Everyone,

Let me share these steps regarding  how to recover  a missing  pool_id file from source container in a Vob.

### NOTE ###################
On the example below we have:
Vob tag:   /vobs/john-vob3
Vob Storage Path:  /vobstore/john-vob3.vbs
##########################################

#### Index ########

I - Symthom
II - Verify if you have remote pools.
III - Recreating the file.

##############


I - Symthom

By running a "cleatool protectvob", for instance, you get a message telling s/sdft/pool_id is missing:



cleartool protectvob -chown john -chgrp abc /vobstore/john-vob3.vbs

This command affects the protection on your versioned object base.
While this command is running, access to the VOB will be limited.
If you have remote pools, you will have to run this command remotely.
cleartool: Warning: Versioned object base owner is already "john".
cleartool: Warning: Versioned object base group is already "abc".
Pool "sdft" appears to be protected correctly.
Pool "ddft" appears to be protected correctly.
Pool "cdft" appears to be protected correctly.
Protect versioned object base "/vobstore/john-vob3.vbs"?  [no] yes
Do you wish to protect the pools that appear not to need protection?  [no] yes
Protecting "/vobstore/john-vob3.vbs/db/logs"...
Protecting "/vobstore/john-vob3.vbs/db"...
Protecting "/vobstore/john-vob3.vbs/admin/vob_space"...
Protecting "/vobstore/john-vob3.vbs/admin/do_space"...
Protecting "/vobstore/john-vob3.vbs/admin"...
Protecting "/vobstore/john-vob3.vbs/s/sdft/42/3b"...
Protecting "/vobstore/john-vob3.vbs/s/sdft/42"...
Protecting "/vobstore/john-vob3.vbs/s/sdft"...
cleartool: Error: unable to access file /vobstore/john-vob3.vbs/s/sdft/pool_id: No such         
file or directory                                                               
cleartool: Error: Trouble protecting versioned object base "/vobs/john-vob3".           
          
II - Verify if you have remote pools.

1) You must be sure you are not running on  NOT accessible remote pools, so look for symbolic links on the Related Vob Store:

cd <vob-store>

find . -type l -exec ls -l {} \;

1.1) If you have empty results that means you have NO remote pools, so you can go ahead to item III below.

cd /vobstore/john-vob3.vbs/
find . -type l -exec ls -l {} \;

Note: On my example I have empty results.

1.2) In other hand if you have symbolic links, that means you have remote pools.

For instance:
                                                              
cd /vobstg/libpub.vbs                                         
find . -type l -exec ls -l {} \;                            

 
   lrwxrwxrwx   1 root           12 Dec 30  1999              
   d/ddft_2 ->/net/vobsvr5/pools/libpub/d/ddft_2             

On this case DON'T go to item III. Instead stop here and verify what is going wrong with the Network Share that provides the remote pools.


III - Recreating the file.                                                                      

NOTE: Is NOT necessary to lock the vob to restore that file (on source container).

If you are sure you have NO remote pools (see item 1.1 above), in order to restore the pool_id inside the source container you should do:

1.1) Get the details necessary on pool_id file, i.e:


poolkind=s  # We already know is the "s".

pool_oid=   # We will get i by running "cleartool dump pool:sdft inside a view context and inside the Vob.

replica_uuid=  # We will get it from the replica_uuid file in the vbs.

vob_oid=  # We will get it  from the vob_oid file in the vbs.


1.1.1) Geeting pool_oid

 cleartool setview john-dyn-view

Note: If the vob is NOT mounted, mount it.

 cd /vobs/john-vob3
 cleartool dump pool:sdft |grep oid

oid=3ee0f993.dcd511e2.9399.00:50:56:98:72:93  dbid=33 (0x21)

So the pool_oid is 3ee0f993.dcd511e2.9399.00:50:56:98:72:93

1.1.2) Getting replica_uuid.

 cd /vobstore/john-vob3.vbs
 cat replica_uuid

3eb0f90f.dcd511e2.9399.00:50:56:98:72:93

1.1.3) Getting vob_oid

cd /vobstore/john-vob3.vbs # Probably you stil there after after 1.1.2 item above.

cat vob_oid

3eb0f90b.dcd511e2.9399.00:50:56:98:72:93

1.2) Creating the pool_id file


As Vob owner:

cd /vobstore/john-vob3.vbs # Probably you stil there after after 1.1.3 item above.

Create a file on the path pool_id file inside "s/sdft/" its contents must be:

poolkind=s pool_oid=<pool_oid from item 1.1.1> replica_uuid=<replica_uuid from item 1.1.2> vob_oid=<vob_oid from item 1.1.3>

For instance:
poolkind=s pool_oid=3ee0f993.dcd511e2.9399.00:50:56:98:72:93 replica_uuid=3eb0f90f.dcd511e2.9399.00:50:56:98:72:93 vob_oid=3eb0f90b.dcd511e2.9399.00:50:56:98:72:93

Set the permission 444 to the file

chmod 444 s/sdft/pool_id

2) Finally verify the Vob healthy by running "cleartool checkvob"

 cleartool  checkvob  -pool -source    /vobstore/john-vob3.vbs
...
The VOB's source pools are healthy.

Regards,

 

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################

 

Hi Everyone,

It's Friday!!!!

Let me share this step-by-step about:

How can you configure an IBM Rational ClearCase Linux machine to use the accounts from an Microsoft Active Directory (AD) without the use of Winbind?

Well, the better approach would be to extend the AD schema to POSIX and then make CC Linux machine as LDAP client.

If you are NOT able to have the above, and since CC does NOT supports Winbind ( Refer to technote 1399614 Winbind support with ClearCase),

the steps below can help you.

#### Concepts Related:

* We will joine the CC - Linux machine to the Domain.

** We will create the accounts/groups locally on the CC - Linux machine (with the same name that they have on AD), but we will NOT set any passwords on Linux side, thus the authentication will remain on AD.

###################

Note1:  If you have other ClearCase Linux machines, use these steps, however, you must  create the accounts and groups on both sides with the same uid and gid respectively.

Note2:  Do not set the passwords on the Linux machines. The password set will be kept only on the AD Server.  

The information below provides an example (on Red Hat 5.5) on how to perform the necessary steps.  You should modify the steps as needed to fit your specific environment.

 

### Index ####

I - Environment  

II - Steps  

#############
                                                               

I - Environment                                                                   
                                                                                  
Domain Controller   

9.X.X.202    

Domain Name: ccbr   

hostname RCSBR         

OS:    

Windows Server 2008 R2 DataCenter Build 7601 64 bit   


Linux VOB Server  

9.X.X.196  RCSRHEL5     

RHEL 5.5    


Packages installed   

rpm -qa |egrep "samba|krb"  

samba3x-winbind-3.5.4-0.83.el5_7.2
krb5-auth-dialog-0.7-1  
samba3x-domainjoin-gui-3.5.4-0.83.el5_7.2
krb5-workstation-1.6.1-36.el5_4.1
samba3x-3.5.4-0.83.el5_7.2
krb5-libs-1.6.1-36.el5_4.1
pam_krb5-2.2.14-15
samba3x-common-3.5.4-0.83.el5_7.2
samba3x-swat-3.5.4-0.83.el5_7.2   
krb5-devel-1.6.1-36.el5_4.1
samba3x-client-3.5.4-0.83.el5_7.2

Note: Winbind is installed but not running.   

II - Steps   

1) Edit the Kerberos config file                 

### "krb5.conf  

[logging]
 default = FILE:/var/log/krb5libs.log    
 kdc = FILE:/var/log/krb5kdc.log      
 admin_server = FILE:/var/log/kadmind.log

[libdefaults]  
 default_realm = CCBR.COM.BR  
 dns_lookup_realm = false  
 dns_lookup_kdc = false
 ticket_lifetime = 24h
 forwardable = yes

[realms]
 CCBR.COM.BR = {   
  kdc = RCSBR.CCBR.COM.BR:88
  admin_server = RCSBR.CCBR.COM.BR:749
  default_domain = CCBR.COM.BR
 }

[domain_realm]
 .CCBR.COM.BR = CCBR.COM.BR
 CCBR.COM.BR = CCBR.COM.BR
 

[appdefaults]
 pam = {   
   debug = false
   ticket_lifetime = 36000
   renew_lifetime = 36000
   forwardable = true  
   krb4_convert = false
 }

############## end "krb5.conf
                                                                                  

2) Edit the Samba file                                                            
                                                                                  
                                                                                  
#### smb.conf     
                                                                                  
workgroup = CCBR     
server string = Samba Server Version %v   
                                                                                  
netbios name = rcsrhel5                                                   
security = ADS                                                                    
#security = domain                                                                
                                                                                  
                                                                                  
realm = CCBR.COM.BR                                                       
password server = RCSBR.CCBR.COM.BR   

 

### If you use Samba to share Vob and View Storages you must have the shares configured also, see
# http://www-01.ibm.com/support/docview.wss?uid=swg27011199
########### end smb.conf                                                          
                                       

                                           
then restart samba  

2) Join to the Domain                                                             
                                                                                  
########                                                                          
                                                                                  
Note: Administrator is an account on AD.                                           

2.1) Run kinit with AD administratior credentials:

                                                                                
kinit Administrator  
Password for Administrator@CCBR.COM.BR:

[root@RCSRHEL5 ]# klist

Ticket cache: FILE:/tmp/krb5cc_0  
Default principal: Administrator@CCBR.COM.BR

Valid starting     Expires            Service principal
01/25/12 15:54:36  01/26/12 01:56:15  krbtgt/CCBR.COM.BR@CCBR.COM.BR
 renew until 01/26/12 15:54:36

Kerberos 4 ticket cache: /tmp/tkt0
klist: You have no tickets cached    si
                                                                                  
                                                                                  
####                                                                              

2.2) Then run "net ads join"

                                                                                
[root@RCSRHEL5 ]# net ads join -U Administrator%user-password -S RCSBR.CCBR.COM.BR

Using short domain name -- CCBR  
Joined 'RCSRHEL5' to realm 'ccbr.com.br'
DNS update failed!

###                                                                               
                                                                                  

3) Then update the Authentication method which will make changes on PAM.

authconfig --update --enablepamaccess --enablelocauthorize --enablekrb5 --enablemkhomedir
 

4)  Create the UNIX accounts   and Groups.                                            
                                                                                  
On AD there is a  john account, however, since there is no Winbind to translate it, this account must be created on Linux as well.                                                                                    

useradd -md /home/john john

   

Some notes regarding Groups:

In case the Primary Group for this user must be  ccgroup, instead "john":

                                                                                         
4.1) Option 1> Create the new account with ccgroup as Primary Group.     

Create ccgroup:

# groupadd ccgroup     

Create the account:             
                                                                                         
# useradd -g ccgroup john    

# getent passwd |grep john                   
john:x:503:4590::/home/john:/bin/bash                 
# id -a john        
uid=503(john) gid=4590(ccgroup) grupos=4590(ccgroup)
                                                                                         
4.2) Option 2> Create the new account and then add this account as a member of ccgroup
  

Create ccgroup:

# groupadd ccgroup    

Create the account:     

# useradd john

# getent passwd |grep john                   
john:x:503:4590::/home/john:/bin/bash                 
 

Add john as mebmer of ccgroup:

# usermod -G ccgroup paul       

# id -a john      


uid=503(john) gid=503(john) grupos=503(john),4590(ccgroup)
                                                                                         

###

NOTE: If the account has other groups (on AD) that will be used on ClearCase work, create them on Linux side that add the related account as member of them.

#####                                                                              

5) Test the authentication                                                        
                                                                                  
5.1) Using smbclient  
                                                                               
smbclient -L 9.X.X.196 -U john%user-password  
                                                                                  
Domain=[CCBR] OS=[Unix] Server=[Samba 3.5.4-0.83.el5_7.2]

 Sharename       Type      Comment   
 ---------       ----      -------   
 IPC$            IPC       IPC Service (Samba Server Version 3.5.4-0.83.el5_7.2)
 john            Disk      Home Directories
Domain=[CCBR] OS=[Unix] Server=[Samba 3.5.4-0.83.el5_7.2]


 Server               Comment
 ---------            -------

 Workgroup            Master  
 ---------            -------

###                                                                               
Note the account password is brought over from AD  
                            
[root@localhost samba]# grep john /etc/passwd

john:x:503:503::/home/john:/bin/bash

                                                               
                                                                                  
5.2) Testing opening an  ssh session                                               
                                                                                                                                                                 
ssh john@9.X.X.196

john@9.X.X.196's password:

-bash-3.2$                                                                        
                                                                                  

5.3) As a double check a new account on Windows called paul has been created (but you do not have to create the UNIX account, this is just to see the results).    
                                                                                  
Then you have:                                                                       
ssh paul@9.X.X.196

paul@9.X.X.196's password:       
Permission denied, please try again.         
paul@9.X.X.196's password:
                                                                                  
Next you create the UNIX account 

                                                  
 useradd -md /home/paul paul    

When you try to open the ssh session again, you will have success.                    
                                                                                  
                                                                                  
ssh paul@9.X.X.196
paul@9.X.X.196's password:    
[paul@RCSRHEL5 ~]$

####

 

As next step Use a Windows CC client and try the access to the Vobs (having them syncronized to Windows Region as expected).

Have a Great Weekend!!!!!

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

Let work today on a simple example on backup/Restore process from a Vob on a Unix/Linux Environment.
I - Backup

1) Preparing to backup

   Be sure your vob is umounted and unlocked.

   # cleartool umount /vobs/2013-01

   # cleartool lock vob:/vobs/2013-01
Locked versioned object base "/vobs/2013-01".

2) Doing the backup

2.1) Let's create a list from with  the existing files.

  find /vobstore/2013-01.vbs/ > /tmp/list-from-production

2.2) Create a list of files and permissions at <vbs>/.identity/

ls -lhta /vobstore/2013-01.vbs/.identity/
total 8.0K
drwxr-xr-x 8 pmoura pmoura 4.0K Mar 10 00:30 ..
drwx------ 2 pmoura pmoura 4.0K Jan 21 13:56 .
-r----s--- 1 pmoura pmoura    0 Jan 21 13:56 gid
-r-S------ 1 pmoura pmoura    0 Jan 21 13:56 uid


2.3) Then let create the backup.

tar czvf /tmp/2013-01.vob.tar.gz /vobstore/2013-01.vbs

3) Testing if I'm able to restore the backup to an alternative place:

mkdir /tmp/testing-backup

tar xzf /tmp/2013-01.vob.tar.gz -C /tmp/testing-backup

Create a list witht the files

find /tmp/testing-backup/ > /tmp/listfrombackup

Since my alternative place have two more levels the the original vob store, i.e:

/tmp/testing-backup/vobstore/2013-01.vbs/

instead

/vobstore/2013-01.vbs/

I will create a new file list (from backup) without /tmp/testing-backup/ and the 2 first lines (that will show /tmp and testing),
just to facilitate the comparison:


sed -e 's/\/tmp\/testing-backup//' -e 1,2d  /tmp/listfrombackup > /tmp/listfrombackup-same-path

Then I ran:

 diff /tmp/list-from-production /tmp/listfrombackup-same-path  
1c1
< /vobstore/2013-01.vbs/
---
> /vobstore/2013-01.vbs

We can disregard the so few differences above and and assume the all files were restore, so our backup seems to be good.

After I have realized my backup is good, I should make a copy from the backup file to other machine (for security purpose), and then I delete  the original vbs:

rm -rf  /vobstore/2013-01.vbs
 

Note: If I tried to mount the vob now I'll have failure:

# cleartool mount /vobs/2013-01
cleartool: Error: The VOB storage directory "/vobstore/2013-01.vbs" was not found.


II - Restoring process

1) Restoring the vbs using the backup file.

1.1)
# tar xzf /tmp/2013-01.vob.tar.gz -C /

Double check if the permissions on <vbs>/.identity still the same (collected from I - 2.2 above):

ls -lhta /vobstore/2013-01.vbs/.identity/
total 8.0K
drwxr-xr-x 8 pmoura pmoura 4.0K Mar 10 00:30 ..
drwx------ 2 pmoura pmoura 4.0K Jan 21 13:56 .
-r----s--- 1 pmoura pmoura    0 Jan 21 13:56 gid
-r-S------ 1 pmoura pmoura    0 Jan 21 13:56 uid

2) Describing the vob, and not it still locked:

# cleartool desc vob:/vobs/2013-01
versioned object base "/vobs/2013-01" (locked)
  created 2013-01-21T13:56:08-05:00 by pmoura.pmoura@abcMachine
  VOB family feature level: 5
  VOB storage host:pathname "abcMachine:/vobstore/2013-01.vbs"
  VOB storage global pathname "/vobstore/2013-01.vbs"
  database schema version: 54
  modification by remote privileged user: allowed
  atomic checkin: disabled
  VOB ownership:
    owner pmoura
    group pmoura
  Attributes:
    FeatureLevel = 5

3) Unlocking the vob

# cleartool unlock vob:/vobs/2013-01
Unlocked versioned object base "/vobs/2013-01".

4) Testing the vob

# cleartool mount /vobs/2013-01

# su - pmoura
$ cleartool pmoura_view
$ cleartool setview pmoura_view2

$ cd /vobs/2013-01/
  $ ls
lost+found  repro  testblabla.txt

  $ cleartool co -nc .
Checked out "." from version "/main/3".
  $ cleartool mkdir test
Creation comments for "test":
.
Created directory element "test".
Checked out "test" from version "/main/0".

  $ cleartool ci -nc test .
Checked in "test" version "/main/1".
Checked in "." version "/main/4".

Then we can conclude our backup was suscefull and we can delete the vbs copy restored on the alternative place

III - Conclusion

Vob Backup is not a matter of copy vbs, but we need to be sure:

There is no process running on this Vob.

The backup must be tested.

 

 

Hi Everyone,

How are you doing on this week?

On 2013-08-14 I submitted a post regarding how to configure the CC scheduler on timely basis (see the link on the References below),

however a new question arrives if you try to do that as regular user but NOT using root,  see that:

If I try to use a regular user we cannot edit the scheduler

cleartool schedule -edit -schedule
cleartool: Error: Unable to edit schedule: Permission denied.
 

So if you are interested to provide permissions to regular user to set jobs on timely basis consider:

1) As root see the current Scheduler Access Control List.

cleartool schedule -get -acl
# Scheduler ACL:
Everyone: Read

2) Delegate the permission to the desired user.
As root run

 cleartool schedule -edit  -acl

And add the user:

Note: If you just use the account name you will have a failure:

# Scheduler ACL:
Everyone: Read
User:user1: Full


#####
Replace the ACL? [yes]
cleartool: Error: ACL identity's name must be non-NULL.
cleartool: Error: Unable to set ACL entry for line 3: error detected by ClearCase subsystem.

######
You should use Domain/account style.

If the account is locally (/etc/passwd) uses <unknown>/accountname


User:<unknown>/user1 Full

Note: <unknown> as literal.


####

4) Then you will be able to edit the Scheduler by using that user:

[user1@machineXYZ ~]$ cleartool schedule -edit -schedule

5) Note: If you are interested to create new tasks you should provide writes to the user to edit /var/adm/rational/clearcase/scheduler/tasks/task_registry file or create the tasks there by using root account.

The next steps to create timely basis jobs, are avaiable ton the reference below:

References:

"How to configure ClearCase Scheduler to run tasks on timely basis?"
https://www.ibm.com/developerworks/community/blogs/ClearCaseonOurDays/entry/how_to_configure_clearcase_scheduler_to_run_tasks_on_timely_basis1?lang=en

"Unable to edit schedule: Permission denied"

http://www-01.ibm.com/support/docview.wss?uid=swg21135247

"schedule" man page.

http://pic.dhe.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.rational.clearcase.cc_ref.doc%2Ftopics%2Fct_schedule.htm

 

Note: If you just need to run the task in behalf of other user than root, but you are NOT interested to allow the regular user to edit the Clearcase scheduler, you could change your task script file to run the commands in name ot the desired user: For instance:

Before the change:                                                                 
                                                                                   
#!/bin/bash                                                                        
                                                                                   
cleartool=/usr/atria/bin/cleartool                                                 
                                                                                   
$cleartool lsvob >> /tmp/$(date +%F:%H:%M:%S)-vobs.txt                             
                                                                                   
bin/echo $(date) >> /tmp/$(date +%F:%H:%M:%S)-vobs.txt                             
                                                                                   
                                                                                   
After the change:                                                                  
                                                                                   
#!/bin/bash                                                                        
                                                                                   
cleartool=/usr/atria/bin/cleartool                                                 
                                                                                   
su - user1 -c "$cleartool lsvob >> /tmp/$(date +%F:%H:%M:%S)-vobs.txt"           
                                                                                   
su -  user1  -c "/bin/echo $(date) >> /tmp/$(date+%F:%H:%M:%S)-vobs.txt"                                                            
                                                                                

Regards,

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################



 

 

 

Hi,

It's Friday!!!!!

Let me share today, this problem.

If  you get "No vob object entry for the vob tag" while   trying to access a vob (mounting it or just describing it) probably you have just the Vob Tag, but the Vob Registry on the Registry Server it was gone.

You can run  "/usr/atria/etc/rgy_check -vob" to verify that, and you can fix it by:

1) Remove the tag:

cleartool rmtag -vob  <vob-tag

2) Registry the Vob again:

cleartool register -replace  -vob  -host  <HOSTNAME>    -hpath <VOB-STORE>  -gpath  <VOB-STORE>  <VOB-STORE>

3) Then re-tag the Vob:

cleartool mktag   -vob    -tag  <VOB-TAG> -replace -public   -host <HOSTNAME>   -hpath <VOB-STORE>  -gpath  <VOB-STORE>  <VOB-STORE>

Regards,

Have a Great Weekend!

 

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################

Hey,

Let me share this tip:

Imagine that you must  to run an executable with setuid permission  inside a vob, how do you do that?

To be able to do that, basically you will need, as root,  to run "change_suid_mounts -enable" then restart CC, since by default Vobs and Views using "nosuid".

NOTE: Be caution to enable that since  setuid permission over a NO safety code could compromise your system.

 

See the example below:

1) The code hello.c will print who is the effective user running the command (provided by setuid).

cat hello.c

#include <stdio.h>
main ()
{
 printf (" Details related this process \n" );
 system ( " ps -fe |grep hello |grep -v grep " );
 printf ("\n Type  \"x\" and press \"Enter\" to exit \n");
 scanf ( "%d, &a" );
}

 

2) I have that file now compiled and belonging  to root

The binary

stat  /home/John/hello
  File: `/home/John/hello'
  Size: 13056      Blocks: 32         IO Block: 4096   arquivo comum
Device: 802h/2050d Inode: 2392121     Links: 1
 

Access: (4755/-rwsr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

3) Running the code outside ClearCase

John@SUSE1164B:~> whoami
John
John@SUSE1164B:~> ./hello
 Details related this process
root     20982 12727  0 10:31 pts/2    00:00:00 ./hello
 Type  "x" and press "Enter" to exit
x
John@SUSE1164B:~>

So, the code is running as expected and due to setuid it is running as root, even a regular user fire the
binary.

4) Verifying how vob and viewroot ar mounted
 

mount |egrep "John-vob1|viewroot"

SUSE1164B:/dev/mvfs on /view type mvfs (rw,viewroot,nosuid)
xyz-machine:/vol/John/vobs/John-vob1.vbs on /tags/John-vob1 type mvfs (uuid=2d5df461.16d511e1.8eda.00:50:56:98:21:c3,nosuid)

As default both are mounted as "nosuid".

5) If I have the file inside a Vob (and having root as owner) what if the results by running it?

Attempt to run the binary using John (with default options regarding mount)

John@SUSE1164B:~> whoami
John

John@SUSE1164B:~> cleartool setview view1-John-nas

John@SUSE1164B:~> cd /tags/John-vob1/    #Since the vob is already mounted:

John@SUSE1164B:/tags/John-vob1>
> ls -l hello
 

-r-sr-xr-x 1 root John 13056 Jan 11 09:10 hello

John@SUSE1164B:/tags/John-vob1>   ./hello

 Details related this process
John   23772 23717  0 10:56 pts/2    00:00:00 ./hello
 Type  "x" and press "Enter" to exit

Conclusion: Even tough  setuid is set for on "hello" the binary ran as the user that fired the file,
this is expected since vob and /view are mounted with nosuid

 

6) Enabling setuid on view and mount

Stop the view and then run as root:

change_suid_mounts -enable

Setuid-honoring MVFS mounts are now enabled.  You must stop and
restart ClearCase for this change to take effect.

Then restart clearcase and verify that no is have no more "nosuid" as option:
 

/etc/init.d/clearcase restart
 

mount |egrep "view|John-vob1"

SUSE1164B:/dev/mvfs on /view type mvfs (rw,viewroot)
xyz-machine:/vol/John/vobs/John-vob1.vbs on /tags/John-vob1 type mvfs (uuid=2d5df461.16d511e1.8eda.00:50:56:98:21:c3)

Reference: https://www-304.ibm.com/support/docview.wss?uid=swg21260652

7)   Attempt to run the binary using John (with setuid enabled to mount):

John@SUSE1164B:~> cleartool setview view1-John-nas
John@SUSE1164B:~> cd /tags/John-vob1/
John@SUSE1164B:/tags/John-vob1> ./hello

 Details related this process
root     24927 24914  0 11:05 pts/2    00:00:00 ./hello
 Type  "x" and press "Enter" to exit
x

Conclusion: Having setuid mount enable this setuid work properly.

Regards,

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

 

 

Hi,

Looking for checked outs from a determined user on many vobs is easy to do, however do NOT forget to have the target vobs mounted.

For instance if I look for checkouts from "pmoura" user on vobs "/vobs/vob2000" and "/vobs/2013-01" I must have the two vobs mounted otherwise I could have a false negative here:

Example:

1) Seting a view.

$cleartool setview view1

2) Then running the apropriated "cleartool lsco" command:

cleartool lsco -long -user pmoura -avobs
$

The empty results here is a false negative, since the vobs are umounted.

cleartool lsvob

  /vobs/vob2000         /vobstore/vob2000.vbs
  /vobs/2013-01        /vobstore/2013-01.vbs

 

3) Mounting the vobs and looking for checkouts again:

$cleartool mount /vobs/vob2000

$cleartool mount /vobs/2013-01

$cleartool lsco -long -user pmoura -avobs

2013-05-13T15:29:55-04:00 pmoura.pmoura@RHEL5U764B
  checkout directory version "/vobs/2013-01/repro" from /main/1 (reserved)
  by view: view1 ("ABC-MACHINE:/viewstore/view1.vws")

 

Regards,

Pedro Moura

 

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

 

 

 

 

 

Hi,

Before prepare a SuSE 12 enviroment for ClearCase you must be aware

Btrfs is not supported by CC and if you have the root partition with that file system you will have problems to load MVFS

 

While starting CC you'll get:

 

# /opt/rational/clearcase/etc/clearcase start
ClearCase is stopped
Starting ClearCase
ClearCase daemons: albd_server modprobe: ERROR: could not insert 'mvfs': Invalid argument
Loading the MVFS was unsuccessful(8:1)
/opt/rational/clearcase/etc/clearcase: Loading MVFS failed

and from the syslog you'll see "ERROR: MVFS loaded with root directory not at file system root."

 

So install your SuSE with ext4, ext3, reiserfs or GPFS.

Take a look on this two Technotes to prepare your SLEs 12 for CC

 

Rational ClearCase does not support Btrfs as the root file system
http://www-01.ibm.com/support/docview.wss?uid=swg21690889

How to configure SUSE SLES12 to run Rational ClearCase
http://www-01.ibm.com/support/docview.wss?uid=swg21691807

Best Regards,

 

Pedro Moura                                                                         

##########################################Disclaimer ###################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
######################################################################################

 

I'm back!

Lets talk about which actions we should be able to do on Dynamic or Snapshot Views on ClearCase, in case of Licensing failures.

Imagine you are working on ClearCase and suddenly your License Key Server (RLKS) start to be NOT available. It is good to know what your users could keep doing while you are fixing the RLKS:


As stated on http://www-01.ibm.com/support/docview.wss?uid=swg21148560 we have some "cleartool commands" that we can still able to do so consider the two possibilities:

For Dynamic Views:
 If you still having the vob mounted, you should be able to:
    Set the view (or start it);
    cd to the Vob mount point (that matches with Vob Tag):
    browse through the directories and read the files inside the vob;
    It will possible to create view private files also.
 
  Any other task  is NOT able to do, such as Check out/in, mkview, mkvob,  to get element details, diff two versions, version tree and etc.
    
For Snapshot views:
    If you already have a Vob loaded (before the RLKS unavailability):
    You should be able to browse Vob directories and read the files, through the View  workspace (root view directory).


  Any other task is NOT able to do, such as view update,  Check out/in, mkview, mkvob,
  to get element details, diff two versions, version tree and etc.
    



See one example below:


1) Realized we have no Licensing:

[user1@MachineXYZ dir1]$ cleartool hostinfo -l

cleartool: Error: License checkout error from Rational Common Licensing:

Cannot connect to license server system.
 The license server manager (lmgrd) has not been started yet,
 the wrong port@host or license file is being used, or the
 port or hostname in the license file has been changed.
Feature:       ClearCase
Server name:   192.168.1.1
License path:  27000@192.168.1.1:
FLEXnet Licensing error:-15,570.  System Error: 115 "Operation on progress"
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".
cleartool: Error: You do not have a license to run ClearCase.

2) Even without Licensing you can read elements from the vob:

2.1) Setting a existing view:

[user1@MachineXYZ ~]$ cleartool setview pmoura_view1

2) Changing to the Vob directory - that is already mounted:

[user1@MachineXYZ ~]$ cd /vobs/abcVob/

3) Alternating to a directory inside the Vob:

[user1@MachineXYZ abcVob]$ cd dir1/

4) Listing and reading files:

[user1@MachineXYZ dir1]$ ls
file2.txt  new-file.txt
[user1@MachineXYZ dir1]$ cat file2.txt
blabla

5) But NOT able to  get details about the element:

cleartool ls  file2.txt

cleartool: Error: License checkout error from Rational Common Licensing:
Cannot connect to license server system.
 The license server manager (lmgrd) has not been started yet,
 the wrong port@host or license file is being used, or the
 port or hostname in the license file has been changed.
Feature:       ClearCase
Server name:   192.168.1.1
License path:  27000@192.168.1.1:
FLEXnet Licensing error:-15,570.  System Error: 115 "Operation in progress"
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".
cleartool: Error: You do not have a license to run ClearCase.

NOTE: Since you are NOT able to run "cleartool lsvob/lsview"  without licensing, is a good idea to keep a list from them (vobs and views) recorded for deal with the situations above.

That's all for today!!! Have a Great Weekend!

 

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################


 

Hi,

Probably you already need to determine who have deleted a View or Vob, for that you can take a look on aldb_logs.* files at Registry Server.

For instance:

See my results from my tests, and based on them you  could research on              
aldb_log*  files on Registry:
                                                                                    
                                                                                    
Monitoring the Registry server:                                                     
                                                                                    
1) Deleting a view using the View owner  (view owner is pmoura that has             
43126 as UID).                                                                      
                                                                                    
                                                                                    
When I ran cleartool rmview -tag <view-name> the action was recorded on             
alb_log. And I was able to see  that was pmoura that has delete it due              
to  " 43126.43126@RHEL5U764B"                                                       
                                                                                    
==> albd_log <==                                                                    
2013-04-15T10:01:59-04:00 albd_server(3906): Ok: 43126.43126@RHEL5U764B             
removed:                                                                            
-entry=view_object;-hostname=RHEL5U764B;-local_path=/viewstore/View-to-b            
e-deleted.vws;-owner=pmoura;-view_uuid=9bc9c975.a5d311e2.85a9.00:50:56:9            
8:72:93;                                                                            
2013-04-15T10:01:59-04:00 albd_server(3906): Ok: 43126.43126@RHEL5U764B             
removed:                                                                            
-entry=view_tag;-tag=View-to-be-deleted;-hostname=RHEL5U764B;-global_pat            
h=/net/RHEL5U764B/viewstore/View-to-be-deleted.vws;-region=unix1;-view_u            
uid=9bc9c975.a5d311e2.85a9.00:50:56:98:72:93;                                       
                                                                                    
                                                                                    
2) Deleting a view using other accounts:                                            
                                                                                    
2.1) By root (on the same system) (see root uid/gid  at  "0.0@RHEL5U764B" )                                                                  
                                                                                    
013-04-15T11:19:46-04:00 albd_server(3906): Ok: 0.0@RHEL5U764B removed:             
-entry=view_object;-hostname=RHEL5U764B;-local_path=/viewstore/viewtest6            
.vws;-owner=pmoura;-view_uuid=e0c95af8.a5e011e2.8d2b.00:50:56:98:72:93;             
2013-04-15T11:19:46-04:00 albd_server(3906): Ok: 0.0@RHEL5U764B removed:            
-entry=view_tag;-tag=viewtest6;-hostname=RHEL5U764B;-global_path=/viewst            
ore/viewtest6.vws;-region=unix1;-view_uuid=e0c95af8.a5e011e2.8d2b.00:50:            
56:98:72:93;                                                                        
                                                                                    
2.2) By root (from remote system): (see  -2.-2 at  " Ok: -2.-2@RHEL63x64 ")                                                                                  
                                                                                    
2013-04-15T10:55:07-04:00 albd_server(3906): Ok: -2.-2@RHEL63x64                    
removed:                                                                            
-entry=view_object;-hostname=RHEL63x64;-local_path=/tmp/test1.vws;-owner            
=pmoura;-view_uuid=6593689e.a5de11e2.83b4.00:50:56:98:6f:d1;                        
2013-04-15T10:55:07-04:00 albd_server(3906): Ok: -2.-2@RHEL63x64                    
removed:                                                                            
-entry=view_tag;-tag=test1;-hostname=RHEL63x64;-global_path=/tmp/test1.v            
ws;-region=unix1;-view_uuid=6593689e.a5de11e2.83b4.00:50:56:98:6f:d1;               
                                                                                 

I hope the above lines help you!!

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

Hi Everyone,

I'm on Vacation up to 2013-07-17,  see you soon with more about ClearCase.

Regards,

 

Pedro Moura

Hi Everyone,

This was a Very Nice Year, thanks by following this blog, and let me wish you a

HAPPY NEW YEAR!!!!!

Best wishes

Pedro Moura

Note: I'll be on vacation from Jan 6th - Fev 3th.

 

##########################################Disclaimer ###################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
######################################################################################

Hi guys,

We know on to support the CCRC (ClearCase Remote Clients) on CC version 7.1.x we expected to have CM_Server feature installed on a Server.

When select CM_Server feature to be installed automatically you will have Websphere and IBM HTTP Server installed to suport it. 

After you have them installed  some times we fall on these question:

How to stop and start Websphere and IBM HTTP services if necessary?

Is easy to do, but before run the commands below be sure you can stop the services now, since the CCRC users will be unavaible to work with ClearCase.

As root you can use the following:

First stop WebSphere:
/opt/IBM/WebSphere/AppServer/bin/stopServer.sh server1

Then stop IBM HTTP:

/opt/IBM/HTTPServer/bin/apachectl -k stop

 

To start use:

First start IBM HTTP:

/opt/IBM/HTTPServer/bin/apachectl -k start

Then start WebSphere:

/opt/IBM/WebSphere/AppServer/bin/startServer.sh server1
 

In time, if you have issues with WebSphere or IBM HTTP Sever not running after a reboot (a machine restart), you should add the start scripts inside a script that will be read on boot process, for instance:

For a Red Hat add the following lines below on your /etc/rc.local file


/opt/IBM/HTTPServer/bin/apachectl -k start
/opt/IBM/WebSphere/AppServer/bin/startServer.sh server1
 

For next post, I'll show some interesting command but for CCRC WAN!

Regards,

Pedro Moura

##########################################Disclaimer ##############################################
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."  #
#################################################################################################
 

Hello everyone,

Here you have 3 examples with the steps while reformating a VOB, on the first you have a regular dump / load process using "cleartool reformatvob",

on the second we have a manual dump and load using db_dumper and db_loader tool, and the third example we have a dump made using "cleartool reformatvob"  followed by a load using db_loader, util for the cases where a "cleartool reformatvob -load" fail.

####### Index ###########
I - Regular Reformatvob (dump and load)

II - Manual dump/load

III - Dump with reformatvob and load manual

#########################

I - Regular Reformatvob  (dump and load)

cleartool lock vob:/vobs/vob-snap-test

cd /home/user1/vobstore/vob-snap-test.vbs/
[user1@machine1 vob-snap-test.vbs]$ ls -lhtr
total 32K
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 vob_oid
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 replica_uuid
-rw-r--r--. 1 user1 user1  625 Nov  1 10:59 vob_server.conf
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 s
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 d
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 c
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 db
drwxr-xr-x. 4 user1 user1 4,0K Nov  1 10:59 admin

[user1@machine1 vob-snap-test.vbs]$ ls -lhtr db/
total 516K
-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
-rw-r--r--. 1 user1 user1 8,0K Nov  1 10:59 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Nov  1 10:59 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Nov  1 10:59 vob_db_schema_version
-rw-r--r--. 1 user1 user1    0 Nov  1 10:59 almd.lck
-rw-r--r--. 1 user1 user1  108 Nov  1 10:59 vob_db.str_file
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k04
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k02
-rw-r--r--. 1 user1 user1  24K Dez 20 18:22 vob_db.k01
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d05
-rw-r--r--. 1 user1 user1  28K Dez 20 18:22 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d01
-rw-r--r--. 1 user1 user1 8,0K Dez 20 18:22 vob_db.d03
-rw-r--r--. 1 user1 user1 334K Mar 29 10:26 almd
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tcf
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:26 vista.taf
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tjf
drwxr-xr-x. 2 user1 user1 4,0K Mar 29 10:26 logs

cleartool reformatvob -dump /home/user1/vobstore/vob-snap-test.vbs

[user1@machine1 vob-snap-test.vbs]$ ls -lhtr
total 36K
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 vob_oid
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 replica_uuid
-rw-r--r--. 1 user1 user1  625 Nov  1 10:59 vob_server.conf
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 s
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 d
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 c
drwxr-xr-x. 4 user1 user1 4,0K Nov  1 10:59 admin
drwxr-xr-x. 3 user1 user1 4,0K Mar 29 10:29 db.reformat
drwxrwxr-x. 2 user1 user1 4,0K Mar 29 10:29 dump.done
[user1@machine1 vob-snap-test.vbs]$

[user1@machine1 vob-snap-test.vbs]$ ls -lhtr db.reformat/
total 516K
-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
-rw-r--r--. 1 user1 user1 8,0K Nov  1 10:59 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Nov  1 10:59 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Nov  1 10:59 vob_db_schema_version
-rw-r--r--. 1 user1 user1    0 Nov  1 10:59 almd.lck
-rw-r--r--. 1 user1 user1  108 Nov  1 10:59 vob_db.str_file
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k04
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k02
-rw-r--r--. 1 user1 user1  24K Dez 20 18:22 vob_db.k01
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d05
-rw-r--r--. 1 user1 user1  28K Dez 20 18:22 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d01
-rw-r--r--. 1 user1 user1 8,0K Dez 20 18:22 vob_db.d03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tcf
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tjf
drwxr-xr-x. 2 user1 user1 4,0K Mar 29 10:26 logs
-rwxrwxr-x. 1 user1 user1    0 Mar 29 10:29 orig
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:29 vista.taf
-rw-r--r--. 1 user1 user1 334K Mar 29 10:29 almd

[user1@machine1 vob-snap-test.vbs]$ ls -lhtr dump.done/
total 36K
-rw-rw-r--. 1 user1 user1 7,0K Mar 29 10:29 pass2_dump_file
-rw-rw-r--. 1 user1 user1  20K Mar 29 10:29 pass1_dump_file
-rw-rw-r--. 1 user1 user1 3,9K Mar 29 10:29 string_dump_file
-rw-rw-r--. 1 user1 user1  480 Mar 29 10:29 pass3_dump_file

 cleartool reformatvob -load /home/user1/vobstore/vob-snap-test.vbs

ls -lhtr
total 36K
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 vob_oid
-r--r--r--. 1 user1 user1   41 Nov  1 10:59 replica_uuid
-rw-r--r--. 1 user1 user1  625 Nov  1 10:59 vob_server.conf
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 s
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 d
drwxr-xr-x. 3 user1 user1 4,0K Nov  1 10:59 c
drwxr-xr-x. 4 user1 user1 4,0K Nov  1 10:59 admin
drwxr-xr-x. 3 user1 user1 4,0K Mar 29 10:30 db.03.29
drwxr-xr-x. 3 user1 user1 4,0K Mar 29 10:30 db

 ls -lhtr db.03.29/
total 516K
-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
-rw-r--r--. 1 user1 user1 8,0K Nov  1 10:59 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Nov  1 10:59 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Nov  1 10:59 vob_db_schema_version
-rw-r--r--. 1 user1 user1    0 Nov  1 10:59 almd.lck
-rw-r--r--. 1 user1 user1  108 Nov  1 10:59 vob_db.str_file
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k04
-rw-r--r--. 1 user1 user1  16K Dez 20 18:22 vob_db.k02
-rw-r--r--. 1 user1 user1  24K Dez 20 18:22 vob_db.k01
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d05
-rw-r--r--. 1 user1 user1  28K Dez 20 18:22 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Dez 20 18:22 vob_db.d01
-rw-r--r--. 1 user1 user1 8,0K Dez 20 18:22 vob_db.d03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tcf
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:26 vista.tjf
drwxr-xr-x. 2 user1 user1 4,0K Mar 29 10:26 logs
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:29 vista.taf
-rw-r--r--. 1 user1 user1 334K Mar 29 10:29 almd

 ls -lhtr db
total 552K
-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:30 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:30 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Mar 29 10:30 vob_db_schema_version
-rw-r--r--. 1 user1 user1    0 Mar 29 10:30 almd.lck
-rw-r--r--. 1 user1 user1 334K Mar 29 10:30 almd
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:30 vob_db.d03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:30 vista.tcf
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:30 vob_db.k04
-rw-r--r--. 1 user1 user1  155 Mar 29 10:30 vob_db.str_file
-rw-r--r--. 1 user1 user1  48K Mar 29 10:30 vista.tjf
-rw-r--r--. 1 user1 user1  16K Mar 29 10:30 vob_db.k02
-rw-r--r--. 1 user1 user1  24K Mar 29 10:30 vob_db.k01
-rw-r--r--. 1 user1 user1  12K Mar 29 10:30 vob_db.d05
-rw-r--r--. 1 user1 user1  28K Mar 29 10:30 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Mar 29 10:30 vob_db.d01
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:30 vista.taf
drwxr-xr-x. 2 user1 user1 4,0K Mar 29 10:30 logs

II - Manual dump/load

http://www-01.ibm.com/support/docview.wss?uid=swg21172574

 cleartool lock vob:/vobs/vob-snap-testLocked versioned object base "/vobs/vob-snap-test".

 /usr/atria/etc/dumpers/db_dumper.54 /home/user1/vobstore/vob-snap-test.vbs/db
0 hyperlinks dumped.
0 derived objects dumped.
59 events dumped.
1 locks dumped.
Dumper done.

-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:30 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:30 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Mar 29 10:30 vob_db_schema_version
drwxr-x---. 9 user1 user1 4,0K Mar 29 10:30 ..
-rw-r--r--. 1 user1 user1    0 Mar 29 10:30 almd.lck
-rw-r--r--. 1 user1 user1  155 Mar 29 10:30 vob_db.str_file
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:43 vob_db.k04
-rw-r--r--. 1 user1 user1  16K Mar 29 10:43 vob_db.k02
-rw-r--r--. 1 user1 user1  24K Mar 29 10:43 vob_db.k01
-rw-r--r--. 1 user1 user1  12K Mar 29 10:43 vob_db.d05
-rw-r--r--. 1 user1 user1  28K Mar 29 10:43 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Mar 29 10:43 vob_db.d01
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:43 vob_db.d03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:43 vista.tjf
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:43 vista.tcf
drwxr-xr-x. 2 user1 user1 4,0K Mar 29 10:43 logs
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:45 vista.taf
-rw-r--r--. 1 user1 user1 334K Mar 29 10:45 almd
drwxr-xr-x. 3 user1 user1 4,0K Mar 29 10:45 .
-rw-rw-r--. 1 user1 user1  20K Mar 29 10:45 pass1_dump_file
-rw-rw-r--. 1 user1 user1 3,9K Mar 29 10:45 string_dump_file
-rw-rw-r--. 1 user1 user1  480 Mar 29 10:45 pass3_dump_file
-rw-rw-r--. 1 user1 user1 7,0K Mar 29 10:45 pass2_dump_file
[user1@machine1 db]$

$ pwd
/home/user1/vobstore/vob-snap-test.vbs

[user1@machine1 vob-snap-test.vbs]$ mv db db.old
[user1@machine1 vob-snap-test.vbs]$ mkdir db
[user1@machine1 vob-snap-test.vbs]$ cd db

cd  /home/user1/vobstore/vob-snap-test.vbs/db.old

user1@machine1 db.old]$ /usr/atria/etc/db_loader /home/user1/vobstore/vob-snap-test.vbs/db
Dumped schema version is 80
59 events loaded.
90 pass 2 actions performed.
7 pass 3 actions performed.
Loader done.

[user1@machine1 db.old]$ ls -lhtr ../db
total 176K
-rw-r-----. 1 user1 user1  33K Jun  1  2011 vob_db.dbd
drwxrwxr-x. 2 user1 user1 4,0K Mar 29 10:50 logs
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:55 vob_db.k03
-rw-r--r--. 1 user1 user1 4,0K Mar 29 10:55 vob_db.d04
-rw-r--r--. 1 user1 user1    3 Mar 29 10:55 vob_db_schema_version
-rw-r--r--. 1 user1 user1 5,1K Mar 29 10:55 vista.taf
-rw-r--r--. 1 user1 user1  108 Mar 29 10:55 vob_db.str_file
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:55 vob_db.k04
-rw-r--r--. 1 user1 user1 8,0K Mar 29 10:55 vob_db.d03
-rw-r--r--. 1 user1 user1  12K Mar 29 10:55 vob_db.d01
-rw-r--r--. 1 user1 user1  24K Mar 29 10:55 vob_db.k01
-rw-r--r--. 1 user1 user1  16K Mar 29 10:55 vob_db.k02
-rw-r--r--. 1 user1 user1  28K Mar 29 10:55 vob_db.d02
-rw-r--r--. 1 user1 user1  12K Mar 29 10:55 vob_db.d05

 cleartool unlock vob:/vobs/vob-snap-test
Unlocked versioned object base "/vobs/vob-snap-test".

 cleartool checkvob -fix -pool /vobs/vob-snap-test

III - dump with reformatvob and load manual

cleartool lock vob:/vobs/vob-snap-test

 cleartool reformatvob -dump /home/user1/vobstore/vob-snap-test.vbs

[user1@machine1 vob-snap-test.vbs]$ cd dump.done/

[user1@machine1 dump.done]$ ls -lhtr
total 40K
-rw-rw-r--. 1 user1 user1  22K Mar 29 11:05 pass1_dump_file
-rw-rw-r--. 1 user1 user1 4,0K Mar 29 11:05 string_dump_file
-rw-rw-r--. 1 user1 user1  559 Mar 29 11:05 pass3_dump_file
-rw-rw-r--. 1 user1 user1 7,8K Mar 29 11:05 pass2_dump_file
[user1@machine1 dump.done]$ /usr/atria/etc/db_loader /home/user1/vobstore/vob-snap-test.vbs/db

NOTE: if necessary to keep the VOB on schema 54 run instead

/usr/atria/etc/db_loader -schema 54  /home/user1/vobstore/vob-snap-test.vbs/db

 ls ../db
logs        vob_db.d02  vob_db.d05  vob_db.k02  vob_db_schema_version
vista.taf   vob_db.d03  vob_db.dbd  vob_db.k03  vob_db.str_file
vob_db.d01  vob_db.d04  vob_db.k01  vob_db.k04

cleartool unlock vob:/vobs/vob-snap-test
Unlocked versioned object base "/vobs/vob-snap-test".

 

Best Regards,

 

Pedro Moura                                                                         

##########################################Disclaimer ###################################
"The postings on this site are my own and don't necessarily represent HCL or IBM's positions, strategies or opinions."  #
######################################################################################

Hey ClearCase peers, here you have an step-by-step example  on how to add two repositories (main media and fix)
to install CC  using console mode (can be used to upgrade as well) .

 

Note1: On my example CC 9 media is extracted to /tmp/cc/cc90/   and the file which I must point on IM as repository is   /tmp/cc/cc90/disk1/diskTag.inf

Note2: And CC 9.0.0.3 fix media is extracted to /tmp/cc/cc9003 and the rile which I must point on IM as repository is /tmp/cc/cc9003/repository.config

Note3: This only works for CC, but not for ClearQuest.

As root run:

/opt/IBM/InstallationManager/eclipse/tools/imcl -c  

1) Adding the ClearCase repositories
####

Enter "P" to change the preferences:

=====> IBM Installation Manager

Select:
     1. Install - Install software packages
     2. Update - Find and install updates and fixes to installed software packages
     3. Modify - Change installed software packages
     4. Roll Back - Revert to an earlier version of installed software packages
     5. Uninstall - Remove installed software packages

Other Options:
     L. View Logs
     S. View Installation History
     V. View Installed Packages
        ------------------------
     P. Preferences
        ------------------------
     A. About IBM Installation Manager
        ------------------------
     X. Exit Installation Manager

-----> p

#####

####

Enter "1" to work with the repositories.

=====> IBM Installation Manager> Preferences

Select:
     1. Repositories
     2. Appearance
     3. Files for Rollback
     4. SSL/TLS
     5. HTTP/FTP Proxy
     6. Passport Advantage
     7. Updates

     R. Return to Main Menu
-----> [1] 1

######

Enter "D" to add a new repository

=====> IBM Installation Manager> Preferences> Repositories

Repositories:
   

Other Options:
     D. Add Repository

     S. [X] Search service repositories during installation and updates

     R. Restore Defaults
     A. Apply Changes and Return to Preferences Menu
     P. Temporarily Keep Changes and Return to Preferences Menu

-----> D

####

Add the path diskTag.inf file inside  to CC 9.0 repository.

=====> IBM Installation Manager> Preferences> Repositories> Add repository

Enter a new repository location. To skip, press Enter:
-----> /tmp/cc/cc90/disk1/diskTag.inf

######

Enter "D" to add a new repository (to CC 9.0.0.3 fix)

Checking repositories...

=====> IBM Installation Manager> Preferences> Repositories

Repositories:
     1. [X] /tmp/cc/cc90/disk1/diskTag.inf

Other Options:
     D. Add Repository

     S. [X] Search service repositories during installation and updates

     R. Restore Defaults
     A. Apply Changes and Return to Preferences Menu
     P. Temporarily Keep Changes and Return to Preferences Menu

-----> D

####

Enter the path to repository.config file inside CC 9.0.0.3 fix media

=====> IBM Installation Manager> Preferences> Repositories> Add repository

Enter a new repository location. To skip, press Enter:
-----> /tmp/cc/cc9003/repository.config

######

Enter "A" to apply the changes

Checking repositories...

=====> IBM Installation Manager> Preferences> Repositories

Repositories:
     1. [X] /tmp/cc/cc90/disk1/diskTag.inf
     2. [X] /tmp/cc/cc9003/repository.config

Other Options:
     D. Add Repository

     S. [X] Search service repositories during installation and updates

     R. Restore Defaults
     A. Apply Changes and Return to Preferences Menu
     P. Temporarily Keep Changes and Return to Preferences Menu

-----> A

#######

Enter R to return to Main Menu

=====> IBM Installation Manager> Preferences

Select:
     1. Repositories
     2. Appearance
     3. Files for Rollback
     4. SSL/TLS
     5. HTTP/FTP Proxy
     6. Passport Advantage
     7. Updates

     R. Return to Main Menu
-----> [1] R

########

2) Proceeding with the Instalation steps

Enter "1" to start the installation.

=====> IBM Installation Manager

Select:
     1. Install - Install software packages
     2. Update - Find and install updates and fixes to installed software packages
     3. Modify - Change installed software packages
     4. Roll Back - Revert to an earlier version of installed software packages
     5. Uninstall - Remove installed software packages

Other Options:
     L. View Logs
     S. View Installation History
     V. View Installed Packages
        ------------------------
     P. Preferences
        ------------------------
     A. About IBM Installation Manager
        ------------------------
     X. Exit Installation Manager

-----> 1

 

Best Regards,

Pedro Moura
                                                                  

##########################################Disclaimer ####################################################################
"The postings on this site are my own and don't necessarily represent HCL or IBM's positions, strategies or opinions."  #
#########################################################################################################################

Let me invite you to join and participate to the The ClearCase & ClearQuest Community (http://www.cccqcommunity.com/)