Symptom
A Binary LOAD corrupts data or throws an unexpected error if ASCII load syntax is used in some or all columns of the statement.
- Extract data in a binary format and load it into another table.
Newly loaded data does not match the original data.
There were no errors or warnings during load.
- Extract data in a binary format and load it into another table.
The data fails to load with one of the following error messages:
1) [20618]: Warning: Partial input record (9 bytes) skipped at EOF (O/S 0). 3 rows read.
Exception Thrown from db_sqlins.cxx:15395, Err# 36, tid 304 origtid 304
O/S Err#: 0, ErrID: 4098 (db_sqlexception); SQLCode: -157, SQLState: '53018', Severity: 16
[2104]: Cannot convert to a timestamp (column c3)
2) Exception Thrown from dflib/dfo_CheckConstraintFilter.cxx:505, Err# 322, tid 3 origtid 3
O/S Err#: 0, ErrID: 4098 (db_sqlexception); SQLCode: -195, SQLState: '23502', Severity: 16
[2126]: Column 'c3' in table 'd2' cannot be NULL
Read more...
Product
SAP IQ 16.0 ; SAP IQ 16.1
Keywords
KBA , BC-SYB-IQ , Sybase IQ , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview