Atomic Materialization Problems

Defined/ Pending

Invalid

Waiting for other subscriptions for the same replication definition and replicate database to be processed.

Check for other subscriptions being created and dropped for the same replication definition and replicate database.

If there are no other subscriptions, wait five minutes.

Defined/ Recovering

Invalid

Cannot connect to the primary Replication Server to define the subscription.

Check the replicate Replication Server error log for messages.

Make sure the user creating the subscription has the same login name and password at the primary Replication Server and the replicate Replication Server. Make sure the user has at least primary subscribe permission at the primary Replication Server.

Defined/ Recovering

Defined

Cannot build the materialization queue.

Verify that the primary data server is running.

Make sure the user creating the subscription has the same login name and password at the primary data server and replicate Replication Server, select permission on the primary table, and execute permission for rs_marker.

Use admin disk_space to investigate whether the replicate Replication Server is out of stable queue segments.

Use admin who, dsi and admin who, sqm to monitor the queues.

Defined

Defined

Building materialization queue.

Building the queue may take some time. Wait until this process is complete.

Use admin who, sqm to monitor materialization.

Use admin disk_space to investigate whether the primary Replication Server is out of stable queue segments.

Check if rows are being selected using a holdlock at the primary database.

Qcomplete

Defined

Waiting for the activation request to get to the primary Replication Server.

Materialization queue has been built.

Verify that the RepAgent for the primary database is running.

Investigate whether the primary Replication Server is out of stable queue segments.

Qcomplete/ Recovering

Defined/ Valid

The replicate Replication Server stopped after the materialization queue was completed.

Wait. The status should return to Qcomplete at the replicate Replication Server.

Qcomplete

Activating

The activation request is being processed at the primary Replication Server.

Wait. The status at the primary Replication Server should change to valid.

Qcomplete

Valid

The subscription is complete at the primary Replication Server.

Waiting for activation request or applying the materialization queue at the replicate Replication Server.

Check the route between the primary and the replicate Replication Server.

Check the replicate Replication Server Data Server Interface (DSI) thread for the replicate database.

Investigate whether the replicate Replication Server ran out of queue segments.

Use admin who, dsi and admin who, sqm to monitor the queues. If admin who, dsi shows that the DSI is processing the materialization queue, wait until the queue has been processed. The length of the wait depends upon the size of the queue.

Valid

Valid

Complete.

None.