You are here: How To Guides > Purging results

Purging Results

OEDQ uses a repository database to store the results and data it generates during processing. All of the results data is 'temporary' in the sense that it can be regenerated using the stored configuration, which is held in a separate database internally.

In order to manage the size of the results repository database, OEDQ allows you to purge the results for a given set of staged data (either a snapshot or written staged data), a given process, a given job, or all results for a given project.

For example, if you have a number of projects on a server, you may wish to purge the results of old projects from the server, but keep the configuration of the project stored in case you need to run any of its processes in the future.

Note that the results for a project, process, job, or set of staged data are automatically purged if that project, process, job, or staged data set is deleted. If required, this means that you can package project configurations to file, test that the packages import correctly, and then delete them from the server. The configurations can then be restored from the archive at a later date if required.

To purge results for a given snapshot, set of written staged data, process, job, or project:

The purge task will run on the server. If there is a lot of data to purge, you may see it running in the Task Window.

Note:Purging data from OEDQ will not purge the data in the Results window in Server Console. Likewise, purging data in Server Console will not affect the OEDQ Results window. Therefore, if trying to free up disc space, you may have to purge data from both.

Purging Match Decision data

Match Decision data is not purged along with the rest of the results data. Match Decisions are preserved as part of the audit trail which documents the way in which the output of matching was handled.

If it is necessary to delete Match Decision data, for example, during the development process, the following method should be used:

Note:Purging the match decisions takes place immediately. However, it will not be visible in the match results until the match process is re-run. This final stage of the process updates the relationships to reflect the fact that there are no longer any decisions stored against them.

Oracle ® Enterprise Data Quality Help version 9.0
Copyright © 2006,2011 Oracle and/or its affiliates. All rights reserved.