Why Does GoldenGate Report The Lag Is Unknown or a Timestamp Mismatch- (Doc ID 968614.1).pdf

DBA never sleep-DBA,永不眠
Focus on Oracle Database, GodenGate and Unix
[置顶] Why Does GoldenGate Report The Lag Is Unknown or a Timestamp
Mismatch? (Doc ID )
分类: Oracle GoldenGate 2013-08-10 19:53 456人阅读评论(0) 收藏举报
Oracle GoldenGateLag Is UnknownTimestamp Mismatch
Issue:
Why does GoldenGate report the Lag is unknown? The "Lag" command fails with "Timestamp Mismatch".
Sometimes the "Info All" will also show the Lag is unknown.
How to troubleshoot the problem?
Add a user token to a test table.
.,
table , tokens (tkn-time = ***@DATENOW());
Next, do a dml on this table mit.
Then, check with logdump (set: usertokens detail) pare the mit time (this is from redo log)
and the token (from os time when extract processes the record). if former time is later then the one from token,
it may cause this 'unknown' display.
Solution Overview:
(1) mand(after handling one or more records)
GGSCI > lag extract e1
Sending GETLAG request to EXTRACT E1...
Lag unknown (timestamp mismatch between source and target).
At EOF, no more records to process.
(2) "Info All"(This may happen after handling a large amount of records)
GGSCI > info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING E1 unknown 00:00:04
(3) "showch" and date timestamp mismatch
GGSCI > info e1 showch
...
Checkpoint Lag unknown (updated 00:00: