14.4 Common Errors During a Relocate Operation

The following conditions are the most frequent causes of failed relocate operations:

In general, you can restart relocate. You fix the reported error and restart relocate with the same command line. Errors that occur during source VOB element removal require manual repair.

Errors Not Related to Source VOB Element Removal

In the event of an error:

  1. Stop and fix the problem. For example, if relocate reports a locked type in the target VOB, unlock it. If it reports a checked-out version in the relocate set, resolve it.

  2. Restart relocate. When invoked with an identical command line, relocate resumes processing from the interrupt point, provided that these conditions are met:

  3. If any of these conditions is not met, relocate starts processing from the beginning, and it may encounter new problems that return you to Step #1 of this procedure.

Errors During Source VOB Element Removal

After relocate has re-created elements in the target VOB, it removes the elements from the source VOB. If this step fails (typically, due to a trigger on the rmelem operation), you must remove the elements manually, as follows:

  1. Find element OIDs from log file. Examine the relocate log file (view-stg-dir\relocate.log.date-time) and find the lines that specify the unique object IDs (OIDs) of the elements that relocate tried to remove but could not. You must remove these elements manually.

  2. Remove the elements. For each element reported in the log file, run this command:

  3. cleartool rmelem oid:OID-reported-in-relocate-output

  4. If necessary, remove the trigger that prevented relocate from removing the elements.

To avoid these errors, remove any rmelem triggers on elements before relocating them.