Archives are again getting read by the extract after it gets abended
638429Aug 2 2012 — edited Aug 5 2012Hi All,
The goldengate is implemented in ALO mode. The issue is that the "extract read the archives from sequence number 219 and then reaches sequence number 555. In the mean time whatever data that has been fetched gets passed on to the replicat and the replicat is applying those data. But when there is no more archive to read the "EXTRACT" gets abended with the message EOF reached.
Now since last two days what i noticed is that whenever i start the extract its starts from the initial position i.e. 219 then again goes to the point like sequence number 600 and again abends. During the extraction time between 219 to 555 it does not show that its extarcting any insert updates and deletes but only extracts data from sequence number 556 to sequence number 600.
The problem is when i moving the archives from sequence 219 to 500 and when i am starting the extract it is looking for 219 sequence. Has anyone experienced these kind of issues.
Any help wiill be highly appreciated.