To reduce the column width back to its original 8, we then run:Īlter table TAB_XYZ modify (COL_XYZ varchar2(8)) So the maximal string length for this column is 8 characters. Select max(length(COL_XYZ)) from TAB_XYZ We now move the data from the source into the target table without problem and then run: To resolve the error the column 'COL_XYZ' gets widened by:Īlter table TAB_XYZ modify (COL_XYZ varchar2(10)) The data in the column is a fixed length string of 8 characters. To migrate the data we use either a dblink or oracle datapump, both result in the same error. The column we get the error on is of CHAR(8).

The source and target table are identical and the column definitions are exactly the same. The target database runs - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production The source database runs - Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production Check sourceĮither make the destination column wider, or use a subset *Action: Examine the SQL statement for correctness. Semantics are in effect for the column, otherwise widths are Note that widths are reported in characters if character length Of the value, and the maximum allowed width of the column. The name of the column is given, along with the actual width Which is too wide for the width of the destination column.

*Cause: An attempt was made to insert or update a column with a value 00000 - 'value too large for column %s (actual: %s, maximum: %s)' SQL Error: ORA-12899: value too large for column 'USER_XYZ'.'TAB_XYZ'.'COL_XYZ' (actual: 10, maximum: 8)ġ2899. It occurs when we are migrating data from one oracle database to another: I'm trying to understand the above error.

Elysian hack error data too large