Using check subscription

If all of the servers and Replication Server threads are running, but the subscription is not being created or dropped, use the check subscription command, which returns messages that describe the status of the materialization process.

Execute the check subscription at the primary and replicate Replication Servers. If the primary and replicate Replication Servers are the same Replication Server, you need to execute check subscription only once; check subscription displays separate status messages.

Use check subscription for publication to find out the materialization status of publication subscriptions. For atomic, nonatomic, or incremental publication subscriptions, check subscription for publication shows the status of only the current article subscription being processed; whereas for bulk or no materialization, the status of all article subscriptions is shown because all article subscriptions are processed together.

Table 5-1 and Table 5-2 list the messages that can be returned by executing check subscription at the primary and replicate Replication Servers.

**Table 5-1: check subscription status at replicate Replication Server**
Status	Message
Invalid	<subscription name> doesn’t exist.
Removing	REMOVING subscription <subscription name> from system tables at the Replicate.
Dematerializing	Subscription <subscription name> is DEMATERIALIZING at the Replicate.
Valid	Subscription <subscription name> is VALID at the Replicate.
Validating	Subscription <subscription name> is VALIDATING at the Replicate.
Materialized	Subscription <subscription name> has been MATERIALIZED at the Replicate.
Active	Subscription <subscription name> is ACTIVE at the Replicate.
Activating	Subscription <subscription name> is ACTIVATING at the Replicate.
Qcomplete and Active	Subscription <subscription name> is ACTIVE at the Replicate and Materialization Queue has been completed.
Qcomplete	Materialization Queue for Subscription <subscription name> has been completed.
Active and Qcomplete	Subscription <subscription name> is ACTIVE at the Replicate, but Materialization Queue for it has not been completed.
Defined	Subscription <subscription name> has been defined at the Replicate.
Error	Subscription <subscription name> has experienced an unrecoverable error during Materialization or Dematerialization. Please consult the error log for more details.
Pending	Other subscriptions are being created or dropped for the same replication definition/database. Subscription <subscription name> will be processed when previous requests are completed.
Recovering	Subscription <subscription name> has experienced a recoverable error during Materialization or Dematerialization. It will be recovered by Subscription Daemon (dSub).

**Table 5-2: check subscription status at primary Replication Server**
Status	Message
Invalid	<subscription name> doesn’t exist.
Dematerializing	Subscription <subscription name> is DEMATERIALIZING at the Primary.
Valid	Subscription <subscription name> is VALID at the PRIMARY.
Active	Subscription <subscription name> is ACTIVE at the PRIMARY.
Activating	Subscription <subscription name> is ACTIVATING at the PRIMARY.
Defined	Subscription <subscription name> has been defined at the PRIMARY.