分类: LINUX
2016-06-09 16:29:17
OGG Extract abends : Non-Standard Redo Detected in 10g compatible Format
Cause 1
This error occurs when the extract's starting seqno# and rba are not on log write boundary. When positioning by time, extract will find the right log write boundary by itself.
Cause 2
Extract may fail with same error due to bug in AsyncReader logic. This issue occurs when the AsyncReader reaches an EOF condition and stops read operations before the REDO thread detects the EOF condition and instructs the AsyncReader thread to stop reading.
Cause 3
Extract is altered by extseqno and extrba
alter extract EACHINTP thread 1, extseqno 10552,extrba 26465408
alter extract EACHINTP thread 2, extseqno 5431,extrba 1148456
Cause 4
Extract with DBLOGREADER can produce this error reading Oracle database versions that support DBLOGREADER APIs and is related to the premature logfile switching, hence "bad" data has been read by the DBLOGREADER api and passed to GoldenGate Extract, which has caused the Extract abend. A restart does not resolve this issue. Please refer to the reference manual for Oracle database versions that support DBLOGREADER APIs.
Solution 1
Alter extract to position by timestamp and restart
ggsci> ALTER EXTRACT {extract group}, BEGIN {timestamp}
ggsci> START {extract group}
Solution 2
1. This issue is recoverable by restarting extract
2. This issue can be avoided via 'tranlogoptions _NOREADAHEAD CURRENT'
3. Upgrade to 11.2.1.0.0 or later
Solution 3
Alter extract to position by timestamp and restart
ggsci> ALTER EXTRACT {extract group}, BEGIN {timestamp}
ggsci> START {extract group}
Solution 4
Include parameter
You need to upgrade to v11.2.1.0.26 or later and specify this parameter
TRANLOGOPTIONS _DISABLESTREAMLINEDDBLOGREADER
As of version 12 this option is permanently disabled.