AUTOSTART

Valid For

Manager (Classic), Microservices Administration Server 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 Step by Step Data Replication Using Oracle GoldenGate Microservices Architecture.