ROLLOVER

Valid for

Extract

Description

Use ROLLOVER to specify times at which local or remote trails automatically roll over, in sequence. Each ROLLOVER rule applies to all Oracle GoldenGate trails and remote trails.

Use ROLLOVER to extract data continuously but create files representing distinct periods of time (for example, each day). Also, to send extracted data to external systems periodically, use ROLLOVER to cut off one file and start the next.

Files roll over only between the output of distinct transactions, not in the middle of a transaction. Checkpoints are recorded as soon as files roll over to ensure the previous files are no longer required by Extract.

Rollover occurs if the rollover conditions are met during the run. In other words, if ROLLOVER ON TUESDAY is specified, and Extract starts on Tuesday, rollover will not occur until the next Tuesday (unless other ROLLOVER rules are specified).

You can specify up to thirty rollover rules.

Syntax

ROLLOVER
[AT hh:mm] 
[ON day_of_week]
[AT hh:mm ON day_of_week]
[AT END]
[REPORT]

AT hh:mm: The time of day. Using AT without ON generates a report at the specified time every day.
ON day_of_week: The day of the week. Valid values are SUNDAY through SATURDAY.
AT END: A STOP requested from GGSCI or the end of a SPECIALRUN.
REPORT: A report regarding the number of records extracted from each table and file since the last report was generated. The report represents the number of records output to the corresponding file (unless other reports are generated by means of the REPORT parameter).

Example

The following example rolls over local and remote Oracle GoldenGate trails every day at 3:00 p.m. as well as every Sunday at 8:00 a.m. For instance, if the file $DATA2.EXTDATA.AA000122 is the current file Monday morning, then at 3:00 p.m. on Monday AA000122 will be closed and AA000123 will be created.

ROLLOVER AT 15:00
ROLLOVER AT 08:00 ON SUNDAY