Use this procedure to set up direct load materialization and enable replication from an Adaptive Server primary to an Adaptive Server replicate.
create subscription subscription_name for replication_definition with replicate at dataserver.database [where search_conditions] without holdlock direct_load [user cusername password cpass] go
The dataserver.database must match the Replication Server connection name you use for the replicate database. If you specify cusername here, this name is used to log in to the primary database and select from the primary table. If you do not specify cusername here, iuser—the name specified in isql—is used. Make sure that the name used to log in to the primary database has necessary permission at the primary database.
check subscription subscription_name for repdef_name with replicate at replicate_dataserver.replicate_database go
When materialization is complete, Replication Server returns a message similar to:
Subscription subscription_name has been MATERIALIZED at the replicate.
When the subscription process is complete, Replication Server returns a message similar to:
Subscription subscription_name is VALID at the replicate.
Subscription subscription_name encountered ERROR.When a subscription encounters an error, look at the replicate and primary Replication Server log files to diagnose the cause, drop the subscription without purge, delete data from the replicate table, correct the error, and then recreate the subscription. See the Replication Server Troubleshooting Guide > Subscription Problems > check subscription > Materialization Status and the Replication Server Troubleshooting Guide > Subscription Problems > Materialization Problems.