Data Integrity Check Process FAQS

1. What is the purpose of the Data Integrity Check Process?
•  The purpose of the Data Integrity Check Process is to ensure that the data being loaded or integrated into the system meets predefined constraints and business rules defined in the Oracle Data Integrator (ODI) model. This process helps maintain data quality by validating it against these constraints.
2. When is the Data Integrity Check Process triggered?
•  The Data Integrity Check is triggered in two main cases:
1. Static Control: When a static control is started on a model, sub-model, or datastore to check existing data against defined constraints.
2. Flow Control: When a mapping is executed with flow control enabled, checking the data in the integration table (I$) against constraints for the target datastore.
3. What is the CKM (Check Knowledge Module)?
•  The CKM is the module responsible for performing the data integrity checks. It checks the data quality based on constraints defined in the model or mapping. The CKM can be used for both static control (checking existing data) and flow control (checking data during integration).
4. What types of controls exist in the Data Integrity Check process?
•  There are two main types of controls:
1. Static Control: Used for checking existing data in the datastore or model. The CKM is defined in the model.
2. Flow Control: Used during the execution of a mapping to check the data in the integration table (I$) before it is loaded into the target datastore. The CKM is specified for the mapping.
5. What kinds of constraints are checked during the process?
•  Various constraints can be checked during the integrity process, including:

• Null constraints (e.g., ensuring columns are not null).
• Range constraints (e.g., ensuring values fall within a valid range).
• Unique constraints (e.g., ensuring no duplicates).
• Foreign key constraints (e.g., ensuring referential integrity).
• Custom business rules defined in the model.

6. Can the CKM remove erroneous records?
•  Yes, the CKM can be configured to remove erroneous records from the table if the data fails the integrity checks. This action is controlled by the configuration set in the static or flow control.
7. How are the results of the Data Integrity Check process reported?
•  The results of the data integrity check process are typically logged and can be reported with details on any records that failed the checks. This log may include error messages and information on why certain records were removed or flagged.
8. Is the Data Integrity Check process always required during data integration?
•  No, the Data Integrity Check process is not always required but is highly recommended when validating data before loading it into the target system. It is activated when specific checks or controls are needed (via static control or flow control).
9. Can I configure which constraints are checked?
•  Yes, you can configure which constraints are checked during the flow control by selecting specific constraints for the mapping. For static control, the constraints are defined in the ODI model.
10. What happens if the Data Integrity Check fails?
•  If the Data Integrity Check fails, it can result in the identification of erroneous data, which may be removed (depending on the configuration). The failure is typically logged, and further actions, such as manual intervention or data correction, might be needed.