Show TOC

validate subscriptionLocate this document in the navigation structure

For a subscription to a replication definition or a publication, sets the subscription status to VALID.

This command is part of the bulk materialization process, or part of the process of refreshing a publication subscription.
Note If you activate a subscription with the catchup_queue option, the subscription becomes VALID only after all the DML operations in the catchup queue are applied at the replicate table.
Syntax
validate subscription <sub_name
>for {<table_rep_def> | <function_rep_def> |
      publication <pub_name> 
      with primary at <data_server.database>}
with replicate at <data_server.database>
Parameters
sub_name

The name of the subscription to be validated.

for table_rep_def

Specifies the name of the table replication definition the subscription is for.

for function_rep_def

Specifies the name of the function replication definition the subscription is for.

for publication pub_name

Specifies the name of the publication the subscription is for.

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. Include this clause only for a subscription for a publication.

with replicate at data_server.database

Specifies the location of the replicate data. If the replicate database is part of a warm standby application, <data_server.database> is the name of the logical data server and database.

Examples
Example 1

Validates the subscription <titles_sub> for the table replication definition <titles_rep>, where the replicate database is SYDNEY_DS.<pubs2>:

validate subscription titles_sub
 for titles_rep
 with replicate at SYDNEY_DS.pubs2
Example 2

Validates the subscription <myproc_sub> for the function replication definition <myproc_rep>, where the replicate database is SYDNEY_DS.<pubs2>:

validate subscription myproc_sub
 for myproc_rep
 with replicate at SYDNEY_DS.pubs2
Example 3

Validates the subscription <pubs2_sub> for the publication <pubs2_pub>, where the primary database is TOKYO_DS.<pubs2> and the replicate database is SYDNEY_DS.<pubs2>:

validate subscription pubs2_sub
 for publication pubs2_pub
 with primary at TOKYO_DS.pubs2
 with replicate at SYDNEY_DS.pubs2
Usage
  • Use validate subscription to validate a subscription at the primary and replicate Replication Servers. The subscription can be to a table replication definition, function definition replication, or publication.

  • This command completes the bulk materialization process. The first step is creating the subscription using define subscription. The second step is activating the subscription using activate subscription.

  • If you have added any new articles to a publication with an existing subscription, you must refresh the publication subscription in order to create new subscriptions for these articles.

    Use define subscription and activate subscription to create and activate the new article subscriptions in the publication subscription. Then manually load the subscription data for the new article subscriptions, and use validate subscription to validate the publication subscription.

  • Execute validate subscription at the Replication Server where you created the subscription using define subscription.

  • When you validate a publication subscription, all of its article subscriptions are validated at the same time.

  • validate subscription changes the status of a subscription from ACTIVE to VALID. Subsequent updates at the primary data server are distributed through the primary Replication Server and applied at the replicate Replication Server.

  • This command modifies RSSD tables at multiple sites. Use check subscription at both the primary and replicate Replication Servers to see the effects on each.

See the Replication Server Administration Guide Volume 1 and Volume 2 for more information about subscription materialization.

Permissions

validate subscription requires “create object” permission at the site where the data is replicated and “primary subscribe” or “create object” permission at the site where the primary data is stored.