Troubleshooting Dematerialization Failures

Troubleshoot subscriptions that have not dematerialized.

Prerequisites
Verify that data has failed to dematerialize by logging to the replicate database using isql and executing a select command that selects the dematerialized columns from the replicate table.
Task
  1. Log in to the destination Replication Server and issue check subscription, which returns information that diagnoses the problem, including:

    • Other subscriptions to the same replication definition and replicate database have not yet processed

    • No connection to the primary Replication Server because of an incorrect login

    • Primary Replication Server down or out of stable queues

    • Stable Queue Manager (SQM), Stable Queue Transaction interface (SQT), and Distributor (DIST) threads down

    • Primary data server down, incorrect login, out of stable queues, or rows selected with holdlock

    • RepAgent problem

    • Route problem

    • Destination Replication Server DSI problem

    • Incorrect user privileges on destination database

  2. Log in to the primary Replication Server and also check its subscription status using check subscription.
  3. If some columns are not being dematerialized:
    1. Check replication status of text, unitext, and image columns.
    2. Verify that the replication definition is correctly defined.
  4. Fix the problem.
  5. Run the replication system when you think you have solved the problem.

    If the subscription is still not dematerialized, analyze the error log again or complete any of the steps you have skipped.

Parent topic: Troubleshooting Overview