Replicating the information helps to automate the steps in setting up DCM database definitions. Replication also helps to make details such as description, location, and administrative information consistently available across the cluster.
Not all of the information in a DCM database definition is replicated. Transfer modes, paths, automatic receive settings, and so on, might be different for the same database definition in different databases. For example, consider a cluster consisting of databases NY1 and NY2 in New York, and databases LO1 and LO2 in London. The DCM database definition for NY2 might use direct transfer mode from NY1, but ftp from LO1 and LO2.
If the DCM database ID of a database is changed, the change is not automatically replicated. You must notify the DCM administrators of all other databases for the changed identifier to update the corresponding DCM database definition in each database.