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

After You Create a Session with Multiple Partitions

After You Create a Session with Multiple Partitions

When you edit a mapping
after
you create a session with multiple partitions, the Workflow Manager does not invalidate the session even if the changes violate partitioning rules. The Integration Service fails the session the next time it runs unless you edit the session so that it no longer violates partitioning rules.
The following changes to mappings can cause session failure:
  • You delete a transformation that was a partition point.
  • You add a transformation that is a default partition point.
  • You move a transformation that is a partition point to a different pipeline.
  • You change a transformation that is a partition point in any of the following ways:
    • The existing partition type is invalid.
    • The transformation can no longer support multiple partitions.
    • The transformation is no longer a valid partition point.
  • You disable partitioning or you change the partitioning between a single node and a grid in a transformation after you create a pipeline with multiple partitions.
  • You switch the master and detail source for the Joiner transformation after you create a pipeline with multiple partitions.


Updated July 04, 2018