"Data overflow" error often appears while running HEI activity with Source as "Oracle" and Destination as "Notes".
Log similar to below can be observed while running the HEI activity -->
2023/04/14 16:31:34 Activity started
2023/04/14 16:31:35 Character set not equal 'Oracle codepage 832 set by EIOracle8NativeText does not equal the codepage of the Oracle database (871), data loss is possible', Connector <Oracle connector name>, Method -Connect-
2023/04/14 16:31:35 Character set overriding 'Overriding Oracle codepage to UTF8 (LCSTREAMFMT 171) from source Oracle Server', Connector <Oracle Connector Name>, Method -Connect-
2023/04/14 16:31:35 Trace Statement: <select * from table>, Connector <Oracle connector name>, Method -Execute-
2023/04/14 16:31:36 Removed all records from metadata '<name>', Connector <Notes connector name>, Method -Action [Truncate]-
2023/04/14 16:31:40 Error: Data overflow, Connector <Oracle connector name>', Method -Fetch-
2023/04/14 16:31:40 Activity Ended With An Error
The error appears due to one/multiple columns of type NVARCHAR2 where double-byte characters are stored.
The error can appear for LEI activities involving data transfer between Notes to Oracle as well as Oracle to Notes.
Note --> The data source in the above example is Oracle. It could be another data source as well having a column of type NVARCHAR2.
Currently, the workaround to deal with this issue is -->
Double the column width for the column of data type NVARCHAR2.
Ex --> If the impacted column causing the error is of type NVARCHAR2(20), then double the width by making it of type NVARCHAR2(40).
This will help in avoiding the "Data overflow" error.
Note -->
This is a limitation of a column of type NVARCHAR2.
The requirement is to allow the double-byte characters in such columns without increasing the width.
