Databases 5 min read

Recovering Oracle GoldenGate After a Source Crash: Step‑by‑Step Fixes

This guide explains how to restore Oracle GoldenGate synchronization after a source‑side crash by repairing the extract service, restarting the pump process, and correcting the replicat on the target, with detailed commands and file‑selection procedures.

ITPUB
ITPUB
ITPUB
Recovering Oracle GoldenGate After a Source Crash: Step‑by‑Step Fixes

Background : At 13:00 the Oracle GoldenGate (OGG) source node crashed, causing the source and target data to become unsynchronized. The extract service stopped, the pump process failed to start, and the replicat on the target showed checkpoint lag.

Source‑Side Recovery

1. Fix the extract service

Status: abended Commands to restart:

alter extract extract_name ETROLLOVER
alter extract extract_name,tranlog,begin 2013-09-13 13:00
start extract_name

Verify with info all that the service is running.

2. Restart the pump process

Locate the view parameters PUMP_P1 to obtain the RMTTRAIL path and the target IP address.

Typical pump configuration (replace placeholders as needed):

EXTRACT PUMP_T1
USERID ogg@xxxx,PASSWORD xxxxxx
SETENV (NLS_LANG="AMERICAN_AMERICA.ZHS16GBK")
RMTHOST 10.x.xx.xx, MGRPORT 8050
RMTTRAIL ./dirdat/m1
PASSTHRU

On the source host, inspect the trail directory to find the latest file number:

cd /app/oracle/ggs/dirdat
ll m1* -t

Assume the newest file is m1010509, giving file number 10509. Apply it to the pump:

alter extract PUMP_T1 ETROLLOVER
alter PUMP_T1 extseqno 10509,extrba 0
start PUMP_P1

Target‑Side Recovery

Log into the target host using the IP obtained from the source pump configuration.

Identify the problematic replicat process (e.g., REP_DS) with: info REP_DS Typical output shows a checkpoint lag and that the trail file prefix matches the source (ml). Example excerpt:

REPLICAT   REP_DS   Last Started 2013-09-13 15:28   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:03 ago)
Log Read Checkpoint   File ./dirdat/m1000752
RBA 1106516

List the trail files on the target to find the newest one: ll m1* -t Assume the latest file is m1000753 (file number 0753). Apply it to the replicat:

alter REPLICAT REP_DS extseqno 0753, extrba 0
start REP_DS

Confirm all processes are healthy with info all or info *.

Following these steps restores OGG synchronization between source and target after an unexpected source crash.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

data replicationtroubleshootingExtractOracle GoldenGatePumpReplicat
ITPUB
Written by

ITPUB

Official ITPUB account sharing technical insights, community news, and exciting events.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.