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

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.