This section describes the replicate database issues and considerations specific to the Adaptive Server Anywhere (ASA) data server in a Sybase replication system.
ASA is a different relational database from Sybase Adaptive Server Enterprise, which is the original replicate data server supported by Replication Server.
As a replicate data server in a replication system, ASA interacts directly with the replicate Replication Server. The replicate Replication Server logs in to the ASA replicate database and applies replicated transactions.
The rssetup script file is provided with ASA to set up an ASA database to function as a replicate database. It performs the following:
Creates a user ID named dbmaint, with password dbmaint, with DBA permissions. This is the Replication Server Maintenance User ID and password required to connect to the primary database.
Creates a user named sa, with password sysadmin, with DBA permissions. This is the user ID used by Replication Server when materializing data.
Adds sa and dbmaint to a group named rs_systabgroup.
Creates the system tables and stored procedures necessary in the replicate database to support Replication Server.
The only significant intrusions or impacts to the ASA replicate database are the database objects created by the rssetup.sql script to support Replication Server replicate database operations.
The rssetup.sql script creates two tables in the replicate database to support Replication Server operations:
rs_info – contains information about the sort order and character set used by the replicate database. You should confirm that the insert statements for this table set the proper character set and sort order for your replicate database.
rs_lastcommit – holds information about the last successfully committed replicate transaction applied to the replicate database.
You do not need to use a database gateway when you use ASA as a replicate data server; the replicate Replication Server connects directly to the ASA replicate data server.
A Replication Server database connection name is made up of two parts: a data server name (server_name) and a database name (db_name). The replicate Replication Server looks for an interfaces file entry for the replicate database server_name specified in the database connection.
Replication Server logs in to the replicate data server using the user_name and password specified in the database connection. For ASA replicate databases, the user_name and password should be the dbmaint user ID and password that were created when the rssetup.sql script was executed.
The replicate Replication Server does not use the source_db portion of the Replication Server database connection. Instead, Replication Server obtains the database name from the command line of the data server identified in the source_ds portion of the Replication Server database connection. However, you must include a database name in the Replication Server create connection statement to conform to the syntax.
You also must make an entry in the Replication Server interfaces file to identify the host and port where the ASA replicate data server is listening. The interfaces file entry name must match the server_name portion of the Replication Server database connection.
The Heterogeneous Datatype Support (HDS) feature of Replication Server does not support ASA databases. No user-defined datatypes, translations, or function strings are provided.
