Verifying the Replication Agent instance

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

1. Update the Replication Server interfaces (UNIX or Linux) or sql.ini (Windows) file with the Replication Agent location.

2. Verify the connection to the Replication Agent.

3. Verify the Replication Agent connection to IBM DB2 Universal Database.

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

   You can use any TDS client utility (isql, isqlApp, or SQLAdvantage) that you prefer.

2. Verify the connection to the Replication Agent:

   1. Open a command window in the $SYBASE (UNIX or Linux) or %SYBASE% (Windows) directory of your Replication Agent installation.

   2. Set the environment variables by sourcing the SYBASE.csh file (UNIX or Linux) or executing the SYBASE.bat file (Windows).

   3. Log in to Replication Agent:

      isql –Usa –P –Smyra
      

      The following verification steps are optional because they were performed when you verified the resource file.

3. Verify the 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 Replication Agent Administration Guide.

4. Verify the Replication Agent connection to the primary IBM DB2 Universal 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

      • One of the connection properties is incorrect.

      Manually log in to the primary IBM DB2 Universal Database as the configured user to find which property is incorrectly defined.

      See the Replication Agent Administration Guide section titled, “Testing network connectivity.”