Object name conflicts

Each object in a DCM cluster has a unique cluster ID attribute. If an object in a DCM transfer package has the same four-part object name as an object in the receiving database, but has a different cluster ID value, it is reported as an object name conflict.

In effect, there are two objects with the same object name that could be unrelated to each other.

An object name conflict can arise for several conditions.

  1. An object is created in a source database and sent to a destination database. It is deleted from the source database. Later, another object is created in the source database that has the same four-part object name and then sent to the destination database. The commonly occurs with projects in prep state.
  2. An object is created in a source database and sent to a destination database. The source database is restored from a backup that was taken before that object existed. Later, another object is created in the source database that has the same four-part object name and then sent to the destination database.
  3. An object is created in a source database and sent to a destination database. The object is renamed in the source database and a new object is created having the former four-part object name of the object. The new object is replicated without the renamed former object to the database. DCM automatically renames objects but only if the renamed object is replicated to the destination database.

Feedback