When an extract process in Oracle GoldenGate abends (abnormally terminates), it can disrupt the data replication flow and require investigation to identify and resolve the underlying issue. Here’s a typical paragraph you might encounter in logs or documentation regarding an abended extract process:
Here are the checklists to be followed to identify the cause of abnormal termination and the process to fix.
Identify the Last Consistent Point: Determine the last consistent point in the source database redo logs where the extract process successfully captured changes before it abended.
Edit the Extract Parameter File: Update the extract parameter file (usually with a .prm extension) to specify the starting point for the extract process.
Reinitialize Extract: If necessary, reinitialize the extract process using the ADD EXTRACT command in the GoldenGate command interface.
Start Extract Process: Start the extract process using the START EXTRACT command in the GoldenGate command interface.
Alter the extract to the last VAM Read Checkpoint time, and start the extract process to start mining the data from a particular point in time. Extract will automatically repoint to the log number and log position
AT THE TIME OF FAILURE
PROCESS STATUS
GGSCI (ORA-X1) 1> info ERMYSQL detail
EXTRACT ERMYSQL Last Started 2021-04-26 13:52 Status ABENDED
Checkpoint Lag 00:00:00 (updated 114:52:15 ago)
VAM Read Checkpoint 2021-04-21 18:55:12.000000
Log Number: 8
Record Offset: 31049
Target Extract Trails:
Trail Name Seqno RBA Max MB Trail Type
/MYSQL/ggtrail/ERMYSQL/rm 11 53084 500 EXTTRAIL
Extract Source Begin End
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Not Available 2021-04-21 18:11 2021-04-21 18:55
Current directory /MYSQL/gguser
Report file /MYSQL/gguser/dirrpt/ERMYSQL.rpt
Parameter file /MYSQL/gguser/dirprm/ermysql.prm
Checkpoint file /MYSQL/gguser/dirchk/ERMYSQL.cpe
Process file
Error log /MYSQL/gguser/ggserr.log
Altering the extract to the VAM Read Checkpoint time.
GGSCI (ORA-X1) 2> ALTER EXTRACT ERMYSQL, BEGIN 2021-04-21
OR TO BE MORE PRECISE
GGSCI (ORA-X1) 2> ALTER EXTRACT ERMYSQL, BEGIN 2021-04-21 18:55:12.000000
GGSCI (ORA-X1) 2> START ERMYSQL
GGSCI (ORA-X1) 1> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING ERMYSQL 00:00:00 00:00:07
EXTRACT RUNNING PRMYSQL 00:00:00 00:00:07
REPLICAT RUNNING RMYSQL 00:00:00 00:00:03
REPLICAT RUNNING RSMYSQL 00:00:00 00:00:08
After repositioning to the exact point of time the extract was able to start without any issues.
