Step 2. Configure Rep Server for replication to standby

This section describes the required configurations for Rep Server for replication to standby.

To create a Rep Server connection to standby

Change directories to the $SYBASE/MRO-12_6/scripts directory.

Create the Oracle error class:

Execute the following three scripts:

The oracle_error_class_1_rs.sql and oracle_error_class_3_rs.sql scripts are executed to the Rep 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

Before executing the oracle_create_rs_standby_connection.sql script against your Rep Server, change all occurrences of value {rds}.{rdb} to the name of the connection Rep Server will use to connect to DirectConnect for Oracle, where:
- rds – the DCO Server name
- rdb – any valid identifier (It is recommended that you use the Oracle SID name.)
- maintuser and password – the user name and password created in DCO
The following 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
```
Execute the script in Rep Server:
```
isql –Usa –P –SSAMPLE_RS -i oracle_create_rs_standby_connection.sql
```
The connection to the standby database is created.
To verify the Rep Server connection to the standby database, log in to SAMPLE_RS and run the admin who command:
```
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.”