Changes to activate subscription

The activate subscription syntax has been modified and a new parameter is added.

activate subscription sub_name
for {table_rep_def | function_rep_def |
   publication pub_name 
   with primary at data_server.database}
   with replicate at data_server.database
   [with suspension [at active replicate only] | with catchup_queue]
Replication Server 15.7.1 SP200 adds the with catchup_queue parameter. Use the with catchup_queue clause to instruct Replication Server to start a catchup queue to store the DMLs for the primary table. Subsequent updates to the primary table are stored in a catchup queue. After the bulk materialization is complete and when you issue the validate subscription command, the subscription becomes VALID after all the DML operations in the catchup queue are applied to the replicate table. This eliminates the need to suspend replicate DSI or restrict DMLs at the primary table when bulk materialization is in progress.
See: