Verify that a replication system is configured correctly by materializing subscription data. Some configuration problems do not appear until you attempt to materialize subscription data. The most common configuration problems that cause materialization failures are:
Failure to log in to the primary Adaptive Server. The user who creates the subscription in the replicate Replication Server must have the same login name and password in the primary Adaptive Server and the primary Replication Server.
Missing permissions in the primary database. The user who creates the subscription must be a user in the primary database and must have select permission in the primary table.
Missing permissions in the replicate database. The maintenance user must have select, insert, update, and delete permissions on the tables in the replicate database.
A Replication Server or Adaptive Server has stopped running. Try to log in to each server using isql. Restart any servers that are not running.
Other common configuration problems include:
Host name resolution error.
The Adaptive Server entry does not exist in the interfaces file.
See “rs_init error message descriptions”.
For more information about troubleshooting Replication Server configuration problems, see the Replication Server Configuration Guide for your platform.
