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

Advanced Workflow Guide

Advanced Workflow Guide

Understanding the Error Log Tables

Understanding the Error Log Tables

When you choose relational database error logging, the Integration Service creates the following error tables the first time you run a session:
  • PMERR_DATA.
    Stores data and metadata about a transformation row error and its corresponding source row.
  • PMERR_MSG.
    Stores metadata about an error and the error message.
  • PMERR_SESS.
    Stores metadata about the session.
  • PMERR_TRANS.
    Stores metadata about the source and transformation ports, such as name and datatype, when a transformation error occurs.
You specify the database connection to the database where the Integration Service creates these tables. If the error tables exist for a session, the Integration Service appends row errors to these tables.
Relational database error logging lets you collect row errors from multiple sessions in one set of error tables. To do this, you specify the same error log table name prefix for all sessions. You can issue select statements on the generated error tables to retrieve error data for a particular session.
You can specify a prefix for the error tables. The error table names can have up to eleven characters. Do not specify a prefix that exceeds 19 characters when naming Oracle, Sybase, or Teradata error log tables, as these databases have a maximum length of 30 characters for table names. You can use a parameter or variable for the table name prefix. Use any parameter or variable type that you can define in the parameter file. For example, you can use a session parameter, $ParamMyErrPrefix, as the error log table name prefix, and set $ParamMyErrPrefix to the table prefix in a parameter file.
The Integration Service creates the error tables without specifying primary and foreign keys. However, you can specify key columns.


Updated November 14, 2019