Content class collisions

Each content class you create in an HCP system has an internal ID that uniquely identifies that content class. As a result, two content classes created on different HCP systems are different from each other, even if they have the same name and are defined for the same tenant.

A content class collision occurs when the Replication service tries to replicate a content class from one system to another system that already has a different content class with the same name, where both content classes are defined for the same tenant.

To recover from a content class collision, take one of these actions:

  • Rename the content class on either of the systems involved in the link.
  • Delete the content class on either of the systems involved in the link.

Here’s a scenario that shows how a content class collision can cause the Replication service to pause replication of a tenant. In this scenario:

  • System A and system B replicate to each other over active/active link AB.
  • Link AB includes tenant T1, so T1 exists on both systems.

These events occur in the order shown:

  1. On system A, you create a content class named CC1 for T1.
  2. Before CC1 is replicated to system B, you create a content class named CC1 for T1 on system B.
  3. The Replication service tries to replicate CC1 to system B. The replication is unsuccessful because a different content class named CC1 already exists on system B. As a result, the service automatically pauses replication of T1 on link AB.