Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and 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 Target Database Partitioning

Rules and Guidelines for Target Database Partitioning

Use the following rules and guidelines when you use database partitioning with database targets:
  • You cannot use database partitioning when you configure the session to use source-based or user-defined commit, constraint-based loading, or session recovery.
  • You cannot use database partitioning when the target tables are partitioned by range. If the target tables are partitioned by range, use pass-through or key range partitioning.
  • The target table must contain a partition key, and you must link all not-null partition key columns in the target instance to a transformation in the mapping.
  • Enable high precision for the session when an IBM DB2 target table partition key is a Decimal column. The Integration Service might fail the session when a partition key is a Decimal column and you do not enable high precision for the session.
  • If you create multiple partitions for a DB2 bulk load session, use database partitioning for the target partition type. If you choose any other partition type, the Integration Service reverts to normal load and writes the following message to the session log:
    ODL_26097 Only database partitioning is support for DB2 bulk load. Changing target load type variable to Normal.
  • If you configure a session for database partitioning, the Integration Service reverts to pass-through partitioning under the following circumstances:
    • The DB2 target table is stored on one node.
    • You run the session in debug mode using the Debugger.
    • You configure the Integration Service to treat the database partitioning partition type as pass-through partitioning and you use database partitioning for a non-DB2 relational target.


Updated July 04, 2018