Why do I get a full extract upon running a Changes Only extract?

There are several reasons why a Changes Only extract runs in a full mode or extracts all data.

Do the following:

• Rollback all the incomplete runs caused due to the forceful cancellation of an extract run. Now, run your Changes Only extract again.

• Select Changes Only since last Successful Run in the Extracts Definitions page of the extract and try again.

• Verify if the configured threading database item uniquely identifies the extracted data.

• Avoid including parameters as record elements in your extracts definition. For example, the effective date parameter is unique for each run and if you include it in your definition as a record element, it can result in full extract even when you run a Changes Only extract.