Performing Nonatomic Bulk Materialization

Perform nonatomic bulk materialization.

1. Log in to the replicate Replication Server as the system administrator (sa):

   isql -Usa -Psa_password -SRRS_servername

   where:

   • sa is the system administrator user ID.

   • sa_password is the password for the system administrator user ID.

   • RRS_servername is the name of the replicate Replication Server.

2. At the replicate Replication Server, turn on the autocorrection feature:

   1> set autocorrection on
   2> for replication_definition
   3> with replicate at dataserver.database
   4> go

3. At the replicate Replication Server, define the subscription:

   1> define subscription subscription_name
   2> for replication_definition
   3> with replicate at dataserver.database
   4> with suspension
   5> go 

   The dataserver.database name must match the name you used for your replicate database.

4. In the primary database, invoke rs_marker to activate the subscription.
5. Check the subscription at both the primary and replicate Replication Servers. Use this command to verify that the subscription status is ACTIVE:

   1> check subscription subscription_name
   2> for replication_definition
   3> with replicate at dataserver.database
   4> go 

   When the subscription status is ACTIVE at the replicate Replication Server, the database connection for the replicate database is suspended.

6. Unload the subscription data at the primary site using the preferred database unload method for your site to select or dump the data from the primary tables.
   Note: When unloading subscription data from the primary table, make sure you select only the columns specified in the replication definition and the rows specified in the subscription.
7. In the primary database, invoke rs_marker to validate the subscription.
8. Wait for the subscription to become valid at both the primary and replicate Replication Servers, then execute check subscription at both the primary and replicate Replication Servers to verify that the status is VALID.
9. Load the subscription data into the replicate database using bcp or the preferred database load utility for your site.
   
   Note: Before loading the subscription data into the replicate table, make sure that any data manipulation that is to be performed by Replication Agent (such as datetime conversion) or by Replication Server function strings is applied to the unload file.
10. From the replicate Replication Server, resume the database connection for the replicate database:

    1> resume connection
    2> to dataserver.database
    3> go

11. Wait for the subscription to become valid at both the primary and replicate Replication Servers, then execute check subscription at both the primary and replicate Replication Servers to verify that the status is VALID.

    When the subscription status is VALID at the replicate Replication Server, the replicate database is synchronized with the primary database and you can turn off autocorrection.

12. Turn off the autocorrection feature at the replicate Replication Server:

    1> set autocorrection off
    2> for replication_definition
    3> with replicate at dataserver.database
    4> go

    When you complete this procedure, the subscription is created, the replicate data is consistent with the primary data, and replication is in progress.

    See the Replication Server Commands Reference for information about Replication Command Language (RCL) commands. See the Replication Server Administration Guide for information about configuring Replication Servers and materialization methods.