After the subscription is activated, complete bulk materialization by using validate subscription at the replicate Replication Server. The subscription status is changed to Validating. The replicate Replication Server forwards the validation request to the primary Replication Server.
When the primary Replication Server receives the validation request, it changes the status at the primary to Valid and returns the validation request to the replicate Replication Server. When the replicate Replication Server receives the validation request, the subscription status becomes Valid at both sites, and the bulk materialization is complete.
Table 5-7 describes solutions for bulk materialization problems that occur during the validation phase based on the status returned by check subscription. The Replicate Status column shows the subscription status returned by check subscription at the replicate Replication Server. The Primary Status column shows the subscription status returned by check subscription at the primary Replication Server. The Subscription State column provides a detailed description of the subscription status. The Suggested Actions column provides the solutions.
Replicate Status |
Primary Status |
Subscription State |
Suggested Actions |
|---|---|---|---|
Validating/ Recovering |
Active |
Cannot send the validation request to the primary Replication Server. |
Verify that the primary Replication Server is running. |
Validating |
Valid |
The primary Replication Server received the validation request. The replicate Replication Server is waiting for the validation request. |
Verify the route between the primary and replicate Replication Server. Verify the DSI is running. Verify that the replicate Replication Server has sufficient queue segments. |
Valid |
Valid |
Complete. |
None. |
