These
checks are made before extracting transfer packages:
- Database parameters must be in DCM databases. DCM
verifies that critical parameters are consistent between the source
and destination databases. If DCM discovers an inconsistency, the
check fails.
- The source and destination databases must use the
same DCM delimiter. Otherwise, transfer packages generated from the
source database is not recognized by the destination database. The
DCM manager must ensure that the same delimiter is used throughout
the DCM cluster.
- The source and destination databases must use the
same release delimiter.
- Compatible versions of Rational® Synergy must be used by the source
and destination databases. If this check fails, DCM displays an error
message that lists the acceptable versions.
Note: If this check fails, and you are receiving
a package generated from a newer release than the one you have, install
a patch that allows the package to be received. In any event, contact Rational Synergy Support for
assistance. Otherwise, crucial data conversions cannot be performed.
- Case settings of the source and destination databases
must be compatible. A transfer package from a database set to use
Lower Case can be received into a database set to Preserve Case. However,
a transfer package from a database set to Preserve Case is incompatible
with a database set to use Lower Case if any of the object names contain
uppercase characters.
Note: An incompatibility message
can be ignored if the transfer package contains
only lower
case filenames.
- The version delimiters of the source and destination
databases must be identical. If they are not the same, the transfer
package can contain objects whose names have the version delimiter
of the destination database. Such objects are not accessible to users.
Note: If this error message is received, proceed
only if you are sure that users can access the objects.