Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Session Properties Reference
  17. Workflow Properties Reference

Error Handling Settings

Error Handling Settings

Error Handling settings allow you to determine if the session fails or continues when it encounters pre-session command errors, stored procedure errors, or a specified number of session errors.
The following table describes the Error handling settings of the Config Object tab:
Error Handling Settings
Description
Stop On Errors
Indicates how many non-fatal errors the Integration Service can encounter before it stops the session. Non-fatal errors include reader, writer, and DTM errors. Enter the number of non-fatal errors you want to allow before stopping the session. The Integration Service maintains an independent error count for each source, target, and transformation. If you specify 0, non-fatal errors do not cause the session to stop.
Optionally use the $PMSessionErrorThreshold service variable to stop on the configured number of errors for the Integration Service.
Override Tracing
Overrides tracing levels set on a transformation level. Selecting this option enables a menu from which you choose a tracing level: None, Terse, Normal, Verbose Initialization, or Verbose Data.
On Stored Procedure Error
Required if the session uses pre- or post-session stored procedures.
If you select Stop Session, the Integration Service stops the session on errors executing a pre-session or post-session stored procedure.
If you select Continue Session, the Integration Service continues the session regardless of errors executing pre-session or post-session stored procedures.
By default, the Integration Service stops the session on Stored Procedure error and marks the session failed.
On Pre-Session Command Task Error
Required if the session has pre-session shell commands.
If you select Stop Session, the Integration Service stops the session on errors executing pre-session shell commands.
If you select Continue Session, the Integration Service continues the session regardless of errors executing pre-session shell commands.
By default, the Integration Service stops the session upon error.
On Pre-Post SQL Error
Required if the session uses pre- or post-session SQL.
If you select Stop Session, the Integration Service stops the session errors executing pre-session or post-session SQL.
If you select Continue, the Integration Service continues the session regardless of errors executing pre-session or post-session SQL.
By default, the Integration Service stops the session upon pre- or post-session SQL error and marks the session failed.
Error Log Type
Specifies the type of error log to create. You can specify relational, file, or no log. 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 error log.
Error Log Table Name Prefix
Specifies table name prefix for a relational error log. Oracle and Sybase have a 30 character limit for table names. If a table name exceeds 30 characters, the session fails.
Error Log File Directory
Specifies the directory where errors are logged. By default, the error log file directory is $PMBadFilesDir\.
Error Log File Name
Specifies error log file name. By default, the error log file name is PMError.log.
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
Specifies whether or not to log source row data. By default, the check box is clear and source row data is not logged.
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.