Valid For

Administration Server Profiles

Description

Use the AUTORESTART parameter to restart one or more Extract or Replicat processes automatically, if they encounter a failure resulting in an ABENDED status.

For Classic Architecture, if the Extract or Replicat process abends, then these processes need to be manually restarted or the AUTORESTART parameter should be used in the Manager parameter file.

For MA, add the user profile either from Admin Client or from Web UI. In the following example, the user profile, critical is added to the Extract group named, extn:

ADD PROFILE critical AUTORESTART RETRIES 1 WAITSECONDS 0 RESETSECONDS 0 DISABLEONFAILURE NO
--Add the profile to EXTRACT/REPLICAT
ALTER EXTRACT extn PROFILE critical

You can use multiple AUTORESTART 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 AUTORESTART 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.

AUTORESTART does not restart processes whose last updated status was STOPPED.

Default

Do not auto-restart processes.

Syntax

AUTORESTART {EXTRACT | REPLICAT | ER} group_name
[, RETRIES number]
[, WAITMINUTES minutes]
[, RESETMINUTES minutes]
[, RESETSECONDS seconds]

EXTRACT

Restarts Extract automatically.

REPLICAT

Restarts Replicat automatically.

ER

Restarts Extract and Replicat automatically.

group_name

A group name or wildcard specification for multiple groups. When wildcarding is used, Oracle GoldenGate starts all groups of the specified process type on the local system that satisfy the wildcard, except those in PASSIVE mode.

RETRIES number

The maximum number of times that Manager should try to restart a process before aborting retry efforts. The default number of retries is 2. The first time that Manager tries to restart a process is not counted as a retry. So, the number of retries performed by the Manager are one more than the value specified for the number of retries. For example, if the number of retries is 2, then Manager tries to restart the process 3 times.

WAITMINUTES {minutes }

The amount of time, in minutes, to pause between discovering that a process has terminated abnormally and restarting the process. Use this option to delay restarting until a necessary resource becomes available or some other event occurs. The default delay is 2 minutes.

RESETMINUTES | RESETSECONDS {minutes | seconds}

The window of time, in minutes or seconds, during which retries are counted. The default is 120 minutes (2 hours) or 7200 seconds. After the time expires, the number of retries reverts to zero.

Example

In the following example, Manager tries to start all Extract processes three times after failure within a one hour time period, and it waits five minutes before each attempt.

AUTORESTART EXTRACT *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 60

If you want to set up AUTORESTART using Microservices, see Managed Processes in Oracle GoldenGate Microsevices Documentation.