" /> Status for Andrew DeFaria: April 11, 2004 - April 17, 2004 Archives

« April 4, 2004 - April 10, 2004 | Main | April 18, 2004 - April 24, 2004 »

April 16, 2004

Reregistering Clearcase objects

  • Worked with Mike trying to get Clearcase web to function correctly
  • Since the IP address of the new servers will be different I worked on a script that will reregister views and vobs. This reregistering and retragging should fix up the IP address problem

Posted by at 10:34 AM |

April 15, 2004

Clearcase & Clearquest Web

Today...

  • Partitioned drive

  • Installed Windows XP

  • Attended Peregrine Training

  • Configured Clearquest web

  • Worked with Michael on Clearcase web problems

  • Worked on problem with accessing Clearcase due to outgrowing the lockmgr's limits

  • Implemented Heap Size fix and Lockmgr fix to new production servers

Several people have been reporting odd problems with Clearcase. In investigating this I checked the server log files and found a lot of:

*** db_VISTA database error -922 - the lock manager is busy

Searching Rational's web I saw lock manager problems, settings and guidelines which seems to indicate that we've probably already outgrown the default parameters for the lockmgr. The article talks about monitoring the server processes for a week to determine how to best set the values for lockmgr. Unfortunately we don't have a week to wait so for the mean time I simply set the following parms on the lockmgr and restarted Clearcase on the vob sever:

-a almd -u 100 -f 200 -q 500
That should give us some breathing room. Meantime I set up a quick script to monitor the number of server processes as per the article.

Posted by at 7:37 PM |

April 13, 2004

The new servers have arrived!

The new servers have arrived and I have been testing them today. Here's what I managed to do:

  • Installed Clearcase server software on new machines.
  • Configured storage locations for vobs/views
  • Practiced moving a vob and view over to the new servers. The view even had a checked out file.
  • Once set up on the new servers accessed the view and insured that I could access it and that the checked out element was still accessible.

In setting up prodfix01 as a the vob server I encountered some problems attempting to set the storage location. The default wizard was not the right way to go. Instead I had to:

cleartool> mkstgloc -vob -host prodfix01 -hpath D:\vobstore -gpath \\prodfix01\vobstore vobstore \\prodfix01\vobstore

Naturally this will not due as this machine will eventually be renamed as rtnlprod01, not prodfix01. This will need to be adjusted during the downtime. Just some notes from my testing session:

After setting up the servers I had to create the storage locations as above. I called them vobstore and viewstore instead of ccvobstg/ccviewstg. Personally I find the former more descriptive.

I tried to simply mktag for the vob and view on the new server but that would not work. Instead I had to:

cleartool register -replace -view \\path\to\view
cleartool register -replace -vob \\path\to\vob
cleartool mktag -replace -view -tag \\path\to\view
cleartool mktag -replace -vob -tag \\path\to\vob
cleartool startview
cleartool mount

Again, if we slide the server into place after changing the DNS/Machine name <-> IP address mapping this should not be an issue.

We should be ready to go, perhaps this coming Thursday evening (sometime after 7 Pm). What we would need to do is:

  1. Announce to the Clearcase community that Clearcase will be down for a few hours Thursday night (7 Pm - 9 Pm)
  2. At 7 Pm stop Clearcase on rtnlprod01 and rtnlprod02
  3. xcopy /e /i /f /h /k /x > C:\vobstore_xcopy.log 2>&1
  4. xcopy /e /i /f /h /k /x > C:\viewstore_xcopy.log 2>&1
  5. Shutdown rtnlprod01 and rtnlprod02
  6. Switch DNS so that prodfix01 -> rtnlprod01 and prodfix02 -> rtnlprod02
  7. Test vob/view access from desktop clients.

Posted by at 6:11 PM |