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 will already contain 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 be working as the DCM manager or administrator 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. You can set the database_spec to 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 a database was created
by unpacking a backup of another database, you can use the date and
time of the backup as the date for this command. Any changes made
after that data will not exist in the copied database.
- -force
- Specifies that the operation will succeed even if the specified
transfer set and destination database have generated previous packages.
By default, the operation will succeed only if the transfer set and
destination database have never generated a transfer package.
- -ts|-transfer_set transfer_set_spec
- Specifies the transfer set to mark as up-to-date for the specified
destination database. You can set the transfer_set_spec to
a single transfer set. For details, see Transfer set
specification.