Monitoring ClearCase Performance

ClearCase is a complicated product, and when you encounter performance issues it’s quite difficult to figure out the reason.
IBM has some technotes and articles on the subject, but most of them involve running all sorts of commands and scripts and meticulously analyzing their output (see one example here).

A few months ago it came to my attention that ALMToolBox are working on a web-based, graphical monitoring tool which provides a simple yet powerful overview on system performance, both on the infrastructure level (CPU, I/O etc.) and on the application level (ClearCase objects and commands), and correlate them as seen below.


You can also watch a live demo on this page.

It’s still early in development but it looks promising, and I urge every ClearCase administrator to keep a close eye on this product.

Edit: Even better – it can be used to monitor virtually anything, not just ClearCase servers. In this page you can see a “vitality report” which also includes ClearQuest, JIRA and Bamboo servers.


Remove Problematic ClearCase Views

This handy little Perl script removes all traces of a view which is irremovable via conventional means – e.g. when the view storage is missing or inaccessible.

The script is design to run on UNIX in an interop environment, but can be easily be adjusted to other cases.

## Usage: perl <region> <view tag>
$region = $ARGV[0];
$region || die "Region must be specified!";
$tag = $ARGV[1];
$tag || die "View tag must be specified!";
## Detect view UUID
@uuid = `cleartool lsview -l -region $region $tag`;
foreach (@uuid)
  if (/View uuid/)
    s/View uuid: //;
    $uuid = $_;
# Remove the tag from the registry
system "cleartool rmtag -view -region $region $tag";
# Unregister the view
system "cleartool unreg -view -uuid $uuid";
# Remove view-related records from all VOBs
system "cleartool rmview -all -uuid $uuid";

Reference: Removing a view