3 Running the Oracle GoldenGate Veridata Programs

This chapter explains how to run the Oracle GoldenGate Veridata programs, such as the agents and Java components.

This chapter includes the following sections:

3.1 Starting and Stopping the C-agent and Manager

The C-agent starts automatically at the request of Oracle GoldenGate Veridata Server when initiating comparisons. However, for Oracle GoldenGate Veridata Agent to function correctly, the following must be running:

  • The database to which the agent is linked.

  • The Manager process for the C-agent.

Although the agent process itself is an automatic process, you can stop the Manager process that controls the agent. Stopping Manager prevents Oracle GoldenGate Veridata Server from being able to start a new agent process, but it does not stop agents that are already running.

To control the C-agent Manager on all platforms

  1. From the Oracle GoldenGate Veridata Agent installation location, run GGSCI.

  2. In GGSCI, issue the appropriate command as follows to stop or start the Manager.

    START MANAGER

    Or...

    STOP MANAGER

3.2 Starting and Stopping the Java-Based Components

The Oracle GoldenGate Veridata Server and Oracle GoldenGate Veridata Web components are Java-based programs. The Oracle GoldenGate Veridata Agent component is also available as a Java program for all platforms except NonStop.

Note:

Before starting the server and web processes, start the repository database.

3.2.1 Controlling the Java-Based Components from the Command Line

To control the agent component, change directories to its installation directory and issue the appropriate command as follows:

UNIX and Linux Windows 
agent.sh {start | run}
Or... 
agent.sh stop  

agent.bat {start | run}
Or... 
agent.bat stop

Where:

  • run starts the agent in the same command window from which it is launched.

  • start starts the agent in a separate command window.

    Note:

    The run option is useful for diagnosing errors that happen during the startup process before the agent error logging is configured. When the run option is used, messages written stdout and stderr appear in the command window. The agent normally logs its messages to the log file, so only operating system messages and logging system errors are written to stderr. When the start option is used, messages written to stdout and stderr are discarded.

Configure the host to start and stop the processes automatically. Contact your system administrator if you need assistance.

3.3 Reloading Log Information

You can reload logging information from the AGENT_ORACLE_HOME/config/odl.xml configuration file to a running agent by using the reloadLog option. The changes in the odl.xml file are put into effect on the agent. The agent must be running for this command to work.

Use the following command:

UNIX and Linux Windows 
agent.sh reloadLog

agent.bat reloadLog

3.4 Connecting to Oracle GoldenGate Veridata Web Interface

To connect to the Veridata Web User Interface, open a web browser and type the following address:

http://hostname:port/veridata

Where:

hostname is the name of the system where Oracle GoldenGate Veridata Server is installed and port is the port number where it is running (default is 8830). Use localhost as the host name if connecting on the system that is local to the server installation.

Examples:

http://localhost:8830/veridata
http://sysa:8830/veridata

The Oracle GoldenGate Veridata Web login page is displayed upon successful connection. Log in with your user name and password. For full instructions on using Oracle GoldenGate Veridata Web Interface, see the Online Help.