Mandatory patch replacement to correct broken hyperlinks

Technical Bulletin #14

Mandatory patch replacement to correct broken hyperlinks

Recent patches to Release 2.1 of ClearCase and Release 1.1 of MultiSite for UNIX have been found to be bad. The bad patch causes errors in updating hyperlinks during checkin. The most common case is merge hyperlinks. Here are the symptoms:

If you describe the target of a hyperlink, no hyperlink is listed.
If you describe the source of a hyperlink, the hyperlink points to "object not available".
If you use lsvtree -merge on an affected element, an "INTERNAL ERROR" is returned.

Rational Engineering has taken the following actions:

Created new patches to replace the bad patches.
Created a tool, check-hlinks.pl to find defective links and create a script to repair all incomplete hyperlinks caused by the bad patches. This tool is available, with associated files, in a tar file.

If you have applied a bad patch to your system, you must not use the system with the bad patch. It is mandatory that you:

Immediately turn off the vob_scrubber by logging in as root on each VOB server and issuing the following commands:

 # cd /usr/atria/etc

 # mv vob_scrubber vob_scrubber.off

Apply the proper patch.
Run check-hlinks.pl on all your VOBs and run the resulting script to repair the hyperlinks.
Turn the vob_scrubber back on by issuing the following command:
```
 # mv vob_scrubber.off vob_scrubber
 
```

ClearCase 2.1

Architecture	Bad Patch Number	Good Patch Number
sun4	2.1-85	2.1-100
sun5	2.1-86	2.1-101
sgi5	2.1-87	2.1-102
sgi6	2.1-88	2.1-103
osf1_axp	2.1-89	2.1-104
aix3_power	2.1-90	2.1-105
aix4_power	2.1-91	2.1-106
hp9_pa	2.1-92	2.1-107
hp9_800	2.1-93	2.1-108
hp10_pa	2.1-94	2.1-109
uw2_x86	2.1-95	2.1-110

MultiSite 1.1

Architecture	Bad Patch Number	Good Patch Number
sun4	1.1-12	1.1-15
sun5	1.1-13	1.1-16
hp10_pa	1.1-14	1.1-17

What to do

Determine if you have applied the bad patch and find the number of the replacement patch for your architecture from the tables.

Obtain the replacement patch and the check-hlinks package from Rational Customer Support.

If you have anonymous FTP capability: Use the ftp program to connect to host ftp.rational.com. Follow the instructions for obtaining ClearCase patches. The check-hlinks package is in the /dist/check-hlinks directory.

If you have WorldWide Web access: Connect to http://www.rational.com and obtain the patch from the Customers Only Technical Information Tree. The check-hlinks package is at ftp://ftp.atria.com/dist/check-hlinks.

If you do not have FTP or WWW: Call Rational Customer Support (see phone number below). Request that the patches and the check-hlinks package be sent to you by electronic mail or magnetic tape.

The check-hlinks packages are named according to the architecture for which they are intended. If the package will run on any architecture at your site, it can operate on all the VOBs at your site. If you do not find a package that fits your site, please inform Rational customer support for direct assistance.

Install the appropriate patch in the release area for ClearCase 2.1 or for MultiSite 1.1. Follow the instructions included in the patch's .doc file and the README file included with check-hlinks.pl. Regardless of whether check-hlinks is available, you must install the patch immediately.

Any Questions?

If you have any questions regarding the situations discussed in this Technical Bulletin, please contact Customer Support at support@rational.com or (781) 676-2450 in Massachusetts or 31-23-569-4310 in the Netherlands.