SQL7939 - Data conversion required on INSERT or UPDATE

SQL7939
Message Text: Data conversion required on INSERT or UPDATE.
Cause Text: The INSERT or UPDATE values cannot be directly moved to the columns because the data type or length of a value is different than one of the columns. The INSERT or UPDATE statement ran correctly. Performance, however, would be improved if no data conversion was required. The reason data conversion is required is &1.
  • Reason 1 is that the INSERT or UPDATE value is a character or graphic string of a different length than column &2.
  • Reason 2 is that the INSERT or UPDATE value is a numeric type that is different than the type of column &2.
  • Reason 3 is that the INSERT or UPDATE value is a variable length string and column &2 is not.
  • Reason 4 is that the INSERT or UPDATE value is not a variable length string and column &2 is.
  • Reason 5 is that the INSERT or UPDATE value is a variable length string whose maximum length is different that the maximum length of column &2.
  • Reason 6 is that a data conversion was required on the mapping of the INSERT or UPDATE value to column &2, such as a CCSID conversion.
  • Reason 7 is that the INSERT or UPDATE value is a character string and column &2 is of type DATE, TIME, or TIMESTAMP.
  • Reason 8 is that the target table of the INSERT is not a SQL table.
Recovery Text: To get better performance, try to use values of the same type and length as their corresponding columns.

The attributes of the INSERT or UPDATE values are different than the attributes of the columns receiving the values. Since the values must be converted, they cannot be directly moved into the columns. Performance could be improved if the attributes of the INSERT or UPDATE values matched the attributes of the columns receiving the values.