From the context menu of a defined distribution, select New Request.
You define a request schedule on the Common page of the request’s Properties dialog box, whose options are the same for a Replication, a Copy, or a Synchronization request. If a request has no schedule, it must be started and stopped manually using a monitoring and control tool, such as Connect CDC MonCon.
By default, dates and times display with the local values for the Connect CDC Director host machine. To see GMT times in the Connect CDC Director, select View>Options and change the Time zone reference to GMT.
If you select GMT, the time you see when you enter a schedule on the Common page of the request’s Properties dialog box is GMT time, including the offset.
However, when the next scheduled time is calculated, GMT is the reference. Connect CDC calculates the local time at which the request starts by considering the time zone of the local host and GMT in combination.
The table below shows the request schedule parameters, what they mean, the rules governing them, and what format to use.
|
Parameter |
Description |
Rules |
Format |
|---|---|---|---|
|
Start Date |
First date to start the request. |
Specify the start date in all schedules. |
format: M/dd/yy M = month [1-12] d = day [1-31] yy = year [2000 or greater] |
|
Start Time |
First time on the start date when the request will be started. |
Specify the start time in all schedules. |
format: h:mm:ss tt h = hour [0-23] (6:00 is 6 AM, and 18:00 is 6 PM) mm = minutes [0-59] ss = seconds [0-59] Microseconds are optional. tt = AM or PM (not case sensitive) |
|
Stop Date |
Date after which the request can no longer be active. |
If the schedule does not contain a stop date and time, request stays activated according to the schedule forever. |
format: M/dd/yy M = month [1-12] d = day [1-31] yy = year [2000 or greater] |
|
Stop Time |
Time on the stop date after which the request can no longer be active. |
If the schedule does not contain a stop date and time, request stays activated according to the schedule forever. |
format: h:mm:ss tt h = hour [0-23] (6:00 is 6 AM, and 18:00 is 6 PM) mm = minutes [0-59] ss = seconds [0-59] Microseconds are optional. tt = AM or PM (not case sensitive) |
|
Request Duration |
Duration of time for which the request is active after each scheduled start. |
|
Number and a unit [seconds, minutes, hours, days, or months]. |
|
Repeat Interval |
Duration of time after each scheduled start when the request needs to be scheduled again. |
|
Number and a unit [seconds, minutes, hours, days, or months] |
Connect CDC uses the following rules to start a request at its scheduled time.
-
The kernel needs to be active for the model.
-
If the kernel is not running, the scheduled request starts are missed during that time.
-
When the kernel runs at a later time, it silently ignores the scheduled start requests that were missed.
-
If the schedule contains a request duration, the request stops on schedule even if the request has not "completed" its work.
For instance, the kernel stops a copy request at its scheduled time even if it has not completed copying all tables in the request.
If a request is not active at its scheduled stop time (due to the request running to completion before its scheduled stop time or a user manually stopping the request), the scheduled stop request results in no action in the kernel.
-
If a bi-directional request has a schedule associated with it, it is started on all its source hosts at the same time, provided the kernel is running on all these hosts.
-
You may manually start or stop the request that has a schedule associated with it
-
You may schedule multiple requests to run at the same time as long as the requests belong to different distributions and do not share tables with other running requests.
Using the start date and time and time zone, Connect CDC applies date arithmetic to handle changes due to daylight saving time and variation in lengths of months. For example, it is possible to run a request on the same day every week or at the end of every month.