Setting up Replication Server

Replicating non-Sybase data requires unique function strings, datatype definitions, and translations to translate data from one datatype to another.

NoteFor more detailed information, refer to “Replication Server heterogeneous datatype support” and “Emulating rs_init activity for a non-Sybase database”.

Replication Server stores function strings, datatype definitions, and translations in the RSSD. These objects are loaded in the RSSD using scripts provided by Sybase. The scripts are located in $SYBASE/$SYBASE_RS/scripts and are named using the following conventions:

Each non-Sybase data server has a function-string class and a UDD class that contains function strings and UDDs that are used to translate the data into its native format. Additionally, each translation that defines how a non-Sybase datatype is translated to another non-Sybase datatype is associated with a function-string class.

All of these objects—function strings, UDDs, and translations—must be loaded in the RSSD of the correct Replication Server to produce the correct datatype transformations.

The following list describes issues that affect where these objects should be loaded:

StepsTo set up Replication Server to translate data for a non-Sybase database

  1. Modify each script to issue a use db command before any other commands, where db is the database name of the RSSD for the Replication Server.

    Make a copy of the script if it is needed in more than one RSSD. For example, add the following lines to the beginning of the scripts:

    use emb
    go
    
  2. Load the function-string class scripts first. From the command prompt enter:

    isql -Uuid -Ppassword -SRSSD
    < hds_dbtype_funcstrings.sql
    
  3. Load the UDD class scripts next. From the command prompt enter:

    isql -Uuid -Ppassword -SRSSD
    < hds_dbtype_udds.sql
    
  4. Load the translation scripts last. From the command prompt enter:

    isql -Uuid -Ppassword -SRSSD
    < hds_dbtype_to_dbtype.sql
    
  5. Shut down and restart the Replication Server.

    NoteThis last step is required. Modifying the RSSD does not refresh the Replication Server memory cache.