LOG

Valid for

Logger

Description

Use LOG to identify both a Logger process and the volume to which the Logger process writes data (a log trail). The trails hold data for Replicat and are maintained by Oracle GoldenGate management processes.

The number of LOG entries in the Logger parameter file indicates the number of Logger processes in the system and the number of log trails. Each Logger process writes data to exactly one log trail. By default, LOG process names have the format $GGLnn. Therefore, if two LOG entries are made in the parameter file, processes $GGL00 and $GGL01 perform logging for the system.

The first LOG entry must precede all other parameter entries. LOG space is allocated after the configuration is processed.

Syntax

LOG logtrail_name
[, EXTENTS (primary, secondary, maximum) |  MEGABYTES megabytes]
[, NUMFILES number]
[, NEWFORMAT]
[, OWNER group_number, user_number]
[, PROCESS process_name]
[, RECSIZE bytes| BLOCKSIZE bytes]
[, SECURE "rwep"]

logtrail_name

The location of the log trail files for the current Logger process and the two-character process prefix. You can use the Oracle GoldenGate defaults, or specify a custom subvolume or process prefix.

To specify a custom subvolume or a custom process prefix, enter $vol.subvol.xx, where $vol. is the volume where Oracle GoldenGate is installed, subvol is the custom name of your subvolume, and xx is the two-character process prefix.

See "Specifying a custom subvolume, process prefix, or process name" for more information.

EXTENTS primary, secondary, maximum

The storage dimensions of each log trail file, where primary, secondary, maximum represents the extents. You must include EXTENTS if you omit MEGABYTES.

MEGABYTES megabytes

The storage in megabytes allocated per log trail file where megabytes represents the number of megabytes. You must include MEGABYTES if you omit EXTENTS.

NUMFILES number

The number of files to include in the log trail.

NEWFORMAT

NEWFORMAT produces Oracle GoldenGate version 7 format trails.

OWNER group_number, user_number

The Guardian group and user that owns the log trail files. The default is the group user running GGSCI.

PROCESS process_name

Lets you override the default process name, for example $GGL01. This can be useful when you add or alter an Extract or Replicat group.

For more information, see "Specifying a custom subvolume, process prefix, or process name".

RECSIZE bytes | BLOCKSIZE bytes

The record or block size in 4096 byte increments up to 56K (57344). It will be rounded to the next higher multiple if the entered value is not a multiple of 4096.

SECURE "rwep"

The Guardian security applied to each of the files. Defaults to the default security of the owner.

Examples

Example 1

The following example creates and pre-allocates 10 files sized at 50 megabytes each in $DATA.GGSLOG, owned by SUPER.SUPER with security NUUU, with a prefix of LT.

LOG $DATA.GGSLOG.LT, MEGABYTES 50, NUMFILES 10, OWNER 255,255, SECURE "NUUU"

Example 2

The following changes the default process name.

LOG $DATA.GGSLOG.LT MEGABYTES 500, PROCESS $GGL01, NUMFILES 10, SECURE "NNNN"

Specifying a custom subvolume, process prefix, or process name

By default, Oracle GoldenGate defaults to the subvolume GLOGGGL, and assigns a default process prefix and name. For example, files are created in volume.GLOGGGL and the default processes would be $GGL00 writing to log trail files AA000000, AA000001 and so on and $GGL01 writing to BB000001, BB000001, etc. To use the Oracle GoldenGate default, enter $vol.GLOGGGL, where $vol is the volume where Oracle GoldenGate is installed.

However, should you change or add a Logger, Extract or Replicat component, you may need to change the subvolume, process prefix, or process name to ensure the correct trails are read.

To change the subvolume or process prefix, see the logtrail_name argument.
To change the process name, see the PROCESS argument.