Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. Repositories
  4. XML Data Source
  5. Tests for XML Data Sources
  6. Connections
  7. Expressions
  8. Table Pairs
  9. Tests for Table Pairs
  10. Single-Table Constraints
  11. Tests for Single-Table Constraints
  12. Examples of Tests from Spreadsheets
  13. SQL Views
  14. Lookup Views
  15. Join Views
  16. Aggregate Views
  17. Business Intelligence and Reporting Tools Reports
  18. Dashboards
  19. DVOCmd Command Line Program
  20. Troubleshooting
  21. Datatype Reference
  22. Reporting Views
  23. Metadata Import Syntax
  24. Jasper Reports
  25. Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Troubleshooting Table-Pair Tests

Troubleshooting Table-Pair Tests

Table-pair tests can fail for different reasons. Review the tips to help you troubleshoot table-pair tests.
Review the following troubleshooting tips for table-pair tests:
The table-pair test fails.
If the Data Validation Option target folder in the PowerCenter Designer or the PowerCenter Workflow Manager is open, Data Validation Option cannot write to the folder and the tests fail. Before you run tests, verify that the target folder is closed in the PowerCenter Designer and the PowerCenter Workflow Manager.
Data Validation Option creates a bad record during a table-pair test when one of the values is empty.
If you compare two fields where one field has a value and the other is empty, Data Validation option considers the record as a bad record. If the repository is on Oracle, the database stores an empty field as NULL. A bad record with NULL value in an Oracle repository can be either NULL or an empty field.
The table join failed for a table pair that has a file list connection.
If you specify a file list connection and the keys in the join condition are not unique among all files in the file list, the join fails. Choose keys that uniquely identify records among all files in the file list.