About initializing a database for DCM use

A database is usable by DCM after it is initialized for DCM use. DCM initialization requires exclusive access to the database.

During DCM initialization, users are excluded from performing operations in the database. Establish a good time to exclude users from the database. The longer a database has been in use, the longer DCM initialization takes.

Choose a DCM database identifier that is unique in the DCM cluster. A DCM requirement is that the database has common database properties and common database parameters with other databases in the cluster. See Establish common database properties and Establish common database parameters for details.

In the database that you are initializing, define the release value and DCM transfers. If you are initializing more than one database, do not define these releases in the other databases.

In the database that you are initializing, ensure that a released baseline has been created for the current release and includes the current project. For example, with a current release of hello/1.0, be sure that it includes all relevant projects.

In the database that you are initializing, copy the previous release to the new release, selecting the Distributed process for the new release. Ensure that the new release can transfer DCM objects. If the new release was defined before the database was DCM initialized, show the properties of the new release in the Properties dialog box. On the Process Rules tab, click Add to add the generic process rules from the Distributed process.

After the database is initialized for use with DCM, you can create destination database definitions and transfer sets. You can also use the database for DCM transfers.


Feedback