check subscription Command

Use check subscription to report the status of a subscription at the Replication Server where you enter the command

The subscription status at the primary and replicate Replication Servers often differs while the subscription is being created, so you should enter check subscription at both sites. If the primary and replicate databases are managed by a single Replication Server, check subscription displays the status of the subscription for both the primary and replicate databases.

The syntax is:

check subscription subscription
for { table_rep_def | function_rep_def | publication pub_name |
	database replication definition db_repdef
	with primary at data_server.db }
with replicate at data_server.db

where subscription is the name of the subscription to check, table_rep_def is the name of the table replication definition the subscription is for, function_rep_def is the name of the function replication definition the subscription is for, pub_name is the publication the subscription is for, db_repdef is the database replication definition the subscription is for, and data_server.db identifies the primary or replicate database.

The message returned by the command contains subscription status information. If the subscription had an error, the message directs you to the log where you should look for specific error messages.

See Replication Server Reference Manual > Replication Server Commands > check subscription for a list of the messages check subscription can return.

Direct Load Materialization Progress

The check subscription command reports progress information for subscriptions created with the direct_load option that are in either the:

initial-load phase – the period of time Replication Server consumes when it selects rowsfrom the primary database and applies the selected rows to the replicate database
catchup-up phase – the period of time between the end of the initial load and when the subscription changes to the VALID state

In the initial-load phase for a subscription named my_sub, the check subscription command reports status similar to:

Subscription my_sub is ACTIVE at the replicate. 
Subscription my_sub is ACTIVE at the primary. 
Subscriptions my_sub progress: initial loading, xx% done, xxxxx commands remaining.

In the catch-load phase for a subscription named my_sub, the check subscription command reports status similar to:

Subscription my_sub has been MATERIALIZED at the replicate. 
Subscription my_sub is VALID at the primary. 
Subscriptions my_sub progress: catchup, xx% done, xxxxx commands remaining.