Configure Replication Server for replication to standby

This section describes how to configure Replication Server for replication to standby.

StepsTo create a Replication Server connection to standby

  1. Go to the $SYBASE/MA-15_0/scripts/oracle directory.

  2. Create the Oracle error class:

    1. Execute these three scripts:

      NoteThe oracle_error_class_1_rs.sql and oracle_error_class_3_rs.sql scripts are executed to the Replication Server. The oracle_error_class_2_rs.sql script is executed in the RSSD.

      isql –Usa –P –SSAMPLE_RS -i oracle_create_error_class_1_rs.sql
      
      
      isql -U SAMPLE_RS_RSSD_prim -P SAMPLE_RS_RSSD_prim_ps 
      –SSAMPLE_RS_ERSSD –i oracle_create_error_class_2_rssd.sql 
      -DSAMPLE_RS_ERSSD
      
      
      isql –Usa –P –SSAMPLE_RS -i oracle_create_error_class_3_rs.sql
      
  3. Make a copy of the oracle_create_rs_standby_connection.sql directory:

    cp oracle_create_rs_standby_connection.sql myma_oracle_create_rs_standby_connection.sql
    
  4. Before executing the myma_oracle_create_rs_standby_connection.sql script against your Replication Server, change occurrences of value {rds}.{rdb} to the name of the connection that Replication Server will use to connect to DirectConnect for Oracle, where:

    Here is an example:

    create connection to DCOServer.oratest2set error class oracle_error_classset function string class rs_oracle_function_classset username maintuserset password “password”set batch to "off"go
    

    NoteIn the previous example, “password” is a Replication Server reserved word, and it must be enclosed in double quotes.

  5. Create the connection to the standby database:

    isql –Usa –P –SSAMPLE_RS -i myma_oracle_create_rs_standby_connection.sql
    

    The connection to the standby database is created.

  6. To verify the Replication Server connection to the standby database, log in to SAMPLE_RS and verify the Replication Server connection to the standby database:

    isql –Usa –P –SSAMPLE_RSadmin whogo
    

    You should see a message returned for the DSI connection {rds}.{rdb}. Verify that the status is “Awaiting Message” or “Awaiting Command.”

  7. Exit isql.