The ODP Fetcher uses an ODP Queue as a data source. For data read it provides multiple Extraction Modes. It also supports filtering on selected data.

Creation of ODP Fetcher

Perform the steps outlined in How to Create a Fetcher Object with the ODP Fetcher option selected under the Component implementation and the dropdown of step 4.

Activation of ODP Fetcher

After creation, the object is in the saved state.

Mandatory inputs to fill before the activation:

ODP Queue
- name of the ODP Queue for data read
- provided with F4 help
ODP Context
- name of the ODP Context also known as Provider in Monitor Delta Queues (transaction ODQMON)
- provided with F4 help
- default value is SAPI (DataSources/Extractors)
Key deduplication
- checkbox (unchecked by default). When checked, the functionality removes duplicate values from a single data load, keeping only the latest value for each record.
- changeable before each extraction

Optional inputs before the activation:

Selection
- checkbox for each field of the ODP Queue that allows you to check them relevant for selection before the extraction

Extraction Modes

ODP Fetcher provides multiple Extraction (Replication) Modes that are identical to (Glue-2205) Data replication with delta with one additional option - Recovery of Previous Deltas.

Recovery of Previous Deltas is useful when the last delta extraction failed and should be repeated.

Please keep in mind that delta functionality is handled by ODP Queue, not by SNP Glue™ that doesn't store any delta pointers, but can reset delta for given ODP Queue (e.g. when running delta Initialization with or without data transfer).

Automatic Recovery of Previous Deltas

Every time the delta load is executed, there is a check verifying if the last delta run finished successfully. If not, the delta mode will be automatically switched to Recovery of Previous Deltas. This was done in order to prevent potential data loss due to ODQ delta logic.

Browser not supported