Establish disk space requirements
Whenever data is sent and received, DCM writes to the file systems of the source and destination databases. Thus, these file systems must have plenty of free space before transfer packages can be generated, transferred, and received.
DCM planning worksheet
Before sending and receiving data, use the DCM planning
worksheet to estimate how much free disk space is needed in the generate and receive directories.
These directories are typically located at the source and destination
databases.
Establish common database parameters
Before using DCM, be sure that source and destination projects
have the same update properties. If they do not, transferred objects
might not be correctly configured into projects in the destination
databases.
Establish common database properties
By design, all databases in a DCM cluster must have: unique
database IDs, identical DCM delimiters, and compatible models.
Synchronize engines and servers
The times on the engine and server machines must be synchronized.
By default, DCM allows machines accessing the same database to have
time discrepancies of up to 60 seconds. If a machine has a time difference
that is greater than 60 seconds with another machine, the object might
not be included in DCM transfer packages.