Verify the Mirror Replication Agent instance

This section describes how to verify a Mirror Replication Agent instance, which includes the following sequence of tasks:

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.

To verify the Mirror Replication Agent

Using dsedit, 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. Use the isql utility to log in to Mirror Replication Agent:
```
isql –Usa –P –Smyma
```
  The following verification steps are optional because they were done when you verified the resource file.
Verify the Mirror Replication Agent connection to Replication Server:
1. Enter this command:
```
test_connection RS
```
```
go
```
2. The following is displayed:
```
 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.
  
  For more information, refer to the Mirror Activator Administration Guide, Chapter 2, “Setup and Configuration,” in the section titled, “Testing network connectivity.”
Verify the Mirror Replication Agent connection to the primary Oracle database:
1. Enter this command:
```
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.
  
  For more information about connection failures, see the Mirror Activator Administration Guide section titled, “Testing network connectivity.”