Extract Is Running But Stuck At Same RBA And Send Commands Gives Timeout Waiting For Message
Last updated on FEBRUARY 06, 2017
Applies to:Oracle GoldenGate - Version 10.4.0.40 and later
Information in this document applies to any platform.
1. Extract is running but stuck at same RBA or Extract is timing out for send commands and extract show the following warning messages in report file
Redo thread 1: Detect slow log writer on sequence 6652, log file /uo1/app/OGG/1_6652_85858539.arc
Redo thread 1: Failed to validate last block from log /uo1/app/OGG/1_6652_85858539.arc with sequence# 6652 and filesize of 45407360 bytes due to mismatch in seqno from last block (0, 6652) . Please make sure the archived log is complete and valid.
2. If the report files does not show any warning or error messages, Enable activity logging trace and see if the trace files has the messages like the following
For enabling activity logging trace refer
OGG v184.108.40.206 Activity Logging tracing Activity Trace [Doc ID 1204284.1]
3. OGG installed on remote system and extract is hung and activity logging shows the following message
2017-01-03 06:27:41.105 INFO |er.redo.ora.thread.logswitch |main| 7380 oracle/redoorardr.c | (get_logfile_header_info) Setting thread NOT DISABLED for thread 256 sequence 1327, DIS 0, eor_type 0, eor_scn 0, eor_restart_scn 0 2017-01-03 06:27:41.105 WARN |er.redo.ora.thread.logswitch |main| 2743 oracle/redoorardr.c | get logfile header info failed with , Block size mismatch (131072/512) reading redo log +DG_DATA05/tarhp1/archive/arch_1_2334_5656778.arc for sequence 2334
2017-01-03 06:27:41.105 INFO |er.redo.ora.thread.logswitch |main| 4718 oracle/redoorardr.c | +DG_DATA05/tarhp1/archive/arch_1_2334_5656778.arc, seq#=1327, bytes read 0, last record SCN = 0.0 (0), filesize 0.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms