Classic Extracts developed a significant lag processing chained rows (Doc ID 2040150.1)

Last updated on AUGUST 04, 2015

Applies to:

Oracle GoldenGate - Version 11.2.1.0.0 to 12.1.2.1.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

A couple of Classic Extracts have developed a significant lag of about 4 days.

Both extracts are RUNNING but the Current Checkpoint and Write Checkpoint are not changing.

The Extract is processing changes to partitioned tables which have hundreds of columns all of which are supplementally logged.

The extracts have stacks of the form

check_related_cfa 
get_next_complete_record 
REDOORAOUT_get_committed_record 
REDO_read_transaction_record 

or 

check_for_new_rowpiece 
force_chained_row_complete 
get_next_complete_record 
REDOORAOUT_get_committed_record 

and in the activity logging trace we have endless entries like 

check against rec: rid=AASlUiAESAAIFWdAAW,nrid=AASlUiAFnAANEk5AAN, u_nrid=AASlUiAAAAAAAAAAAA, rba=2924591052, seqno=358317 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms