Summary of Extract Parameters (Classic Architecture)

4 Summary of Extract Parameters (Classic Architecture)

Here's a list of Extract parameters available in Classic Architecture.

Table 4-1 Extract Parameter: Processing Method

Parameter	Description
`RMTTASK`	Creates a processing task on a remote system.

Table 4-2 Extract Parameters: Tuning

Parameter	Description
`THREADOPTIONS`	Controls aspects of the way that Extract operates in an Oracle Real Application Cluster environment.

THREADOPTIONS

Valid For

Classic Extract, Oracle Database only

Description

Use the THREADOPTIONS parameter to control how a threaded Extract operates.

Stop and restart GGSCI, Manager, and Extract for the change to take effect.

Default

None

Syntax

THREADOPTIONS
[INQUEUESIZE n]
[OUTQUEUESIZE n]
[PROCESSTHREADS SELECT thread_spec | PROCESSTHREADS EXCEPT thread_spec]
[STACKSIZE bytes]

INQUEUESIZE n

Specifies the number of queue entries in the input queue of each producer Extract thread in an Oracle RAC cluster. Higher values produce better performance for large amounts of data. Lower values move data more quickly in environments with very little activity. Valid values are 16 to 65535. The default is 128. The default should be adequate in most cases, but if you need to increase it, 1000 should be sufficient in most types of environments. See also OUTQUEUESIZE.

In addition to INQUEUESIZE and OUTQUEUESIZE, AIX users might obtain better performance by setting the environment variable AIXTHREAD_SCOPE to S (system scope) which specifies the use of multiple CPUs so that processes can run concurrently. To use system scope, add the following to the .profile file of the user who starts the Manager process or else export the variable manually before starting GGSCI.

AIXTHREAD_SCOPE=S
export AIXTHREAD_SCOPE

OUTQUEUESIZE n

Specifies the number of queue entries in the output queue of each producer Extract thread in an Oracle RAC cluster. Valid values are 8 to 65535. The default is 2048. The default should be adequate in most cases.

[PROCESSTHREADS SELECT thread_spec | PROCESSTHREADS EXCEPT thread_spec]

Specifies the Extract threads to be processed or to be excluded from processing. Valid values are:

A single thread ID, such as 1
A range, such as 1-5

Extract threads are mapped to redo threads. Caution: Excluding any of the Extract threads from being processed excludes that data from being synchronized with the target tables.

Primarily for use when Extract is in Archived Log Only mode (ALO).

[STACKSIZE bytes]

Specifies the stack size of each producer Extract thread in an Oracle RAC cluster. Valid values are a range of 65536 - 33554432; the default is 1048576.

AUTOSTART

Valid For

Microservices Administration Service Profiles

Description

Use the AUTOSTART parameter to start one or more Extract or Replicat processes automatically when Manager starts. AUTOSTART ensures that no process groups are overlooked and that synchronization activities start immediately.

You can use multiple AUTOSTART statements in the same parameter file.

To apply this parameter to an Extract group that is created in PASSIVE mode, use it for the Manager that is on the target system where the associated alias Extract group resides. Oracle GoldenGate will send the start command to the source system. If AUTOSTART is used locally for a passive Extract group, it is ignored.

If Manager encounters an out-of-order transaction upon restart, it will not restart Extract. Instead, it will log a warning that notifies you to use the ETROLLOVER option of SEND EXTRACT to advance the trail to skip the transaction that caused the error.

Default

Do not auto-start processes.

Syntax

AUTOSTART {{EXTRACT | REPLICAT | ER} group_name | JAGENT}

EXTRACT: Starts Extract automatically.
REPLICAT: Starts Replicat automatically.
ER: Starts Extract and Replicat automatically.
group_name: Valid for EXTRACT, REPLICAT, ER only. JAGENT does not take a group name as input. Specifies a group name or wildcard specification for multiple groups. When wildcarding is used, Oracle GoldenGate starts all groups of the specified process type that satisfy the wildcard on the local system, except those in PASSIVE mode.
JAGENT: Starts the Oracle GoldenGate Monitor JAgent automatically. For more information, see Administering Oracle GoldenGate Monitor.

Example

AUTOSTART ER *

To know how to use this parameter from Microservices, see Administration Server: Profile Page in Oracle GoldenGate Microservices Documentation.