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

Configuring Error Log Options

Configuring Error Log Options

You configure error logging for each session on the Config Object tab of the sessions properties. When you enable error logging, you can choose to create the error log in a relational database or as flat file. If you do not enable error logging, the Integration Service does not create an error log.
Use the Workflow Manager to create a reusable set of attributes for the Config Object tab.
To configure error logging options:
  1. Double-click the Session task to open the session properties.
  2. Select the Config Object tab.
  3. Specify the error log type.
    The following table describes the error logging settings of the Config Object tab:
    Error Log Options
    Description
    Error Log Type
    Specifies the type of error log to create. You can specify relational database, flat file, or none. Default is none.
    You cannot log row errors from XML file sources. You can view the XML source errors in the session log.
    Error Log DB Connection
    Specifies the database connection for a relational log. This option is required when you enable relational database logging.
    Error Log Table Name Prefix
    Specifies the table name prefix for relational logs. The Integration Service appends 11 characters to the prefix name. Oracle and Sybase have a 30 character limit for table names. If a table name exceeds 30 characters, the session fails.
    You can use a parameter or variable for the error log table name prefix. Use any parameter or variable type that you can define in the parameter file.
    Error Log File Directory
    Specifies the directory where errors are logged. By default, the error log file directory is $PMBadFilesDir\. This option is required when you enable flat file logging.
    Error Log File Name
    Specifies error log file name. The character limit for the error log file name is 255. By default, the error log file name is PMError.log. This option is required when you enable flat file logging.
    Log Row Data
    Specifies whether or not to log transformation row data. When you enable error logging, the Integration Service logs transformation row data by default. If you disable this property, n/a or -1 appears in transformation row data fields.
    Log Source Row Data
    If you choose not to log source row data, or if source row data is unavailable, the Integration Service writes an indicator such as n/a or -1, depending on the column datatype.
    If you do not need to capture source row data, consider disabling this option to increase Integration Service performance.
    Data Column Delimiter
    Delimiter for string type source row data and transformation group row data. By default, the Integration Service uses a pipe ( | ) delimiter. Verify that you do not use the same delimiter for the row data as the error logging columns. If you use the same delimiter, you may find it difficult to read the error log file.
  4. Click OK.


Updated June 03, 2019