Quickly force the kill goldengate exception process

Goldengate cannot shut down the process normally by using stop when it encounters a large transaction or exception, and it is a headache when it encounters this problem, so help finds two mass killers, so you no longer have to worry about stop not dropping the process. If you encounter a large transaction or recommend to wait for the transaction to commit or rollback to close normally, but when you encounter some exceptions, you can use the following kill to drop the process:

GGSCI > KILL REPLICAT group_name

GGSCI > KILL EXTRACT finance

Stop the process normally:

GGSCI > stop REPLICAT group_name

GGSCI > stop EXTRACT finance

Here is a detailed description of the two commands

GGSCI > help kill replicat

Use KILL REPLICAT to kill a Replicat process. Killing a process leaves the

Most recent checkpoint in place, and the current transaction is rolled back

By the database, guaranteeing that no data is lost when the process is

Restarted. The Manager process will not attempt to restart a killed Replicat

Process. Use this command only if Replicat cannot be stopped gracefully with

The STOP REPLICAT command.

Syntax

KILL REPLICAT group_name

Group_name

The name of a Replicat group or a wildcard () to specify multiple groups.

For example, T kills all Replicat processes whose group names begin with T.

Example

KILL REPLICAT finance

GGSCI > help kill extract

Use KILL EXTRACT to kill an Extract process running in regular or PASSIVE mode.

Use this command only if a process cannot be stopped gracefully with the STOP

EXTRACT command. The Manager process will not attempt to restart a killed

Extract process.

Syntax

KILL EXTRACT group_name

Group_name

The name of an Extract group or a wildcard () to specify multiple groups.

For example, T kills all Extract processes whose group names start with T.

Example

KILL EXTRACT finance