ASE Replicator configuration problems  Problems that cause replication to fail

Chapter 5: Troubleshooting ASE Replicator

User login or permission problems

ASE Replicator requires a user login for each data server and database that it connects to.

The system user login is the login that ASE Replicator uses to connect to its host Adaptive Server (the primary data server). The ASE Replicator system user login must be added to each primary database, and must have appropriate object access permissions in each primary database.

The Maintenance User login is the login that ASE Replicator uses to connect to each remote (replicate) data server. The ASE Replicator Maintenance User login must be added to each replicate database, and must have appropriate object access permissions in each replicate database.

To allow bidirectional replication, in which a primary database also acts as a replicate database, ASE Replicator identifies a Maintenance User for each database. ASE Replicator uses the Maintenance User login to apply replicated transactions to a replicate database. When publishing the transactions from a primary database, ASE Replicator filters out any transactions applied by the Maintenance User in that database.

If you use the same login name and password for all ASE Replicator database connections, user login and permission problems are less likely to occur, but using a common password may not be feasible in a bidirectional replication system, and it may not meet your security requirements.

Some typical symptoms of user login or permission problems are:

StepsTo correct user login or permission problems

  1. See Chapter 2, “Setting Up and Starting ASE Replicator,” and verify that all the configuration tasks are completed.

  2. Verify that the ASE Replicator system user login (or Maintenance User login) is:





Copyright © 2004. Sybase Inc. All rights reserved. Problems that cause replication to fail

View this book as PDF