Show TOC

Error Handling for the SAP ASE Output AdapterLocate this document in the navigation structure

Various scenarios that write error messages in the ESP Server log.

Scenario Result
  • The database service specified by the service parameter is not for an SAP ASE database.
  • The connection information for the database is invalid.
  • The database table specified by the table parameter does not exist.
  • The permutation parameter is specified but one of the columns does not exist in the database table.
  • The database column datatype is not supported for a given Event Stream Processor datatype.
  • You do not specify the permutation parameter, and the stream or window attached to the SAP ASE Output adapter has a schema where the order, names, or count of the columns are different from the order, names, or count of the columns in the target database table.
  • The database contains a column that is not nullable and has no default value defined in the database, and a column mapping does not exist in the permutation for that column.

The SAP ASE Output adapter fails to initialize and logs an error message to the ESP Server log file.

  • A row contains integer or long or money values that are too large to store in a given SAP ASE column datatype.
  • A row has a float value that fails to convert to the target numeric or decimal value.
During message flow:
  • The row is rejected.
  • The bad rows statistic is incremented.
  • An error message is logged to the ESP Server log file.
  • The Event Stream Processor string value is longer than the varchar or char database column into which it is to be stored.
During message flow:
  • The adapter truncates the string value.
  • A warning message is logged to the ESP Server log.
  • The warning messages in the ESP Server log file do not contain any data from the rows truncated during message flow.
  • The Event Stream Processor binary value is longer than the varbinary or binary database column into which it is to be stored.
During message flow:
  • The adapter rejects the row.
  • An error message is logged to the ESP Server log.
  • The error messages in the ESP Server log file do not contain any data from the rows rejected during message flow.
  • A row contains a duplicate primary key of a row that is already in the database.

The given row and all other rows in the current batch are rejected and are not inserted into the database.

  • You do not set the select into/bulk copy option in the database.
The SAP ASE adapter will fail to initialize, as it requires the select into/bulk copy option enabled for bulk copying to work.
  • A batch contains a bad row.
During message flow:
  • The individual row is discarded.
  • The bad rows statistic is incremented.
  • An error message is logged to the ESP Server log file.