Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Rules and Guidelines for Creating Key Ranges

Rules and Guidelines for Creating Key Ranges

Use the following rules and guidelines when you create key ranges:
  • The partition key must contain at least one port.
  • If you choose key range partitioning at any partition point, you must specify a range for each port in the partition key.
  • Use the standard PowerCenter date format to enter dates in key ranges.
  • The Workflow Manager does not validate overlapping string or numeric ranges.
  • The Workflow Manager does not validate gaps or missing ranges.
  • If you choose key range partitioning and need to enter a date range for any port, use the standard PowerCenter date format.
  • When you define key range partitioning at a Source Qualifier transformation, the Integration Service defaults to pass-through partitioning if you change the SQL statement in the Source Qualifier transformation.
  • The Workflow Manager does not validate overlapping string ranges, overlapping numeric ranges, gaps, or missing ranges.
  • If a row contains a null value in any column that defines the partition key, or if a row contains values that fall outside all of the key ranges, the Integration Service sends that row to the first partition.


Updated July 04, 2018