|| Description / Cause
||No more data
||No more data is available.
||Output string truncated
||The output string was truncated in lrd_to_printable, setting the last three characters to '...'.
||Invalid data type or unprintable data
||The specified data type is invalid or not printable (e.g., DT_VARRAW).
||Invalid data for data type
||For non-character data types, the data is invalid for the specified data type (e.g., 0x12BB for DT_DECIMAL)For character data types, the data contains unpredictable characters. This includes '\0' for types that are not null terminated such as DT_SF, DT_VARCHAR, DT_LONG_CHAR, DT_SF_STRIPPED_SPACES, DT_LONG_VARCHAR, DT_DISPLAY).
||Next set available
||The previous result set has ended and the next result set is available for lrd_fetch. No row is currently available.
||The host variable contains NULL data.
||Invalid host variable length
||An invalid length was specified for the host variable. This only applies to variable length data types where the length of the host variable and its prefix exceeds MAX SIZE.
||In lrd_to_printable, the indicator variable associated with the host variable indicates that the data was truncated. The host variable was too short to contain the fetched data.
||A call to a database routine failed, but the severity level|*LR_lrd_severity_levels>proc1 was set to WARNING OR the mliOpt1 and mliOpt2 combination in lrd_result_set, indicates an error in the original application.
||Data in error
||In lrd_to_printable, the return code variable associated with the host variable indicates an error in the data.
||A required null-terminator is missing.
||Value was rounded off
||The data's value was rounded off. For example: 1. When an underflow occurred for a numeric value, zero is assigned. 2. Nanoseconds were specified for the DT_DATETIME variable, for a database that does not support fractions of a second; the fraction is ignored.
||Recoverable row error
||A recoverable row error occurred when the current row was fetched. For example, a conversion error occurred when storing bound variables. In CtLib, the current ct_fetch generated a CS_ROW_FAIL return code.
||No fetchable data
||There is no more fetchable data from the current result set.
||No result sets
||There are no more result sets.
||Parameter saved as null
||A parameter was saved with a null value. References to this parameter may fail.
||Parameter saved with invalid value
||A parameter was saved with an invalid value. References to this parameter may fail.
||Parameter not be saved
||The specified parameter could not be saved; lr_param_save_bytes failed.
||Failed attempt to close structure
||An attempt was made to close a context, connection, or cursor that is not open.
|| Failed attempt to open structure
||An attempt was made to open a context, connection, or cursor that is already open.
||No fetchable result set is available
||There is no active fetchable result set, but the script continued because LRD_ON_FETCHABLE_SET_ERR_CONT was issued.
||"Success with Info" return code
||The database operation returned a "success with info" return code.
||"Need data" return code
||The database operation returned a "need data" return code.
||"Invalid handle" return code
||The database operation returned an "Invalid handle" return code.
||"Still executing" return code
||The database operation returned a "still executing" return code.
||"Continue" return code
||The database operation returned a "continue" return code.
||LRDBI handle mismatch
||There was a mismatch in an LRDDBI handle, e.g., a different parent handle
||Handle not allocated
||A handle was not properly allocated.