Error Handling for the SAP IQ Output Adapter

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

Scenario	Result
On start-up, the adapter verifies that the service name provided belongs to an ODBC service entry, and that the specified table exists. The adapter then checks whether a permutation exists, or it assumes a default mapping from the stream or window to the indicated database table and verifies that the mapping is valid.	If any of these checks fail, the adapter logs an error message to the Server log and does not start.
There is a column in the database that is not nullable, and there is no column mapping in the permutation for that column.	The adapter fails to initialize, and an error is logged to the Server log indicating that a mapping for the required column was not provided.
Certain column mappings are valid in data-dependent situations. For example, an integer may be stored in a `tinyint` column only if its value is between 0 and 255. Refer to Datatype Mapping for the SAP IQ Output Adapter.	The mappings that require runtime data checks are identified at adapter start-up, and the adapter verifies only these for each record. Due to the performance impact of runtime checks on each Event Stream Processor record, SAP recommends that you do not use these mappings unless you cannot change your existing schemas . If a runtime check fails for a mapping, the adapter rejects the record. The bad rows statistic is incremented, and the adapter logs a message to the Server log indicating that it discarded a row, and the nature of the error, without providing any information about the specific record (no data values).
An `string` is longer than the `varchar` or `char` column into which it is to be stored.	The Event Stream Processor record is stored in the database and the string is truncated to fit in the column. The warning that is written to the log indicates that the string was truncated without providing any specific data from the row.
A load file cannot be loaded into the database due to a database error.	The load file remains on the file system, and an error indicating the location and name of the file, and the nature of the error is logged. You can use the load table statement for SAP IQ that is in the Event Stream Processor log file to reload the file into SAP IQ. The adapter does not attempt to reload any load files that have failed in the past.You must manually correct any problems and load the file.
Binary values that are too large for the database column into which they are mapped.	The individual row is discarded, the bad rows statistic is incremented, and an error is logged to the Server log.
A batch contains a bad row.	The individual row is discarded, the bad rows statistic is incremented, and an error is logged to the Server log.