Verify the Mirror Replication Agent instance

This section describes how to verify a Mirror Replication Agent instance, which includes:

Update the Replication Server interfaces file with the Mirror Replication Agent location.
Verify the connection to the Mirror Replication Agent.
Verify the Mirror Replication Agent connection to Oracle.

Verifying the Mirror Replication Agent

Use dsedit to update the Replication Server interfaces file to include an entry for the Mirror Replication Agent location.

You can use any TDS client utility (isql, isqlApp, or SQLAdvantage) that you prefer.
Verify the connection to the Mirror Replication Agent:
1. Open a command window in the $SYBASE directory of your Replication Server installation.
2. Set the environment variables by sourcing the SYBASE.csh file.
3. Log in to Mirror Replication Agent:
```
isql –Usa –P –Smyma
```
  The following verification steps are optional because they were performed when you verified the resource file.
Verify the Mirror Replication Agent connection to Replication Server:
1. Enter:
```
test_connection RS
```
```
go
```
2. The following appears:
```
 Type Connection
```
```
 ---- ----------
```
```
 RS   succeeded
```
```
(1 row affected)
```
3. If the result indicates a failure, either the server is not responding or the connection properties (host, port, user, or password) are incorrect.Verify the host and port configuration values, and manually log in to the Replication Server as the configured user to determine which property is incorrectly defined.
  
  See the Mirror Activator Administration Guide.
Verify the Mirror Replication Agent connection to the primary Oracle database:
1. Enter:
```
test_connection PDS
```
```
go
```
  This message appears:
```
Type Connection
```
```
---- ----------
```
```
PDS  succeeded
```
```
(1 row affected)
```
2. If the result indicates a failure:
  - The server is not responding, or
  - The connection properties; tnsnames.ora connection name is incorrect.
  Check the tnsnames.ora file and tnsnames configuration values, and manually log in to the primary Oracle database as the configured user to find which property is incorrectly defined.
  
  See the Mirror Activator Administration Guide section titled, “Testing network connectivity.”