Dematerialization Problems

Fix dematerialization problems based on the status returned by check subscription.

Check the error logs for all of the servers involved for specific information. Also check that the user who is dropping the subscription has the same login name and password at the replicate and primary Replication Servers, and, if you used the with purge option, that the maintenance user for the replicate database has select, delete, and update permissions on the replicate table.

Dematerialization Problems—with purge Option
Status at Replicate Replication Server	Status at Primary Replication Server	Subscription State	Suggested Actions
Dematerializing/ Pending	N/A	Waiting for other subscriptions for the same replication definition and replicate database.	Look for other subscriptions being created or dropped for the same replication definition and database. If no other subscription operations are in process, wait for five minutes.
Dematerializing/ Recovering	N/A	Cannot connect to the primary Replication Server to drop the subscription.	Check replicate Replication Server error log for messages. If the user dropping the subscription does not have the same login and password at the primary and replicate Replication Servers, then: Provide the user with a Replication Server account that has the same login and password at the primary and replicate, or Have a different user with the appropriate permissions drop the subscription. Also, the user must have at least primary subscribe privileges at the primary Replication Server.
Dematerializing	N/A	The primary Replication Server is waiting for the drop request.	Investigate whether the primary Replication Server is out of queue segments. Verify that the primary Replication Server is running and that the Stable Queue Manager (SQM), Stable Queue Transaction (SQT), and Distributor (DIST) threads for the primary database are running.
Dematerializing	Dematerializing	The primary Replication Server processed the drop request and sent it to the replicate Replication Server. The replicate Replication Server is waiting for the drop request.	Check the route between the primary Replication Server and the replicate Replication Server. Check the Data Server Interface (DSI) thread for the replicate database. Investigate whether the replicate Replication Server has run out of queue segments.
Dematerializing/ Recovering	Dematerializing	The primary Replication Server processed the drop request and sent it to the replicate Replication Server. The replicate Replication Server failed to create and process the dematerialization queue.	Investigate whether the replicate Replication Server has run out of queue segments. Verify that the maintenance user has select privileges on the replicate table. Check the DSI thread for the replicate database.
Removing/ Recovering	Dematerializing	The subscription has dematerialized at the replicate Replication Server, but the replicate Replication Server could not log in to primary Replication Server to remove the subscription from the system tables.	Verify that the primary Replication Server is running. If the user dropping the subscription does not have the same login and password at the primary and replicate Replication Servers, then: Provide the user with a Replication Server account that has the same login and password at the primary and replicate, or Have a different user with the appropriate permissions drop the subscription.
Removing	Dematerializing	The primary Replication Server is deleting the subscription. The replicate Replication Server is waiting for the primary Replication Server to finish.	Wait.
Removing	Invalid	The subscription has been removed from the primary Replication Server. The replicate Replication Server will remove the subscription next.	Wait.
Invalid	Invalid	The subscription has been dropped.	None.

Dematerialization Problems—without purge Option
Replicate Status	Primary Status	Subscription State	Suggested Actions
Dematerializing/ Pending	N/A	Waiting for other subscription requests for the same replication definition and replicate database.	Check for other subscription being created or dropped for the same replication definition and database. If there are no other subscriptions, wait for five minutes.
Dematerializing/ Recovering	N/A	Cannot connect to the primary Replication Server to drop the subscription.	Check the replicate Replication Server error log for messages. Make sure the user who created the subscription has the same login name and password at the primary Replication Server and the replicate Replication Server. The user should also have at least primary subscribe privileges.
Dematerializing	N/A	The primary Replication Server is waiting for the drop request.	Determine whether the primary Replication Server has run out of queue segments. Verify that the primary Replication Server is up and that the SQM, SQT, and DIST threads for the primary database are running.
Dematerializing	Dematerializing	The primary Replication Server processed the drop request and sent it to the replicate Replication Server. The replicate Replication Server is waiting for the drop request.	Check the route between the primary Replication Server and the replicate Replication Server. Check the DSI thread for the replicate database. Determine whether the replicate Replication Server ran out of queue segments.
Dematerializing/ Recovering	Dematerializing	The primary Replication Server processed the drop request and returned it to the replicate Replication Server. The replicate Replication Server terminated abnormally.	Wait for the subscription daemon to reset the recovering flag.
Removing/ Recovering	Dematerializing	The replicate Replication Server could not log in to the primary Replication Server to delete the subscription from the system tables.	Verify that the primary Replication Server is running.
Removing	Dematerializing	The primary Replication Server is deleting the subscription from the system tables. The replicate Replication Server is waiting for the primary Replication Server to finish.	Wait.
Removing	Invalid	The subscription is removed from the primary Replication Server. The replicate Replication Server will remove the subscription next.	Wait.
Invalid	Invalid	The subscription has been dropped.	None.