Why the OGGBD replicat not starting at the same seq/rba of where it was stopped.
(Doc ID 2590996.1)
Last updated on JULY 18, 2023
Applies to:
Oracle GoldenGate Big Data and Application Adapters - Version 12.3 and laterInformation in this document applies to any platform.
Symptoms
The OGGBD(Big data) replicat not starting at the same seq/rba of where is was stopped.?
GGSCI (<Host name>) 43> info <Replicat Name>
REPLICAT <Replicat Name> Last Started 2019-09-13 11:15 Status RUNNING
Checkpoint Lag 615:15:16 (updated 00:00:03 ago)
Process ID 342396
Log Read Checkpoint File
<path>/bo000000234
2019-08-18 20:05:56.999262 RBA 238459224
GGSCI (<Host name>) 44> stop <Replicat Name>
Sending STOP request to REPLICAT <Replicat Name> ...
Request processed.
GGSCI (<Host name>)45> info <Replicat Name>
REPLICAT <Replicat Name> Last Started 2019-09-13 11:15 Status STOPPED
Checkpoint Lag 614:15:24 (updated 00:00:15 ago)
Log Read Checkpoint File
<path>/bo000000242
2019-08-18 21:06:01.000863 RBA 86159962
GGSCI (<Host name>) 46> start <Replicat Name>
Sending START request to MANAGER ...
REPLICAT <Replicat Name> starting
GGSCI (<Host name>) 47> info <Replicat Name>
REPLICAT <Replicat Name> Last Started 2019-09-13 11:21 Status RUNNING
Checkpoint Lag 626:20:44 (updated 00:00:01 ago)
Process ID 354576
Log Read Checkpoint File
<path>/bo000000000
2019-08-18 09:01:05.000659 RBA 15395745
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |