You can mark a database definition as up-to-date for a specified transfer set. When you create a database by unpacking a copy of the current database and changing its database identifier, it contains all the objects that existed when the database was backed up. Use this feature to stop objects from being sent unnecessarily to an existing database during replication.
Before you begin
The current database must be initialized to use DCM.
You must have the dcm_mgr or ccm_admin role available to use this feature.
About this task
ccm dcm -mark_up_to_date -dbid|-database_id database_spec
-ts|-transfer_set transfer_set_spec [-force] [date]
- -database_id database_spec
- Specifies to generate the destination database for the transfer package. The database_spec must specify a single database definition. See Database specification for details.
- date
- Specifies the date that the database is up-to-date. By default, Synergy uses the current date and time. If you created a database by unpacking a backup of another database, use the date and time of the backup as the date for this command. Any changes made after that data no longer exist in the copied database.
- -force
- Specifies for the operation to succeed even if the specified transfer set and destination database have generated previous packages. By default, the operation succeeds only if a DCM generate operation was not performed for the transfer set and destination database.
- -ts|-transfer_set transfer_set_spec
- Specifies the transfer set to mark as up-to-date for the specified destination database. Set the transfer_set_spec to a single transfer set. For details, see Transfer set specification.