6 Working with Trails

A trail is a series of files on disk where Oracle GoldenGate stores the captured changes temporarily to support the continuous extraction and replication of database changes You can use trails to monitor path, tune networks, and data input and output..

This section provides steps to perform the tasks required to set up trails:

Topics:

  • Quick Tour of the Receiver Server Home Page
    The Receiver Server is the central control service that handles all incoming trail files.
  • Monitoring Paths
    You can monitor the path statistics from the Receiver Server.
  • Tuning Network Parameters
    Network parameters include TCP flush byte options, DSCP, TOS, buffer size settings and so on. You can monitor and fine-tune these parameters depending on your requirements using the Performance Metrics and Distribution Server.

6.1 Quick Tour of the Receiver Server Home Page

The Receiver Server is the central control service that handles all incoming trail files.

The Receiver Server works with the Distribution Server to provide compatibility with the classic remote architecture. The Receiver Server home page shows the condition of the distribution path with one end depicting the Extract and the other end, the Replicat.

You can use the Receiver Server home page to view the path details. Simply click Action, Details to see the path details. To know more, see Monitoring Paths.

Parent topic: Working with Trails

6.2 Monitoring Paths

You can monitor the path statistics from the Receiver Server.

To monitor path statistics:, visit the Receiver Server. You’ll see the path depicted in a graphical representation. and you can perform the following steps to monitor the selected path:
  1. From Service Manager, click Receiver Server.
  2. Click Action, Details.
    The Process Information page is displayed. You can constantly monitor the activity of the path on the Process Information page. This page displays the following details:

    • Network Statistics: The network statistics information includes details such as target trail file name, port number, total messages written out, and so on. You can use this information to go back to the Distribution Server and tune the network parameters, if required.

    • File IO Statistics: The file IO statistics include total bytes read, total idle time and so on.

Parent topic: Working with Trails

6.3 Tuning Network Parameters

Network parameters include TCP flush byte options, DSCP, TOS, buffer size settings and so on. You can monitor and fine-tune these parameters depending on your requirements using the Performance Metrics and Distribution Server.

You can view the network parameters from the Performance Monitor Server Overview page. If you need to tweak them, go to the Distribution Server and do the following:
  1. Click the path Action, Details.
    The Process Information page is displayed. This page displays Advanced Options.
  2. Expand the Advanced Options.

    You’ll see App Options, which contain the TCP Flush Bytes and TCP Flush Seconds values. By default, this value is set to OS Default.

    The TCP Options, include the following parameters:

    • DSCP

    • TOS

    • Nodelay

    • Quick ack

    • Cork

    • System Send Buffer Size

    • System Receiver Buffer Size

  3. Click the Edit icon next to Advanced Options, to change any of the these values,.
  4. Click Apply to save the changes to the network parameters.
Once you edit the network parameters, do monitor their status changes and messages from the server. You can do so using the Performance Monitor Server. See Monitoring Performance for details.

Parent topic: Working with Trails