Hello,
I have integrated Extract (remote capture) and integrated Replicat (remote apply) set up using GoldenGate Cloud Service. When the source database was taken down for maintenance I expected the Extract process would have been abendoned and then it would have restarted on its own. But it didn't happen. The connections to the source were gone so I received alerts, later I found the extract still shows 'RUNNING' so it didn't restart. it was basically hung.
Was that by design?
I had the AUTORESTART set in manager, and I've seen a few times when the target was down, the replicat process did restart just fine.
Does the extract process work differently with replicat process on this perspective? that I should manually stop/start the extract process for maintenance on source db?
Thank you,
Erin