Symptom
View persisting in SAP Datasphere failed with the following error message:
- Error: "{"code":274, "message":"inserted value too large for column: \"**\".\"***\": line ** col ** (at pos ***): TrexColumnUpdate failed on table ****' with error: AttributeEngine: indexed value not within specified range;checkCesu8StringColumn(): max length (5000) violated on pos ..."
Environment
SAP Datasphere
Reproducing the Issue
View persisting
Cause
This issue occurs when the length of type definition of a column is insufficient to hold the actual data at runtime. Typical causes:
- Column length too small. The column definition in the view is smaller than the incoming values.
- Type/length mismatch between layers. Calculated or concatenated columns result in implicit conversion where application-layer definition and database-layer definition do not match.
Resolution
There are several ways to adjust column definitions depending on the situation.
Option A: Increase column length in the UI.
- Open the View
- Increase the length of the column
- Save and re-run the persistency
Option B: Use CAST to align types
See Also
- KBA 3627941 - AttributeEngine: indexed value not within specified range;checkCesu8StringColumn(): max length () violated on pos
- CAST Function (Data Type Conversion) | SAP Help Portal
Keywords
Datasphere, Persist View, Error 274, inserted value too large for column, length exceeded, CAST, substring limit , KBA , DS-DI-VIW , View Persistency and Runtime , Problem
Product
SAP Datasphere all versions
SAP Knowledge Base Article - Public