ClearCase Version Importer limitations and known problems

This release of the ClearCase Version Importer has the following limitations and restrictions.
  • Items that are not imported with the ClearCase Version Importer:
    • Version history of the directory
    • Element properties
    • Hyperlinks (except for merge hyperlinks)
    • Labels
    • Hard links (imported as symbolic links instead)
    • Build scripts and triggers
    • Access control on imported objects
    • Rational® ClearCase® views that are not converted to a workspace
    • UCM metadata (such as the project, stream, baseline, and activity)
  • Incremental import: When you import the data from Rational ClearCase to IBM® Engineering Workflow Management (EWM) but have check-in changes on the Rational ClearCase side that must be imported, you can run the export command again to generate intermediate files. Then, you can import data into EWM, and the importer command imports only the changed Rational ClearCase data by skipping any versions that were previously imported.
  • Command failures: Detailed failure information is reported in the log file. The path to the log file is <data folder>/logs/[export|import]CCase.log.
  • Colon in branch type name: Older versions of Rational ClearCase MultiSite® append site names to branch names with a colon when the branch name has a conflict during the multisite synchronization. Because the colon is a special character in Windows, you cannot export versions with a colon in the name on a Windows host. Use a Linux host to export the data or rename the branch type. Then, export the data again. You can also exclude file elements from being exported. For more information, see Excluding file elements from the exported data files.
  • Imported change-set creation time does not match the version creation time that is recorded in Rational ClearCase: The ccc import ccase command creates change sets with creation times that are based on the associated version's creation time, which is recorded in Rational ClearCase. It then adds a few milliseconds for each version of the file that is imported. If the file has many versions, such as more than 1,000, the change-set creation time is newer than the Rational ClearCase version creation time.
  • Increasing heap size for large exports and imports: The export and import commands use memory proportional to the number of versions they process. If you plan to export and import many tens of thousands of versions at a time, use a server class machine and set the maximum heap size for the JVM to about 1.5 gigabytes.
    Note: You can set the maximum heap size by editing the value in the ccc.ini file. By default, the parameter setting is -Xmx512m. You can set it to about 1.5 gigabytes by changing it to -Xmx1512m.
  • Merge hyperlinks: When you have more than one merge hyperlink to a version in a Rational ClearCase version tree, part of the link might not be migrated into EWM source control. The warning message, Could not create a merge change set from <...> to <...>, is recorded in the import command log file.
  • Running multiple import commands: You cannot run multiple import commands in parallel and import data to the same EWM component.
  • Importing files, folders, and symbolic links of a sub-VOB component: You cannot import files, folders, or symbolic links that are part of a sub-VOB component. To migrate them with the ClearCase Version Importer, you must rename the attribute type, and then run the ccc export ccase command. After the command completes, you can rename the attribute type to its original value.
  • Rational ClearCase lshistory event records: The ClearCase Version Importer migrates all versions of a file, but that does not mean all the event records of Rational ClearCase lshistory command result are copied to the history of EWM source control. For example, events with create branch, create file element, or import file element are not imported into EWM because no versions are associated to the event records.
  • The maximum number of versions that you can export per file is 10,000 versions. To reduce the number of versions, you can filter versions during the export. For more information, see Selecting versions to export by filtering.
  • When you run the resume or incremental export, the exporter extracts the starting time of the previous export from the data folder, and it exports versions that are only newer than the starting time. If you are exporting a Rational ClearCase MultiSite-replicated VOB, versions that are created on a remote mastered branch that are not yet available in the previous export might not be exported in the subsequent export. Because their creation times are recorded at the remote site, the versions might be older than the starting time of the previous export. Ensure that the replicated VOBs are in synchronization with all other VOBs before you export the data initially.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki