1 person found this helpful
How about scheduling a script to do this for you?
Do it via cron or Windows scheduler.
You could then run the following command -
ggsci paramfile stop_all_replicats.script
And the stop_all_replicats.script file would contain something like -
stop replicat *
If you want to direct the output to a log then in Linux you would do this something like -
ggsci paramfile stop_all_replicats.script > stop_all_replicats.log 2>&1
Yes we had this option but as per client requirement it has to be done through GG and not by any os utility.
We also tried using endpoint.inc option of GG but this file also needs to be edited with date daily.
As we need to to exact date and time when we want to stop replicat/extract this again has dependency at OS level.
Any suggestions will really be helpful.
Sorry for the late reply on this.
stop_all_replicats.script will stop the replicats on target at 1 am. But their can be some scenarios where the replicat itself is lagging behind in such case the data will not be accurate as of 1 am.
Hence, we created a table in source and scheduled a cronjob to update this table at 1 am. when this record is replicated the replicat will stop with eventactions stop.