Alter Replicat to start at the last good RBA before corruption:
After the replicat passes that RBA, remove the filter and restart normally.
When this happens, your target database stops synchronizing. Data latency begins to grow. And if not handled correctly, you risk data divergence between source and target.
#!/bin/bash for trail in /u01/gg/dirdat/rt*; do echo "checking $trail" echo "open $trail" > /tmp/logdump_cmd echo "n" >> /tmp/logdump_cmd echo "q" >> /tmp/logdump_cmd /u01/gg/logdump < /tmp/logdump_cmd | grep -i "error\|corrupt\|unexpected" done Scenario: A large financial firm replicates a 10TB Oracle database. One night, a backup job fills the /goldengate filesystem to 100%. The Extract continues writing but fails to complete the last record in rt000241 .
Alter Replicat to start at the last good RBA before corruption:
After the replicat passes that RBA, remove the filter and restart normally.
When this happens, your target database stops synchronizing. Data latency begins to grow. And if not handled correctly, you risk data divergence between source and target.
#!/bin/bash for trail in /u01/gg/dirdat/rt*; do echo "checking $trail" echo "open $trail" > /tmp/logdump_cmd echo "n" >> /tmp/logdump_cmd echo "q" >> /tmp/logdump_cmd /u01/gg/logdump < /tmp/logdump_cmd | grep -i "error\|corrupt\|unexpected" done Scenario: A large financial firm replicates a 10TB Oracle database. One night, a backup job fills the /goldengate filesystem to 100%. The Extract continues writing but fails to complete the last record in rt000241 .