Verifying the Replication Agent Instance Installation

Verify that the Replication Agent instance has been successfully installed.

Use dsedit to update the Replication Server sql.ini (Windows) or interfaces (UNIX or Linux) file to include an entry for the Replication Agent location.

Note: You can use any Tabular Data Stream™ (TDS) client utility (isql, isqlApp, or SQLAdvantage) that you prefer.
If you use direct load materialization, also add the server name part of the connection name to the interfaces file. This entry should point to Replication Agent. For example:
```
pds
master tcp ether hostname 9030
query tcp ether hostname 9030
```
Note: The server name is the same value as the rs_source_ds value in the resource file used to create a Replication Agent instance.
(Optional)Verify the connection to Replication Agent:
1. Open a command window in the %SYBASE% (Windows) or $SYBASE (UNIX or Linux) directory of your Replication Agent installation.
2. Set the environment variables by executing the SYBASE.bat file (Windows) or by sourcing the SYBASE.csh file (UNIX or Linux).
3. Log in to Replication Agent:
```
isql –Usa –Psa_pass –Smyra
```
  Note: These verification steps are optional because they were performed when you verified the resource file.
```
isql –Uusername –Ppassword –Smyra
```
Verify the Replication Agent connection to Replication Server:
1. Enter:
```
test_connection RS
go
```
2. This result is returned:
```
 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 Replication Agent Administration Guide.
Verify the Replication Agent connection to the primary database:
1. Enter:
```
test_connection PDS
go
```
  You see:
```
Type Connection
---- ----------
PDS  succeeded
(1 row affected)
```
2. If the result indicates a failure:
  - The server is not responding, or
  - One of the connection properties 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 Testing Network Connectivity in the Replication Agent Administration Guide.