Subscription Problems

Subscription problems occur when subscription materialization or dematerialization fails.

The replication process begins with subscription materialization, which is the process by which data is initially copied to the destination database. When you no longer want a subscription replicated to a destination database, dematerialize the subscription at the destination database. Dematerialization is the process by which data is deleted from the destination database.

Note: If you are using a Replication Agent, your subscription materialization process may differ from the process described here. See your Replication Agent documentation for the Replication Agent-specific subscription materialization process.

Subscription problem symptoms are easily identified and include:

Materialization failure – no data in the subscription’s replicate table at the destination database, invalid status for subscriptions at the primary and replicate Replication Servers, or materialization has been taking longer than is reasonable.
Dematerialization failure – data still exists in the subscription’s replicate table at the destination database, the status for subscriptions at the primary and replicate Replication Servers is invalid, or dematerialization has been taking longer than is reasonable.

Usually, the person who is conducting the materialization or dematerialization monitors the operation and reports any problems.

Some subscription problem symptoms are reported as error messages in the Replication Server error log. You might also need to use the diagnostic tools to identify subscription problem symptoms.

If a subscription problem caused the Data Server Interface (DSI) thread for the replicate database to abnormally terminate, restart it using the resume connection command.