I am trying to find out if there is a way to scheduling my tasks to run every 15 minutes. I have been testing out the Batch tuning settings and have mixed results with the Apply Latency setting. I don't need the tasks to continuously run, just to run every 15 minutes and apply the change records.
"WHY" ? Knowing why may help providing a better solution.
The Replicate build in scheduler has daily as the lowest granularity so that's not practical.
To schedule a full-load task every so many minutes is fine (unavoidable). As per @PGN you best option is probably to use a server specific scheduler like 'at' and activate the task with REPCTL (not supported) or the Enterprise Manager API (supported).
To schedule a CDC task every so many minutes as suggested is not a great idea. So much overhead in starting up and closing down. But most importantly how and when will you stop the task? Give it 5 minutes, hope for the best and request a stop? There is no concept of 'done' for a CDC task. At best you could try to look for quiet periods or low activity periods. More work and not robust.
You may want to look at just changing the rate with which Replicate asks the source DB whether there is something new. This is heavily end-point dependent and often an advanced setting sometimes under internal parameters. For example logScanPollingCycleInterval for a SQLserver source if I recall correctly. Is this perhaps a file source? - Advanced - Check for changes every (sec):
Does your source DB have regular transaction log backup like in SQLserver or Archivelogs in Oracle. Then you may want to switch the source endpoint to 'archive log only' and set 'checkArchivedRedoIntervalInSeconds' to be a few minutes. This most effective as the tasks sleeps for long intervals and wakes up when there is a nice chunk of work to be done.
