Promoting selected rule sets to a new subscription

You can use a wizard to promote your selected rule sets to a new subscription in a new environment.

About this task

For example, you may have projects that are exclusive for development or testing purposes. You can promote subscriptions into one of these environments.

1. Click Configuration > Subscriptions.
2. Select the subscription with the rule sets you want to promote.
3. Click Rules in the Table Mappings view.
4. Select one or more rule sets.
5. Right-click and select Promote....
6. Select Promote to a new subscription.
7. Enter the name of the new subscription in the Name box.

   All subscriptions that come from the same source datastore must have a unique name and all subscriptions that go to the same target datastore must have a unique Source ID. The source ID is automatically generated based on truncating the subscription name to 8 characters. If you attempt to create a subscription with a duplicate Source ID, an error will result and the subscription will not be created. If this occurs, click Advanced Settings and give the subscription a unique Source ID.

8. Enter the description of the new subscription in the Description box.
9. If you want to include the new subscription in a project, select a project from the Project list or click New Project to create a new project.

   If you do not select a project, Management Console places the new subscription into the Default Project.

10. Click Next.
11. Select the name of the new source datastore from the New Source Datastore list.
12. Select the name of the database and owner from the New Name list.
13. If you want to specify advanced settings for the subscription, click Advanced Settings. Modify the following properties and click OK, then click OK again.

    On the General tab, the following properties can be set:

    Source ID

    Specify the source ID for the new subscription.

    TCP Host

    Specify the TCP host that your source datastore will use to recognize the target datastore when the computer where CDC Replication is installed has multiple network cards. This is useful if you want to specify a host that is different from the host that you specified in the Access Manager perspective. The default option is Auto-select, which will automatically select the network card that can communicate with the target datastore. The host that you specified in the Access Manager perspective also appears by default as well as any alias that you configured in the Datastore Properties dialog box.

    Firewall Port

    Specify a port number for the new subscription.

    Mark subscription as persistent

    Enable if you want to specify that the subscription is persistent. This feature is only enabled for subscriptions whose datastores support the functionality. A persistent subscription restarts automatically after a recoverable error occurs. By default, a persistent subscription restarts only after a recoverable error when the instance is restarted. To allow a persistent subscription to restart after a subscription stops without the instance stopping and restarting, set the system property mirror_auto_restart_interval_seconds to a non-zero value. See the documentation for this parameter under the "System parameters" > "General product system parameters" section for your CDC Replication engine.

    Select the datastore to handle the transferable work

    Specify where transferable work will be performed, in order to minimize impact on the source or target datastore.

    Minimize network load

    Specify whether to minimize the network load where possible, even if it may result in increased replication latency. This option is only available when both the source and target datastores support the functionality.

    On the Propagation Control tab, the following properties can be set:

    Propagation Control

    Click Add and select the source ID for any subscription for which you want to prevent data from being replicated to the target.

    On the Communication Protocol tab, you can specify the communications protocol that will be used by the source datastore to communicate with the target datastore

    Do not replicate data received from any subscriptions

    Enable if you want to prevent replication from all subscriptions.

    TCP/IP

    Specifies that TCP/IP will be used exclusively as the communication protocol.

    JMS

    Specifies that either TCP/IP or JMS message queues will be used as the communication protocol.

14. Select the name of the new target datastore from the New Target Datastore list.

    Note that subscriptions with rule-based table mappings can not be promoted when the source and target datastores are identical.

15. Review the list of changes and click Finish.