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. Appendix A: Datatype Reference
  22. Appendix B: Reporting Views
  23. Appendix C: Metadata Import Syntax
  24. Appendix D: Jasper Reports
  25. Appendix E: Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Maximum Row Size Limit

Maximum Row Size Limit

Often, when importing schema definitions into PowerCenter, string fields are imported with "infinite" length. This is simply a convenience when the maximum size of the field is not known in advance.
"Infinite" length strings are given a physical length in PowerCenter of 898989 characters.
In most cases, having many fields this size does not cause errors, because the maximum row size that PowerCenter can process is 100MB. But some transformations have restrictions on their maximum row size. The Sorter can handle a maximum row size of 8MB, which is a significantly smaller than the maximum row size of PowerCenter in general.
Sorters are used in Data Validation Option mappings to sort data before Joins. This is a best practice when using PowerCenter as Joiners process sorted inputs almost an order of magnitude more efficiently than Joiners with unsorted data.
If an XML definition has multiple "infinite" string fields, the following error may appear in the session log when a Data Validation Option job fails:
>SORT_40414 : Error: Total row size [12586408] in transformation [NAME_6] is more than the allowed maximum [8388607].
This error is typically caused by "infinite" length strings in the PowerCenter source or target definition.
To resolve the problem, update the PowerCenter XML definition that is causing the error, and replace "infinite" field lengths of 898989 with field lengths based on the size of the actual data.