The ccm export command exports
specified objects to a package that might be later imported into the
same or another Rational® Synergy
database at the same release and patch level. The format of the packages
that is produced by the ccm export command is implementation
private and only intended for use with the ccm import command.
Export and import restrictions
Using
the ccm export command to export data from one database
and the ccm import command to import that data into
another database is subject to the following restrictions.
CAUTION:
Any use outside of these restrictions is not supported.
If you choose to work in an unsupported mode, loss of data or data
inconsistencies in the database into which the data is imported might
occur.
- The exporting database and importing database must be at the same Rational Synergy release, iFix,
and patch level.
- If the exporting database is DCM initialized, the importing database
must also be DCM initialized.
- If the exporting database is not DCM initialized, the importing
database must also not be DCM initialized.
- The importing database must have type definitions for each object
that is to be imported into the database.
- If the user is in the ccm_admin role, the import
might overwrite and update existing objects, including objects in
static states. The use of ccm export and ccm
import is not intended as a replacement for DCM. If you are
trying to implement replication of data between Rational Synergy databases, use DCM.
- The use of import or export to copy model, cvtype, attype, admin,
or other similar types of objects that make up the Rational Synergy model is not supported.
Incorrect usage in the ccm_admin role can make the
importing database unusable.
The export command supports the following
subcommand: