The following considerations apply to deploying replication configurations:
For a full deployment, you do not need to stop replication tasks in either the original or destination environment before performing the full deployment.
If you perform a full deployment of a configuration with an Oracle source that includes tablespaces or columns that are encrypted with Oracle TDE, the Oracle wallet password and internal master key IDs are not deployed from the original configuration. After deployment, if you open the Oracle wallet and generate new internal master keys for the new configuration in the destination environment, Data Replication will retain these keys during future partial deployments of the configuration changes.
To update a deployed configuration later, use one of the following strategies:
Update the configuration directly in the destination environment.
Update the configuration in the original environment and then use the
Partial deploy
option to deploy only the configuration changes to the destination environment. When you perform a partial deployment of configuration changes, stop all of the replication tasks that use the configuration, deploy the configuration changes, and then start the replication tasks again.
Use the same update strategy for all subsequent updates of the configuration.
Data Replication deploys only the replication settings of a configuration and not any of the internal Data Replication processing information for the configuration, which should not be modified. Depending on the deployment type, Data Replication handles the internal processing information in one of the following ways:
For an initial full deployment of a configuration, Data Replication creates a copy of the configuration in the destination environment. This copy does not contain the internal information that the replication tasks added to the configuration in the original environment. You can use the new configuration to start replication in the destination environment.
For a partial deployment of configuration changes, Data Replication does not modify the internal information that the replication tasks previously added to the configuration in the destination environment. You can resume all of the replication jobs with the updated configuration in the destination environment.