Goldengate holding archivelogs for inactive txns
edited Jun 25, 2013 9:57AM in GoldenGate, Streams and Distributed Database (MOSC) 4 commentsAnswered
Hello Experts,
Today we had ac issue in one of prod env where the gg (11.2.1.0.1). was holding the archivelogs for a session which was 4 days old and was in 'inactive' state. Why does gg was hold the archive log for inactive session .
how to do we avoid this issue, i think we do have a command to skip the txns from the extract or kill the session at db using manual approach but is there any other way do this where gg can automatically skips inactive session .
We have also seen some case 's where the gg is holding archivelog for select txns on the schema tables which are not in replication .
Today we had ac issue in one of prod env where the gg (11.2.1.0.1). was holding the archivelogs for a session which was 4 days old and was in 'inactive' state. Why does gg was hold the archive log for inactive session .
how to do we avoid this issue, i think we do have a command to skip the txns from the extract or kill the session at db using manual approach but is there any other way do this where gg can automatically skips inactive session .
We have also seen some case 's where the gg is holding archivelog for select txns on the schema tables which are not in replication .
0