By design, all databases in a DCM cluster must have: unique database IDs, identical DCM delimiters, and compatible models.
- Unique database IDs
- Each DCM database must be manually given a unique database ID (dbid). The ID is set when the database is initialized to use DCM. The database ID is case sensitive and is a logical identifier for the database. It can be the same as the name of the database, but it does not have to be.
- Identical DCM delimiters
- The DCM delimiter is used in the names of all non-local objects in a DCM database. Each database in a DCM cluster must be given the same delimiter so that object naming is consistent. The delimiter is set when the database is initialized to use DCM. However, the delimiter can be changed.
- Compatible database case settings
- Case settings of the source and destination databases must be compatible.
- Identical release delimiters
- For consistent processing of release definitions and operations related to releases, the release delimiter must be identical across all databases in a DCM cluster.
- Compatible models
- The life cycles and types of all shared objects must be compatible across all databases in a DCM cluster. Also, to ensure compatibility during a receive operation, DCM automatically creates any user-defined type definitions that are not already defined in the destination database.