Starting an instance with the Administrator GUI

You must set the SYBASE environment before you invoke the Replication Agent administrator utility. See “Preparing to use the utilities” for more information.

To start a Sybase Replication Agent instance using Administrator

The administrator utility must be running before you use it to start a Replication Agent instance. See “Starting the Administrator GUI” for details.

When you start a Replication Agent instance on Windows, start-up processes are running in the background with no DOS windows open.

Select the Sybase Replication Agent instance or instances you want to start in the list of instances. Click Start.

Administrator provides a dialog box asking you to confirm that the appropriate JDBC driver is specified in the CLASSPATH environment variable. Click Yes to continue.

If the appropriate JDBC driver is not listed in the CLASSPATH environment variable, you can start the Sybase Replication Agent instance, but it will not be able to establish a connection to the primary database server.
Click Start.

The Sybase Replication Agent window indicates that the instance you selected is running:

You may need to click Refresh to see if the Sybase Replication Agent instance is running.
- On Windows 2000 or 2003, a console window opens for each Replication Agent instance you selected to start.
- On UNIX, each Replication Agent instance you selected is started in the background.
For all platforms, the Replication Agent is started using the ra_auto script, which is located in the RAX-15_0/bin directory. During start-up, standard error output is redirected to the error.log file, which is located in the Replication Agent instance’s log directory. After start-up, standard error and standard output directed to the <instance>.log file in the <instance>/log directory.

If you try to start a Sybase Replication Agent instance with the same administration port number as an instance that is already running, Sybase Replication Agent aborts the process and logs an error message in the system log.

If the instance you try to start does not run, check the instance log to see if an error occurred. See “Examine the Replication Agent logs” for more information about viewing the instance log.
Click Done to exit the Administrator GUI window.