check publication

Finds the status of a publication and the number of articles the publication contains.

Syntax

check publication pub_name
   with primary at data_server.database

Parameters

pub_name – The name of the publication to check.
with primary at data_server.database – Specifies the location of the primary data. If the primary database is part of a warm standby application, data_server.database is the name of the logical data server and database.

Examples

Example 1 – Checks the status of the publication pubs2_pub, where the primary database is TOKYO_DS.pubs2:
```
check publication pubs2_pub
 with primary at TOKYO_DS.pubs2
```

Usage

Use check publication to find the status of a publication and the number of articles the publication contains.

See the Replication Server Administration Guide Volume 1 for more information about publications.
Execute check publication at the Replication Server that manages the replicate database or at the Replication Server that manages the primary database.
If you execute check publication at the replicate Replication Server, the publication is checked at the primary Replication Server using the current user name and password. You must have the same login name and password at the primary Replication Server to display current information about the publication.
To check subscription status, use check subscription. See check subscription command for more information.

Messages Returned by check publication

When you execute check publication at a primary or replicate Replication Server, it returns one of these messages:

Publication pub_name for primary database
data_server.database is valid. The number of
articles in the publication is number_articles.
Publication pub_name for primary database
data_server.database is invalid. The number of
articles in the publication is number_articles.

When you execute check publication at a replicate Replication Server, it returns this message if it cannot contact the primary Replication Server:
```
Failed to get publication information from primary.
```

Permissions

Any user may execute this command. A user who enters this command at a replicate Replication Server must have the same login name and password in the primary Replication Server.