PM38183: CCRC COMPARE IN A SYMLINKED DIRECTORY ERRORS WITH 'THE INTERNAL OPERATION 'GET_CLEARTEXT' FAILED.'

Rational ClearCase Fix Pack (7.1.2.5) for version 7.1.2
Rational ClearCase Fix Pack (8.0.0.1) for version 8.0
Rational ClearCase Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearCase Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0

APAR status

• Closed as program error.

Error description

• APAR content:
  =============
  Headline:
  CCRC compare in a symlinked directory errors with 'The internal
  operation 'get_cleartext' failed.'
  
  APAR description:
  
  In IBM Rational ClearCase Remote Client (CCRC) 7.1.x, performing
  a 'Compare with Predecessor' or 'Compare with Another Version'
  operation results in errors similar to either of the following:
  
  -----
  Failed to invoke compare operation
  null
  -----
  
  -----
  Unable to access the version data for
  'C:\ccweb\user1\ccrcview\vob1\symlinktest\dir1\file1.txt': No
  such file or directory
  The internal operation 'get_cleartext' failed.
  -----
  
  - The issue only occurs in directories which are symlinks.
  
  - It has been seen to only occur when two or more elements
  within the same symlinked directory are checked out (all but the
  last checked out element within the directory will fail).
  
  - It can be seen regardless of whether the symlink target is
  within the same VOB or another (cross-vob symlink).
  
  - It occurs whether the target of the symlink is loaded or not.
  
  - It does not occur if the checkouts are performed first in the
  symlink target location.
  
  
  Steps to reproduce the issue:
  
  1. From IBM Rational ClearCase Explorer, add a new directory
  'symlinktest' to source control.
  
  2. Within 'symlinktest', add a new directory 'dir1' along with
  three new file elements contained within: file1.txt, file2.txt,
  file3.txt.
  
  Example structure: \vob1\symlinktest\dir1\file1.txt (file2.txt,
  file3.txt)
  
  3. Within 'symlinktest', add a new directory 'dir2'.
  
  Example structure: \vob1\symlinktest\dir2
  
  4. Right-click 'dir1' in the right-hand pane of ClearCase
  Explorer and select Symlinks > Create Symlink. Select 'dir2' as
  the target.  This will create a symlink path similar to
  '\vob1\symlinktest\dir2\dir1'.
  
  5. Log into CCRC, creating a view loading this VOB.
  
  6. Navigate to \vob1\symlinktest\dir2\dir1.
  
  7. Checkout files individually in this order: file1.txt,
  file2.txt, file3.txt.
  
  8. Attempt to 'Compare with Predecessor' for file1.txt or
  file2.txt.  The operation will error.  Attempt the same for
  file3.txt and the operation will complete as expected.
  
  
  Workaround:
  
  - Perform the checkouts in the symlink target location.
  
  - Ensure no more than one element is currently checked out in
  the directory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Compare in CCRC of symlinked directories fails.
  

Problem conclusion

• This issue has been fixed in the 7.1.2.5 and 8.0.0.1 releases of
   Rational ClearCase.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLEARCASE WIN

• Fixed component ID

  5724G2900

Applicable component levels

• R710 PSN

     UP