Synchronization import problems
This section describes problems that can occur during the
import phase of synchronization.
- Packets accumulate in incoming storage bay
A recoverable error occurs when an update packet is lost and therefore is not applied to your replica. - Packet is not applicable to any local replicas
A synchronization import can fail when a replica has been moved and the host-name property has not been updated with the chreplica command. - Read from input stream fails
If a packet is corrupted, a syncreplica –import command can fail with an error message about the "read from the input stream" failing. - Element changes during operation
If a syncreplica –import command fails with an error message about the element changing during the operation, try the import operation again. - The rmreplica operation cannot be imported
Import of an rmreplica operation fails if the importing replica records that the removed replica still masters objects. - Pre 7.0 systems only: database limit is exceeded
DevOps Code ClearCase versions 4.0 and later include support for VOB database schema (version 54). If you update one or more replicated VOBs in a family to schema version 54, you do not have to update the other replicas in the VOB family immediately. However, you must update all replicas before one of the updated replicas exceeds the database limit of the previous schema (version 53). If you do not, replicas that have not been updated cannot import synchronization update packets from the updated replica. - Replica incarnation is old
Differences in the replica incarnation can prevent syncreplica –import command at the importing replica from completing its operation properly. - Warning on receipt of packet from earlier MultiSite version
Different versions of MultiSite have different packet protocols. When multitool with a newer protocol reads a packet with the older protocol, it prints a warning message. - Miscellaneous problems
There are simple problems (disk space, locked replicas, licensing, multiple processes running) that can cause a packet import to fail. - Recovering from lost packets
There are several circumstances in which a replica-creation or update packet is generated but is never applied at one or more of its destinations. - Inconsistent changes to replica
A recoverable error occurs if syncreplica –import detects that an incoming change is inconsistent with another change that has already been applied to the replica. - Automatic renaming of type objects and replica objects
The syncreplica –import command resolves naming conflicts among type objects or replica objects created at two or more replicas.
Parent topic: Troubleshooting MultiSite operations