Problem

- Axway has defined the TO fields in VARCHAR() BYTES (e.g "ReturnMessage" field of XFBLog in VARCHAR (250) BYTES)
- When Axway products sends notifications to Sentinel greater than the defined number (e.g 250 characters) or using an encoding on 2 bytes, or more ...
- ORACLE truncates automatically the notification to the defined number of characters, but a character may be encoded on 2 bytes, or more (e.g accentuated character)
- if there are 1 or more characters like that in the characters kept after truncation
ORACLE tries to insert 251 bytes or more in a field of 250 bytes and the result is the error message ORA-12899: value too large for column

Resolution

- Modify the column of the TO table to be in VARCHAR () CHAR
- This will allow to be compatible with the result after the truncation of Oracle

or

- Change the encoding of your database in UTF8.
- Add in the server.properties file the line axway.use.unicode=true
- Regenerate all TO tables in the database.