Jitterbit · Database Insert, Update and Upsert activities
Field value too long / values were truncated
Short answer
This Jitterbit database error means a mapped source value is longer than the target column, and by default the value is rejected. In the activity configuration, enable Allow truncation of character fields.
VerifiedLast verified
01Error text
One or more values were truncated when inserting and/or updating the field
Field value too long02Likely causes
- A mapped source value is longer than the target column. By default the value is rejected and the activity reports an Error status.
03How to fix it
- In the activity configuration, enable Allow truncation of character fields.
- Or trim or transform the source field in the mapping so values never exceed the column length.
- Or widen the target column on the database side.
- Redeploy and rerun the operation.
04Official documentation
→Related errors
- Base64 decoding failedThis Jitterbit error in DBLookup or DBExecute means an agent earlier than 12.9 tried to Base64-decode a JDBC result that only looks like Base64, such as a JWT. For private agents, upgrade to version 12.9 or later.
- Database connection could not be established due to a security policy violationThis Jitterbit error means agent 12.10 or later blocked a database connection to a loopback address or one that uses a restricted connection string parameter. On the private agent, configure the [JdbcSecurity] section of jitterbit.conf to allow the specific connection or parameter.
- Could not initialize class com.microsoft.sqlserver.jdbc.KerbAuthenticationThis Jitterbit error means the Kerberos configuration files on the agent host do not have the correct file permissions. On the private agent host, set permissions to 644 on jaas.conf, krb5.conf and the Kerberos ticket cache file.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries