READER

Valid for

Coordinator

Description

Use READER to trigger the creation of a Reader process to monitor a local trail and communicate with the system Coordinator. The HOST parameter from GLOBALS file will be used to determine the location of the object to be used. Typically this will be the installation location for Oracle GoldenGate, but if it varies the PROGRAM option can be used to point to another object.

Syntax

READER EXTTRAIL trail_name
[, PROCESS process_name], 
[, CPU primary_cpu] 
[, BACKUPCPU cpu] 
[, PRI priority]
[, PROGRAM program_name]

EXTTRAIL trail_name

The fully qualified identifier of the trail that will be monitored by the Reader. This is a required entry.

PROCESS process_name

The process name of the associated Reader.

Oracle GoldenGate recommends you allow the process name to be generated by the system. However, if you must specify an alternative process, PROCESS process_name lets you do so.

CPU primary_cpu

Specifies the primary CPU on which the Reader process runs. The default is the CPU on which Manager runs.

BACKUPCPU cpu

Specifies an alternate CPU on which the process runs if the primary CPU becomes unavailable.

PRI priority

The NonStop priority for the process. This defaults to the priority assigned to the TACL process underlying the ADD.

PROGRAM program_name

This specifies the name of the program that Manager uses when starting the Reader process. Typically this is not entered, and Manager uses the HOST parameter in the GLOBALS files to determine the Oracle GoldenGate installation subvolume as indicated in the GGSSUBVOL option.

Example

The following example identifies a Reader process to monitor Oracle GoldenGate trail AA on \NY.
READER EXTTRAIL \NY.$DATA5.GGSDAT.AA, PROCESS $GGRD1, CPU 1, PRI 180