Table of Contents

Search

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

Data Validation Option User Guide

Data Validation Option User Guide

Troubleshooting

Troubleshooting

Unlike relational tables, which are relatively straight forward, XML structures can be quite complex, and span multiple files or locations. In short, there are more "moving parts" when dealing with XML, and each part has to be correct and consistent with the other parts.
When XML errors are encountered, there are several immediate areas to consider and verify.
  • Does the XML data match the schema?
  • Does the data match the PowerCenter metadata definition?
  • For multi-file schemas, are the files and relative file path references matching?
  • Are all the expected files present?
The error messages displayed in the Data Validation Option screens are the first place to look.
For example, the following error message indicates that the data does not match the schema. An element in the XML file is not defined in the XML definition.
In the following example, the message indicates that the expected XML file is not present. This means the file could be missing, the file name could misspelled, or the directory or path was entered incorrectly.
Use of Multi-file schemas could also cause these types of errors if the relative file paths are not correct.
These are the easier problems to solve because they follow well defined patterns and error messages are reasonably specific.